From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mxc nand: Add support for i.MX5
Date: Tue, 8 Jan 2013 11:40:05 +0100 [thread overview]
Message-ID: <201301081140.05508.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5DiAdW-5OBVQo4MNE38NdErXcvJZxuLeLjjE=QvysbHXQ@mail.gmail.com>
Dear Fabio Estevam,
> On Tue, Jan 8, 2013 at 7:33 AM, Marek Vasut <marex@denx.de> wrote:
> > From: Beno?t Th?baudeau <benoit.thebaudeau@advansee.com>
> >
> > Signed-off-by: Beno?t Th?baudeau <benoit.thebaudeau@advansee.com>
> > Cc: Scott Wood <scottwood@freescale.com>
> > Cc: Stefano Babic <sbabic@denx.de>
> > ---
> >
> > arch/arm/include/asm/arch-mx5/imx-regs.h | 9 ++
> > drivers/mtd/nand/mxc_nand.c | 219
> > ++++++++++++++++++++++-------- include/fsl_nfc.h
> > | 149 +++++++++++++------- nand_spl/nand_boot_fsl_nfc.c |
> > 114 ++++++++++++---- 4 files changed, 364 insertions(+), 127
> > deletions(-)
> >
> > NOTE: I'm seeing issues when this is compiled into U-Boot. U-Boot won't
> > boot on my MX53 board and will hang right after printing "DRAM:" and
> > before printing the CPU info. I suspect it's some kind of unaligned
> > access.
>
> I was seeing the same problem and this patch fixed it:
> http://git.denx.de/?p=u-boot/u-boot-imx.git;a=commit;h=1411fb37b5a8d56becec
> c5e6ea09d2e0670b9810
>
> Let me know if this fixes the issue you are seeing.
I have that applied, but still seeing the issue. Maybe there's some additional
problem with the NAND driver ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-01-08 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 9:33 [U-Boot] [PATCH 1/2] mxc nand: Add support for i.MX5 Marek Vasut
2013-01-08 10:23 ` Fabio Estevam
2013-01-08 10:40 ` Marek Vasut [this message]
2013-01-08 10:24 ` Benoît Thébaudeau
2013-01-08 10:38 ` Marek Vasut
2013-01-08 10:54 ` Benoît Thébaudeau
2013-01-08 11:05 ` Marek Vasut
2013-01-08 11:18 ` Benoît Thébaudeau
2013-02-02 13:43 ` Benoît Thébaudeau
2013-02-02 15:04 ` Marek Vasut
2013-02-04 19:55 ` Scott Wood
2013-01-08 18:34 ` Scott Wood
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=201301081140.05508.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.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