From: Holger Schurig <holgerschurig@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Question about SPI NOR flash
Date: Tue, 13 May 2014 12:22:13 +0200 [thread overview]
Message-ID: <CAOpc7mFPDrfWRW3+kP5=EcPvzGtPdx++ac1NrvNz=qaLR2xN7w@mail.gmail.com> (raw)
In-Reply-To: <20140513100044.GO5858@pengutronix.de>
> Your device is detected as a 32KB mr25h256 instead
> of the n25q512 you really have.
Oh, something here is flaky. Because sometimes it get's detected
correctly. Sigh. This here with dev_dbg() turned into dev_info() and
the partition things removed from the DTS:
detected i.MX6 Quad revision 1.2
mdio_bus: miibus0: probed
m25p80 spiflash@00: n25q512 (65536 Kbytes)
m25p80 spiflash@00: mtd .name = <NULL>, .size = 0x4000000 (64MiB)
.erasesize = 0x00001000 (4KiB) .numeraseregions = 0
imx-esdhc 2194000.usdhc: registered as 2194000.usdhc
imx-esdhc 219c000.usdhc: registered as 219c000.usdhc
environment load /dev/env0: No such file or directory
Maybe you have to create the partition.
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...
> http://lists.infradead.org/pipermail/linux-mtd/2014-January/051382.html?#
Hmm, this isn't in origin/master. I'm a bit confused.
What should I use, master or next? And why do both get patches
applied regularly?
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-05-13 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 8:55 Holger Schurig
2014-05-13 10:00 ` Sascha Hauer
2014-05-13 10:22 ` Holger Schurig [this message]
2014-05-13 10:24 ` Sascha Hauer
2014-05-13 11:35 ` Holger Schurig
2014-05-22 16:14 ` Holger Schurig
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='CAOpc7mFPDrfWRW3+kP5=EcPvzGtPdx++ac1NrvNz=qaLR2xN7w@mail.gmail.com' \
--to=holgerschurig@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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