From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: How to port brcmnand Linux driver?
Date: Wed, 21 Sep 2016 17:09:03 +0200 (CEST) [thread overview]
Message-ID: <1030650857.351517095.1474470543435.JavaMail.root@zimbra32-e6.priv.proxad.net> (raw)
In-Reply-To: <20160921090500.bkrkohjxpye2gkc6@pengutronix.de>
> On Wed, Sep 21, 2016 at 10:40:43AM +0200, Eric Le Bihan wrote:
> >
> > I'm trying to port the brcmnand driver for Broadcom NAND controller
> > from Linux.
> > This driver requires an update of the MTD headers in barebox, as
> > they lack
> > definitions for functions such as mtd_set_ooblayout().
> >
> > What is the recommended strategy for this? Should I update the
> > whole set of
> > headers and report the barebox specific changes (use of device_d,
> > etc) or only
> > add the missing functions?
>
> For the mtd headers we usually only port the functions we need which
> worked good enough in the past.
OK. I've noticed that the use of mtd_set_ooblayout() was introduced in
Linux 4.7. So I'll port brcmnand from 4.6, thus avoiding quite a few
changes in the OOB/ECC management.
Thanks for your advices.
Best regards,
--
ELB
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2016-09-21 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <122759075.350079920.1474446203319.JavaMail.root@zimbra32-e6.priv.proxad.net>
2016-09-21 8:40 ` Eric Le Bihan
2016-09-21 9:05 ` Sascha Hauer
2016-09-21 15:09 ` Eric Le Bihan [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=1030650857.351517095.1474470543435.JavaMail.root@zimbra32-e6.priv.proxad.net \
--to=eric.le.bihan.dev@free.fr \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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