Hi, Werner, Willie, Nod:
production information now:
device nand0 <neo1973-nand>, # parts = 6
#: name size offset mask_flags
0: u-boot 0x00040000 0x00000000 0
1: u-boot_env 0x00040000 0x00040000 0
2: kernel 0x00800000 0x00080000 0
3: splash 0x000a0000 0x00880000 0
4: factory 0x00040000 0x00920000 0
5: rootfs 0x076a0000 0x00960000 0
Regards,
-- Miles
nod wrote:
--
- Nod Huang <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
http://openmoko.org <http://openmoko.org/>/
============================================================================
Software for the world's first truly open Free Software mobile phone
*寄件人: *Willie Chen <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>
*日期: *2008年1月10日 上午12時55分20秒
*收件人: *Werner Almesberger <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>
*副本: *Andy Green <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>,
Wolfgang Spraul <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>, [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>, [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>, Jim Huang <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>, [email protected]
<mailto:[email protected]>
*標題: **Re: Hello -- NAND/NOR Flash design for GTA02*
Hi Nod, Werner,
Please provide your production information. Werner can't decide the
NAND/NOR flash partition map here. Thanks.
According GTA02 product specification, we have backup and maintenance
features. Jserv will also request one partition flash that has
erasing protection here. There is a another design issue that NOR
flash is booting uboot and kernel. Or we still use current state that
is booting from NAND flash.
Regards,
willie
Werner Almesberger wrote:
[ Added Cc to nod. ]
Andy Green wrote:
If it is really needed for the data to stay in the flash, I guess since
we change the partitioning to support NOR it's okay to change it at the
same time to add a partition... what do you think Werner?
Yes, what we would need to decide this properly is a list (from Nod ?)
of things that have to go to this partition (or whatever it shall be).
This list has to detail:
- what is it ? E.g., serial number.
- who accesses it ? E.g., set and read by DM2 (= kernel)
- how big is it, roughly ? E.g., a few bytes.
- how long does it have to be on the device ? E.g., forever.
If we can't get this list, then a "worst-case" solution would be to
just create a new NAND partition, along with all the other partition
changes. (I suspect that's what production has in mind anyway, i.e.,
basically what we've done for HXD8.)
Cheers, Werner
