On Monday 07 May 2007,
ian@brightstareng.com wrote:
> On Monday 07 May 2007 06:36, David Goodenough wrote:
> > I am currently trying to get a 2.6.19 kernel working on a
> > Routerboard RB112 (and the rest of the 100 series).
> >
> > The RB112 (like the RB532) has a boot loader which loads an
> > ELF file which comes from one of two places, it can be
> > downloaded from a TFTP server (I have this working) or from
> > the onboard NAND chip, the first 4MB of which are assumed to
> > be a Yaffs partition containing a single file called kernel.
>
> Seems to me that you need to know more about the NAND layering
> used by the bootloader: What is the layout of the oob/spare
> data? Which bytes are used for ECC (and what order), which bytes
> are used to hold Yaffs' tags (and what order). Then you can
> make linux mtd and yaffs work the same way. Unless Yaffs is
> specifically licensed for inclusion in this bootloader, the
> producer should be obligated to provided you with the complete
> code (GPL).
>
> -imcd
I have no idea what data is in the OOB data, I have never met a
tool that would show me. Can you tell me how to read it?
As I said later in the note to which you replied, Microtik do
ship a version of Yaffs suitable for linux 2.4, I am trying to
get it to work with Linux 2.6.19+. I have no idea what licences
Microtik have from Aleph1, I presume that they have one for their
boot loader. The point however is that Yaffs on 2.6.16 and below
work, that with 2.6.19 seem not to - or I have not found the right
combination of options. Resolving this is the point of my question.
David
(text/plain)