From: Thomas Gleixner <tglx@linutronix.de>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND Driver skeleton?
Date: Fri, 25 Feb 2005 10:39:09 +0100 [thread overview]
Message-ID: <1109324349.3033.2.camel@lap02.tec.linutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0502250931370.5525@phoenix.infradead.org>
On Fri, 2005-02-25 at 10:31, Artem B. Bityuckiy wrote:
> extabe@bredband.net wrote:
> > Hi all!
> > I will make a new NAND board driver for our own hardware. Is there a
> good and basic driver whitch I can start from?
> > I saw drivers/mtd/nand/skeleton was mentioned in the "MTD NAND Driver
> Programming Interface" manual, but I cant find the skeleton anyware.
> >
> I don't know about drivers/mtd/nand/skeleton, but IMO nand_base.c contains
> good enough "skeleton" comprised on default handlers of NAND operations.
Na, nand_base.c is not a skeleton for a board driver.
I never came around to hack the skeleton driver as I wanted to do it
with platform_device support.
Use one of the simple drivers like edb7312.c or autcpu12.c as
reference.
tglx
prev parent reply other threads:[~2005-02-25 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 23:17 NAND Driver skeleton? extabe
2005-02-25 9:31 ` Artem B. Bityuckiy
2005-02-25 9:39 ` Thomas Gleixner [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=1109324349.3033.2.camel@lap02.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.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