[Buildroot] Dataflash rootfs problems (still)

[Ulf Samuelsson <ulf@atmel.com>]

Ok, i'll give a try, as far as i'm concerned there are two choices for SPI
driver on the kernel:

- AT91_SPI
- ATMEL_SPI

Which one is better?, i've tested ATMEL_SPI this afternoon, but the kernel
doesn't detects my dataflash, can you point me to a source of information to
read steps to define my dataflash speed and get detected on boot?.

==> The AT91_SPI is the original SPI for AT91
        The Atmel_SPI is a newer version which also supports AVR32.
        This is probably the one to go for long term, but I did not try it myself.
        Try disabling the SD/MMC card interface.
        You probably want to address questions like this to the linux kernel mailing
        list instead of the buildroot list.

My previous kernel was detecting the dataflash itself, but when i define the
speed on my board config, the dataflash isn't detected anymore.

2007/10/25, Ulf Samuelsson <ulf@atmel.com>:
>
> > What about using the SPI bitbang driver for the AT91??
> >
>
>
> Not a good idea since you are transferring large amount of data.
> Better to use the PDC and the H/W SPI.
> Just set down the speed of the SPI.
>
> >> ons 2007-10-24 klockan 21:34 +0300 skrev Ivan Kuten:
> >> > >
> >> > > During the 1st boot, Dropbear creates and "writes" the generated
> keys,
> >> maybe
> >> > > is this *write* operation the one screwing up the dataflash?
> >> > >
> >> >
> >> > We have similar problems with Dataflash&RM9200
> >> > *write* operation is unreliable - we had corrupted filesystem after
> >> reboot.
> >> > Our solution was to use r/o only on dataflash.
> >> >
> >>
> >> I would reduce speed to 5 Mbps or lower. or implement the external
> gate.
> >> Moving to the AT91SAM9260 is of course a nice alternative.
> >> Lower cost, (soon) much higher speed (with the AT91SAM9260A)
> >> Better BootROM (I defined it :-)
> >>
> >>
>


Best Regards
Ulf Samuelsson