On Sun, Apr 10, 2011 at 11:40 PM, Carl-Daniel Hailfinger <[email protected]> wrote: > Hi Hamo, > > I wrote a CBFS design change proposal ~2 years ago which handled such issues > just fine, but IIRC nobody had time to comment. I can try to dig it up > again. > > Regards, > Carl-Daniel
Can you send your change to me? Thanks. > > Am 10.04.2011 14:49 schrieb Hamo: >> >> Dear lists, >> I have be studying CBFS filesystem these days. Since coreboot only >> supports IA32 architecture now, the CBFS has hard-coded boot address >> and all the boot-related code and master header are located at around >> 0xFFFFFFF0. But as ARM read their first instruction at 0x0, we need >> change the CBFS filesystem but not destroy IA32 support. When porting >> to ARM, how should the rom be organized? I have 2 ideas: >> 1. Totally rewrite the CBFS structure on ARM according to that one on >> IA32 to meet the requirement of ARM architecture, including move the >> reset code and bootblock to the start of ROM(at address 0x0) and put >> all the other components follow them. In this way, we should rewrite >> the CBFStool and add a new option to CBFStool to tell it the >> architecture we are using. >> 2. Use the same structure on IA32 architecture but set the master >> header's offset to other value than 0x0 so that we can put boot code >> at the start of rom. >> Which one should I take or Do we have any better choice? >> Hope for your help. >> >> > > > -- > http://www.hailfinger.org/ > > -- """ Keep It Simple,Stupid. """ Chinese Name: 白杨 Nick Name: Hamo Homepage: http://hamobai.com/ GPG KEY ID: 0xA4691A33 Key fingerprint = 09D5 2D78 8E2B 0995 CF8E 4331 33C4 3D24 A469 1A33 -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
