611a15afcd
The fs_no mean used to be fs_enet driver driven, hence it was an enumeration across all the possible fs_enet "users" in the SoC. Now, with QE on the pipeline, and to make DTS descriptions more clear, fs_no features relevant SoC part number, with additional field to describe the SoC type. Another reason for that is now not only fs_enet is going to utilize those stuff. There might be UART, HLDC, and even USB, so to prevent confusion and be ready for upcoming OF_device transfer, fs_enet and cpm_uart drivers were updated in that concern, as well as the relevant DTS. Signed-off-by: Vitaly Bordug <vbordug@ru.mvista.com> |
||
|---|---|---|
| .. | ||
| dts | ||
| .gitignore | ||
| addnote.c | ||
| addRamDisk.c | ||
| crt0.S | ||
| div64.S | ||
| dummy.c | ||
| elf.h | ||
| hack-coff.c | ||
| install.sh | ||
| main.c | ||
| Makefile | ||
| page.h | ||
| ppc_asm.h | ||
| prom.c | ||
| prom.h | ||
| README | ||
| rs6000.h | ||
| stdio.c | ||
| stdio.h | ||
| string.h | ||
| string.S | ||
| zImage.coff.lds | ||
| zImage.lds | ||
To extract the kernel vmlinux, System.map, .config or initrd from the zImage binary: objcopy -j .kernel:vmlinux -O binary zImage vmlinux.gz objcopy -j .kernel:System.map -O binary zImage System.map.gz objcopy -j .kernel:.config -O binary zImage config.gz objcopy -j .kernel:initrd -O binary zImage.initrd initrd.gz Peter