Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Frank Neuber <linux-mips@kernelport.de>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: borasah@gmail.com, linux-mips@linux-mips.org
Subject: Re: Au1200 and NAND Flash - K9F1G08U0A -
Date: Thu, 12 Feb 2009 14:24:50 +0100	[thread overview]
Message-ID: <1234445090.12847.151.camel@t60p> (raw)
In-Reply-To: <20090212085312.GA3914@roarinelk.homelinux.net>

Hi Manuel,
thank you for the code. It is working perfect :-)
I added this in arch/mips/au1000/common/platform.c.
1,94 MByte/s read performance.
I think it is a good idea to remove the au1550nd.c.

Thank's again,
 Frank
Am Donnerstag, den 12.02.2009, 09:53 +0100 schrieb Manuel Lauss:
> On Thu, Feb 12, 2009 at 09:40:43AM +0100, Frank Neuber wrote:
> > Thank you for this very quick answer ...
> > 
> > Am Donnerstag, den 12.02.2009, 09:17 +0100 schrieb Manuel Lauss:
> > > Here's the NAND portion of a DB1200 board support rewrite I did a while
> > > ago.  It uses gen_nand instead of the au1550nd.c driver (which seems to
> > I saw this gen_nand (plat_nand.c) never before (because it is not
> > configurable in the Makefile)
> > 
> > > only work on the Db1550 and small page devices).  It shouls also work on
> > > any Au1550 since the Au1200 has identical NAND hardware.
> > Do I understand right, this is not a handmade patch aginst
> > plat_nand.c ? 
> > 
> > I try to mix this code now with the plat_nand.c, rigth?
> 
> No no no no: this belongs in your board code (board_setup.c or whatever you
> call it).  It's nothing more than registration of a platform_device plus
> required information/callbacks for the gen_nand driver.
> 
> 	Manuel Lauss

      reply	other threads:[~2009-02-12 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19 19:13 Au1200 and NAND Flash - K9F1G08U0A - borasah
2007-05-19 19:13 ` borasah
2009-02-12  7:55 ` Frank Neuber
2009-02-12  8:17   ` Manuel Lauss
2009-02-12  8:40     ` Frank Neuber
2009-02-12  8:53       ` Manuel Lauss
2009-02-12 13:24         ` Frank Neuber [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=1234445090.12847.151.camel@t60p \
    --to=linux-mips@kernelport.de \
    --cc=borasah@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mano@roarinelk.homelinux.net \
    /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