From: "George Pontis" <GPontis@z9.com>
To: barebox@lists.infradead.org
Subject: RE: Lost access to M25Pxx in move to 2013.01
Date: Mon, 4 Feb 2013 12:16:07 -0800 [thread overview]
Message-ID: <004901ce0314$7742f870$65c8e950$@com> (raw)
In-Reply-To: <CAA4bVAFm-82XbexDM9sPUmfYUmh8bp9Y2o2eM20PXmqiqDU=Lg@mail.gmail.com>
> -----Original Message-----
> From: Antony Pavlov [mailto:antonynpavlov@gmail.com]
> Sent: Saturday, February 02, 2013 9:56 AM
> To: George Pontis
> Cc: barebox@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
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-02-04 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 16:35 George Pontis
2013-02-02 17:56 ` Antony Pavlov
2013-02-02 18:09 ` Eric Bénard
2013-02-04 20:16 ` George Pontis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004901ce0314$7742f870$65c8e950$@com' \
--to=gpontis@z9.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox