From: Pantelis Antoniou <panto@intracom.gr>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND driver
Date: Wed, 02 Jun 2004 09:08:36 +0300 [thread overview]
Message-ID: <40BD6EE4.5010805@intracom.gr> (raw)
In-Reply-To: <200406020023.02262.tglx@linutronix.de>
Thomas Gleixner wrote:
>Hi all,
>
>the NAND driver has some more new features
>
>- support for AG-AND chips (currently tested with HN29V1G91T-30)
>- bad block table support (memory and flash based)
>- a new API documentation (online version is available on MTD homepage)
>
>
Sounds interesting...
I'll test when I have some spare time available.
Just a question.
Does it do the automatic bad block skipping on read-only
like my patch did, so I can mount CRAMFS?
That is, is something like my patch still required,
or it is no longer necessary?
Regards
Pantelis
next prev parent reply other threads:[~2004-06-02 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 22:23 NAND driver Thomas Gleixner
2004-06-02 6:08 ` Pantelis Antoniou [this message]
2004-06-02 22:04 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2008-02-25 9:54 Mark Underwood
2008-02-26 9:04 ` Mark Underwood
2008-03-26 4:57 ` RadhaKumar Pulyala
2004-04-15 19:50 Thomas Gleixner
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=40BD6EE4.5010805@intracom.gr \
--to=panto@intracom.gr \
--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