Fix pictures links and add ARM pictures

This commit is contained in:
Dr-Noob
2020-12-25 18:39:58 +01:00
parent cc20fff6ea
commit 1ef6daf943
3 changed files with 13 additions and 6 deletions

View File

@@ -1,7 +1,7 @@
# cpufetch # cpufetch
Simplistic yet fancy CPU architecture fetching tool Simplistic yet fancy CPU architecture fetching tool
![cpu1](i9.png) ![cpu1](pictures/i9.png)
### Platforms ### Platforms
cpufetch currently supports x86 CPUs (both Intel and AMD CPUs) cpufetch currently supports x86 CPUs (both Intel and AMD CPUs)
@@ -34,13 +34,20 @@ make
The Makefile is designed to work on both Linux and Windows. The Makefile is designed to work on both Linux and Windows.
### Example ### Examples
Here are more examples of how `cpufetch` looks on different CPUs. Here are more examples of how `cpufetch` looks on different CPUs.
![cpu2](epyc.png) ##### x86_64 CPUs
![cpu3](cascade_lake.png) ![cpu2](pictures/epyc.png)
![cpu3](pictures/cascade_lake.png)
##### ARM CPUs
![cpu4](pictures/exynos.png)
![cpu5](pictures/snapdragon.png)
### Colors and style ### Colors and style
By default, `cpufetch` will print the CPU art with the system colorscheme. However, you can always set a custom color scheme, either By default, `cpufetch` will print the CPU art with the system colorscheme. However, you can always set a custom color scheme, either
@@ -61,5 +68,5 @@ See [cpufetch programming documentation](https://github.com/Dr-Noob/cpufetch/blo
### Bugs or improvements ### Bugs or improvements
There are many open issues in github (see [issues](https://github.com/Dr-Noob/cpufetch/issues)). Feel free to open a new one report an issue or propose any improvement in `cpufetch` There are many open issues in github (see [issues](https://github.com/Dr-Noob/cpufetch/issues)). Feel free to open a new one report an issue or propose any improvement in `cpufetch`
### Testers ### Testing
I would like to thank [Gonzalocl](https://github.com/Gonzalocl) and [OdnetninI](https://github.com/OdnetninI) for their help, running `cpufetch` in many different CPUs they have access to, which makes it easier to debug and check the correctness of `cpufetch`. I would like to thank [Gonzalocl](https://github.com/Gonzalocl) and [OdnetninI](https://github.com/OdnetninI) for their help, running `cpufetch` in many different CPUs they have access to, which makes it easier to debug and check the correctness of `cpufetch`.

BIN
pictures/exynos.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

BIN
pictures/snapdragon.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 43 KiB