From: "Jan Lübbe" <jlu@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: AM335x NAND
Date: Mon, 30 Jun 2014 16:00:58 +0200 [thread overview]
Message-ID: <1404136858.9771.109.camel@polaris.local> (raw)
In-Reply-To: <53AC8965.4020806@web.de>
On Thu, 2014-06-26 at 22:58 +0200, Stefan Müller-Klieser wrote:
> 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've seen that the Phytec AM335x BSPs contain patches which add support
for the ELM. This wasn't mainlined, but might a good starting point.
Regards,
Jan
--
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
prev parent reply other threads:[~2014-06-30 14:01 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
2014-06-30 14:00 ` Jan Lübbe [this message]
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=1404136858.9771.109.camel@polaris.local \
--to=jlu@pengutronix.de \
--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