Github_Repos/cvw
1
0
Fork 1
mirror of https://github.com/openhwgroup/cvw synced 2025-02-11 06:05:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

greatly stripped down unused stuff in linux config

Browse Source
This commit is contained in:
bbracker 2021-07-10 11:53:35 -04:00
parent 488cfa16ff
commit e77a9169b6
2 changed files with 167 additions and 2385 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
wally-pipelined/linux-testgen/WALLY-README.txt
View File

@ -7,32 +7,36 @@ If you instead wish to regenerate the RAMs and testvectors from a new Linux imag
you'll need to build the new Linux image, simulate it, and parse its output, you'll need to build the new Linux image, simulate it, and parse its output,
as described below. as described below.
* To build a new Linux image, Git clone the Buildroot repository to ./buildroot. *To build a new Linux image:
For reference, most recent commit made to the Buildroot repo was 1. Git clone the Buildroot repository to ./buildroot.
as of last generating the image found on Tera: For reference, Wally (*** will) be proven to work on an image built using
Buildroot when the following was the most recent commit to the Buildroot repo:
commit 4047e10ed6e20492bae572d4929eaa5d67eed746 commit 4047e10ed6e20492bae572d4929eaa5d67eed746
Author: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> Author: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
Date: Wed Jun 30 06:27:10 2021 +0200 Date: Wed Jun 30 06:27:10 2021 +0200
Then hard link ./buildroot-config-src/main.config to ./buildroot/.config.
2. Then hard link ./buildroot-config-src/main.config to ./buildroot/.config.
That config file will in turn point to the other config files in ./buildroot-config-src. That config file will in turn point to the other config files in ./buildroot-config-src.
If you wish to modify the configs, then
1. Copy ./buildroot-config-src/linux.config to ./buildroot/output/build/linux-5.10.7/.config 3. If you wish to modify the configs, then in ./buildroot:
2. Copy ./buildroot-config-src/busybox.config to ./buildroot/output/build/busybox-1.33.1/.config a. Run "make menuconfig" or "make linux-menuconfig" or "make busybox-menuconfig".
3. Run "make menuconfig" "make linux-menuconfig" "make busybox-menuconfig" as needed. b. For linux-menuconfig and busybox-menuconfig, use the TUI (terminal UI) to load in
4. Copy ./buildroot/output/build/linux-5.10.7/.config back to ./buildroot-config-src/linux.config configs from "../../../../buildroot-config-src/<linux or busybox>.config"
5. Copy ./buildroot/output/build/busybox-1.33.1/.config back to ./buildroot-config-src/busybox.config We have to tell make to go back up several dirs because for linux and busybox,
(*** There may be a better way to do this, but do know that setting up main.config make traverses down to ./buildroot/output/build/<linux or busybox>.
to point to those two locations within the Buildroot repo results in interesting c. Likewise, when you are done editing, tell the TUI to save to the same location.
".config is the same as .config" errors.)
Then finally you can run make. Note that it may be necessary to rerun make twice, 4. Then finally you can run make. Note that it may be necessary to rerun make twice,
once when main.config asks for an "Image" output, and once when main.config once when main.config asks for an "Image" output, and once when main.config
"vmlinux" output. "vmlinux" output.
* To generate new RAMs and testvectors from a Linux image, *To generate new RAMs and testvectors from a Linux image:
sym link ./buildroot-image-output to either your new image in ./buildroot/output/image 1. sym link ./buildroot-image-output to either your new image in ./buildroot/output/image
or the existing image at /courses/e190ax/buildroot/output/image on Tera. or the existing image at /courses/e190ax/buildroot/output/image on Tera.
(This might require first deleting the empty buildroot-image-output directory). This might require first deleting the empty buildroot-image-output directory.
Then run ./testvector-generation/logBuildrootMem.sh to generate RAMs. 2. Then run ./testvector-generation/logBuildrootMem.sh to generate RAMs.
Then run ./testvector-generation/logAllBuildroot.sh to generate testvectors. 3. Then run ./testvector-generation/logAllBuildroot.sh to generate testvectors.
Note that you can only have one instance of QEMU open at a time! Check "ps -ef" to see if
anybody else is running QEMU. These latter two steps require QEMU.
Note that you can only have one instance of QEMU open at a time!
At least on Tera, it seems. Check "ps -ef" to see if anybody else is running QEMU.

2492
wally-pipelined/linux-testgen/buildroot-config-src/linux.config
View File

File diff suppressed because it is too large Load Diff