From: Vanalme Filip <F.Vanalme@TELEVIC.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: bootargs
Date: Fri, 4 Mar 2011 14:49:37 +0100 [thread overview]
Message-ID: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B010B6@SRV-VS06.TELEVIC.COM> (raw)
In-Reply-To: <20110304083028.GC29521@pengutronix.de>
> -----Original Message-----
> From: Sascha Hauer [mailto:s.hauer@pengutronix.de]
> Sent: vrijdag 4 maart 2011 9:30
> To: Vanalme Filip
> Cc: barebox@lists.infradead.org
> Subject: Re: bootargs
>
> On Fri, Mar 04, 2011 at 09:18:26AM +0100, Vanalme Filip wrote:
> >
> > I think it might have something to do with the BI-swapping issue. The
> > BI-swapping is, as far as I know, not yet implemented in the kernel's
> > NAND driver. So, if I flash the rootfs with Barebox (doing the
> > BI-swap) and then read the rootfs from within the kernel (not doing
> > the BI-swap), I will for sure have problem...
>
> Using 2k NAND flash on the i.MX27 will most likely lead to problems...
>
> >
> > Remarkable : the Linux version I use is a version we downloaded from
> > Freescale's git repositry. In this version, we could select the
> > i.MX27PDK board. However, that board's code is obviously not
> > registering the NAND flash driver... knowing that the i.MX27PDK only
> > contains NAND-flash, this is very weird...
>
> Normally we do root over nfs during development, so this is not very
> surprising. As Freescale does not support the i.MX27 anymore the
> i.MX27PDK support in FSLs git kernel is probably identical to mainline.
>
> Sascha
>
[Filip]
I implemented the BI-swapping in mxc_nand.c (analogous to the implementation in Barebox's mxc_nand.c). With success. The kernel can now mount the root filesystem from NAND flash and ends with a prompt.
Filip
> --
> 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:[~2011-03-04 13:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 8:18 bootargs Vanalme Filip
2011-03-04 8:30 ` bootargs Sascha Hauer
2011-03-04 12:54 ` bootargs Vanalme Filip
2011-03-04 13:13 ` bootargs Baruch Siach
2011-03-04 13:24 ` bootargs Vanalme Filip
2011-03-04 13:49 ` Vanalme Filip [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-03 12:22 bootargs Vanalme Filip
2011-03-03 12:33 ` bootargs Sascha Hauer
2011-03-03 14:00 ` bootargs Vanalme Filip
2011-03-03 14:13 ` bootargs Sascha Hauer
2011-03-03 14:23 ` bootargs Vanalme Filip
2011-03-03 14:34 ` bootargs Jon Ringle
2011-03-03 14:42 ` bootargs Vanalme Filip
2011-03-03 14:43 ` bootargs Sascha Hauer
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=6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B010B6@SRV-VS06.TELEVIC.COM \
--to=f.vanalme@televic.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