From: Sascha Hauer <s.hauer@pengutronix.de>
To: Roberto Nibali <rnibali@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Booting mx25 based device from SD and NOR
Date: Thu, 31 May 2012 19:06:31 +0200 [thread overview]
Message-ID: <20120531170631.GR30400@pengutronix.de> (raw)
In-Reply-To: <CAONxwYNf7_+H1oC2AuL2A_edBXqqkdSjxt6eFwPvU4VS+UzU0g@mail.gmail.com>
On Thu, May 31, 2012 at 03:12:08PM +0200, Roberto Nibali wrote:
> Hi
>
>
>
> > > +# or set your networking parameters here
> > > +#eth0.ipaddr=192.168.1.80
> > > +#eth0.netmask=255.255.255.0
> > > +#eth0.gateway=a.b.c.d
> > > +eth0.serverip=192.168.1.23
> > > +eth0.ethaddr=00:50:c2:8c:e6:0e
> >
> > *never* *ever* add MAC addresses to the default environment.
>
>
> Ok. In my case, the MAC address is actually stored inside a secured at24
> EEPROM buffer. Unfortunately, at24 via I2C does not seem to be available in
> barebox. I reckon I have to port it from the kernel or uboot :).
Or just leave the field blank. In this case a random (local-) MAC
address is generated.
>
> I have included some more debugging and also workarounds for the mx25. This
> is the current debug output, where it clearly indicates that for some
> reason the mx25 esdhc related registers never show a transfer complete for
> a multiblock write:
The kernel has this:
if (is_imx25_esdhc(imx_data) || is_imx35_esdhc(imx_data))
/* Fix errata ENGcm07207 present on i.MX25 and i.MX35 */
host->quirks |= SDHCI_QUIRK_NO_MULTIBLOCK
| SDHCI_QUIRK_BROKEN_ADMA;
Which means that the kernel won't do multiblock on i.MX25 and i.MX35.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-05-31 17:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 12:11 Roberto Nibali
2012-05-22 18:42 ` Sascha Hauer
2012-05-23 10:43 ` Roberto Nibali
2012-05-23 11:47 ` Eric Bénard
2012-05-24 12:49 ` Roberto Nibali
2012-05-24 12:58 ` Eric Bénard
2012-05-24 13:18 ` Roberto Nibali
2012-05-24 13:31 ` Eric Bénard
2012-05-25 9:04 ` Roberto Nibali
2012-05-25 10:08 ` Eric Bénard
2012-05-29 9:06 ` Roberto Nibali
2012-05-29 9:29 ` Sascha Hauer
2012-05-29 9:56 ` Roberto Nibali
2012-05-29 10:14 ` Roberto Nibali
2012-05-30 5:47 ` Sascha Hauer
2012-05-30 6:39 ` Juergen Beisert
2012-05-31 13:12 ` Roberto Nibali
2012-05-31 17:06 ` Sascha Hauer [this message]
2012-06-01 10:25 ` Roberto Nibali
2012-06-05 7:09 ` Sascha Hauer
2012-05-24 17:17 ` Sascha Hauer
2012-05-25 9:19 ` Roberto Nibali
2012-05-25 10:01 ` Sascha Hauer
2012-05-29 9:26 ` Roberto Nibali
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=20120531170631.GR30400@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rnibali@gmail.com \
/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