mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Clemens Koller" <clemens.koller@anagramm.de>
Cc: bryan.wu@analog.com, "David Woodhouse" <dwmw2@infradead.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH] Blackfin BF54x NAND Flash Controller driver
Date: Mon, 3 Sep 2007 13:58:53 -0400	[thread overview]
Message-ID: <8bd0f97a0709031058g3d0b5e8dodbb5fa5f35366b4f@mail.gmail.com> (raw)
In-Reply-To: <46DBDE75.90203@anagramm.de>

On 9/3/07, Clemens Koller <clemens.koller@anagramm.de> wrote:
> Bryan Wu schrieb:
> > This is the driver for latest Blackfin BF54x nand flash controller
> >
> >  - use nand_chip and mtd_info common nand driver interface
> >  - provide both PIO and dma operation
> >  - compiled with ezkit bf548 configuration
> >  - use hardware 1-bit ECC
> >  - tested with YAFFS2 and can mount YAFFS2 filesystem as rootfs
>
> Looks great!
>
> Will this driver also work for the new BF52x series of the Blackfin Series?
> (Or is it planned to make it work for... anytime soon.)

the order for porting of new chips is:
u-boot -> core kernel -> peripherals

we generally dont bother looking at peripherals until the earlier stuff is done
-mike

  reply	other threads:[~2007-09-03 17:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-03  7:25 Bryan Wu
2007-09-03 10:14 ` Clemens Koller
2007-09-03 17:58   ` Mike Frysinger [this message]
2007-09-03 16:46 ` David Woodhouse
2007-09-03 17:33   ` Bryan Wu
2007-09-03 17:57 ` Mike Frysinger
2007-09-04  3:21   ` Bryan Wu
2007-09-13  8:37 ` Andrew Morton
2007-09-13  8:45   ` Mike Frysinger
2007-09-13  8:45     ` Bryan Wu
2007-09-13  8:51       ` Mike Frysinger
2007-09-13  8:49         ` Bryan Wu
2007-09-13  8:49     ` Andrew Morton
2007-09-14  7:19   ` 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=8bd0f97a0709031058g3d0b5e8dodbb5fa5f35366b4f@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bryan.wu@analog.com \
    --cc=clemens.koller@anagramm.de \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.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

Powered by JetHome