From: "Bryan Wu" <cooloney.lkml@gmail.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: "Bryan Wu" <bryan.wu@analog.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
"Michael Hennerich" <michael.hennerich@analog.com>
Subject: Re: [PATCH 1/1] [MTD/NAND]: Add Blackfin BF52x on-chip NAND Flash controller driver support in bf5xx_nand driver
Date: Fri, 23 Nov 2007 22:25:29 +0800 [thread overview]
Message-ID: <386072610711230625k23b68e49q6090b7eb27c2c039@mail.gmail.com> (raw)
In-Reply-To: <1195813178.25590.35.camel@pmac.infradead.org>
On Nov 23, 2007 6:19 PM, David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Fri, 2007-11-23 at 18:14 +0800, Bryan Wu wrote:
> >
> > +#ifdef CONFIG_BF54x
> > /* Setup DMAC1 channel mux for NFC which shared with SDH */
> > val = bfin_read_DMAC1_PERIMUX();
> > val &= 0xFFFE;
> > bfin_write_DMAC1_PERIMUX(val);
> > SSYNC();
> > -
> > +#endif
>
> You can't build a multiplatform kernel which runs on BF52x and BF54x?
There are some hardware difference between BF52x and BF54x. We have to do this.
> And want to make it harder to do so in future?
>
Any idea to make it easier? providing a specific hardware init hook
function from each platform board files?
Regards,
-Bryan
> --
> dwmw2
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2007-11-23 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 10:14 Bryan Wu
2007-11-23 10:19 ` David Woodhouse
2007-11-23 14:25 ` Bryan Wu [this message]
2007-11-23 21:52 ` Arjan van de Ven
2007-11-23 22:04 ` Robin Getz
2007-11-24 6:43 ` David Woodhouse
2007-11-24 7:15 ` Bryan Wu
2007-11-24 13:11 ` Robin Getz
-- strict thread matches above, loose matches on Subject: below --
2007-10-30 9:08 Bryan Wu
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=386072610711230625k23b68e49q6090b7eb27c2c039@mail.gmail.com \
--to=cooloney.lkml@gmail.com \
--cc=bryan.wu@analog.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael.hennerich@analog.com \
--cc=uclinux-dist-devel@blackfin.uclinux.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
all inboxes | Powered by JetHome®