Editing Mer/Status/SmartQ5
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
- | |||
- | |||
- | |||
- | |||
Notes on SmartQ 5 MID: | Notes on SmartQ 5 MID: | ||
Line 212: | Line 208: | ||
This is where qi is placed, maximum 16 blocks size, zero out the remaining 2/1027 blocks | This is where qi is placed, maximum 16 blocks size, zero out the remaining 2/1027 blocks | ||
- | Qi will then (see /qi/src/cpu/s3c6410/start_qi.c) try to locate a SmartQ firmware image (see genimage for format, or same file, struct FirmHead on | + | Qi will then (see /qi/src/cpu/s3c6410/start_qi.c) try to locate a SmartQ firmware image (see genimage for format, or same file, struct FirmHead on 16384 blocks before the end, or 32768 blocks before the end, and load u-boot from the firmware image. |
If this fails it will load u-boot from 512+18 blocks before the end, maximum size 512 blocks. | If this fails it will load u-boot from 512+18 blocks before the end, maximum size 512 blocks. | ||
Line 254: | Line 250: | ||
Offset in NAND is meant as offset from 16/8mb end offset in blocks (512 byte blocks). If offset is 0, it is not meant to be in the NAND image (qi doesn't make any sense there, nor rootfs, etc) | Offset in NAND is meant as offset from 16/8mb end offset in blocks (512 byte blocks). If offset is 0, it is not meant to be in the NAND image (qi doesn't make any sense there, nor rootfs, etc) | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- |
Learn more about Contributing to the wiki.