From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Stefan Müller-Klieser" <stefan.mueller-klieser@web.de>
Cc: barebox@lists.infradead.org
Subject: Re: AM335x NAND
Date: Sat, 28 Jun 2014 01:31:52 +0200 [thread overview]
Message-ID: <20140627233152.GU14257@pengutronix.de> (raw)
In-Reply-To: <53AC8965.4020806@web.de>
Hi Stefan,
On Thu, Jun 26, 2014 at 10:58:13PM +0200, Stefan Müller-Klieser wrote:
> Dear list,
>
> I am working on TI's AM335x SoCs and want to add support for the missing
> NAND controller features in the driver. As the NAND interface of the
> barebox is not in sync with the kernel, it is difficult for me to decide
> which way to go. Is there already work going on to update the barebox
> NAND driver? I suppose the barebox nand_omap_gpmc is a port of the
> u-boot NAND driver. So, should I port the features from the u-boot
> driver into barebox, e.g. ELM and HW BCH16 support, or are there
> different plans from the maintainer?
I have no further plans with nand_omap_gpmc. Note the driver can switch
the ecc correction type during runtime. We have to do this since the
boot ROM needs a different ecc layout than the rest of the NAND does.
I don't want to lose this feature. Other than that feel free to update
the driver with new features.
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:[~2014-06-27 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 20:58 Stefan Müller-Klieser
2014-06-27 23:31 ` Sascha Hauer [this message]
2014-06-30 14:00 ` Jan Lübbe
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=20140627233152.GU14257@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=stefan.mueller-klieser@web.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