Lost access to M25Pxx in move to 2013.01
George Pontis
GPontis at z9.com
Mon Feb 4 15:16:07 EST 2013
> -----Original Message-----
> From: Antony Pavlov [mailto:antonynpavlov at gmail.com]
> Sent: Saturday, February 02, 2013 9:56 AM
> To: George Pontis
> Cc: barebox at lists.infradead.org
> Subject: Re: Lost access to M25Pxx in move to 2013.01
>
...
>
> Here is part of my board code. It works for old barebox release:
>
> static struct spi_board_info board_spi_devs[] __initdata = {
> {
> /* Spansion S25FL004A SPI flash */
> .name = "m25p",
> .max_speed_hz = 50000000,
> .bus_num = 0,
> .chip_select = 0,
> .mode = SPI_MODE_3,
> .platform_data = &lig32_spi0_flash_data,
> }
> ...
> spi_register_board_info(board_spi_devs,
> ARRAY_SIZE(board_spi_devs));
>
> I changed the 'name' field from "m25p" to "m25p80", and it works again!
>
>
This fixed it for me too, thanks for posting. This behavior is different
from the way that at least some kernels work. I was working with 3.4.6, and
there it prefers to see the name be the same as the actual hardware device.
So in my case the kernel expects .name to be "m25p32", and if it gets m25p80
it squawks a message saying what it really found was "m25p32".
GP
More information about the barebox
mailing list