From: ebiederman@lnxi.com (Eric W. Biederman)
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Flash driver probe/commandset separation.
Date: 03 May 2001 15:45:52 -0600 [thread overview]
Message-ID: <m3r8y6p0mn.fsf@DLT.linuxnetworx.com> (raw)
In-Reply-To: David Woodhouse's message of "Thu, 03 May 2001 22:40:13 +0100"
David Woodhouse <dwmw2@infradead.org> writes:
> ebiederman@lnxi.com said:
> > Note there is a good argument for joining the probe paths Handling
> > chip interleaving, unless we can make it simple we don't want that
> > duplicated many times.
>
> True. The build_cmd et al macros prevent duplication to a certain extent.
>
> > I'll try to have something working for 2 & 4 by the end of today. Any
> > hints on why the cmdset drivers don't compile?
>
> I changed the chip driver registration stuff. They need to have a
> struct mtd_chip_driver and set mtd->fldrv to point to it.
I'll look I currently have the simply moved the destroy function into
cfi_probe.
> And I'd like to
> make the inter_module_xxx stuff go away completely - maybe they can
> register with the code in chipreg instead, and get cfi_probe to look them
> up that way. That can wait a little while though - I'm not sure that's the
> correct approach (because they're not actually probes).
Right, but something smiliar code work. Or we could make them serve
dual duty.
Eric
next prev parent reply other threads:[~2001-05-03 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-29 18:38 Flash driver probe/commandset separation David Woodhouse
2001-04-30 15:17 ` AW: " Florian Schirmer / TayTron
2001-04-30 15:56 ` David Woodhouse
2001-04-30 15:56 ` Eric W. Biederman
2001-05-01 14:26 ` David Woodhouse
2001-04-30 17:56 ` Alice Hennessy
2001-05-02 15:33 ` Nicolas Pitre
2001-05-02 15:39 ` David Woodhouse
2001-05-03 17:32 ` Eric W. Biederman
2001-05-03 21:40 ` David Woodhouse
2001-05-03 21:45 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-02 16:22 Kári Davíðsson
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=m3r8y6p0mn.fsf@DLT.linuxnetworx.com \
--to=ebiederman@lnxi.com \
--cc=dwmw2@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