From: David Woodhouse <dwmw2@infradead.org>
To: Tim Hockin <thockin@sun.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: hacking - need feedback
Date: Fri, 13 Jul 2001 07:58:23 +0100 [thread overview]
Message-ID: <24388.995007503@redhat.com> (raw)
In-Reply-To: <3B4E4E40.5300A2DD@sun.com>
thockin@sun.com said:
> Would life be easier if all maps just called do_map_probe_all() and
> that would walk down the list of supported chiptypes?
Maybe, but to be honest most map driver authors know what type of chip is
going to be found. No harm in providing it, as long it remains possible to
call the other probes individually.
> cfi_probe
> jedec_probe (new)
> jedec
> amd_flash
> ram
> rom
I think there'll be an intel_probe in there too, passing control to
cfi_cmdset_000[13].
> Is it true that the code in cfi_probe.c (for doing things like
> interleave, multiple chips etc) should be common for CFI and JEDEC
> (and others?) If so, it should be shared, but it hardly makes sense
> that do_map_probe("cfi") would find jedec chips...
A lot of the required magic is actually in include/linux/mtd/cfi.h. to the
extent that the contents of cfi_probe.c end up duplicated in jedec_probe.c,
I think we should just live with it.
> Sorry I'm rambling. I'm still trying to wrap my head around the lot
> of it, and being new to the codebase, it is easy for me to say "rip
> out the old stuff" :)
Believe me, it's still easy to say "rip out the old stuff". :)
--
dwmw2
prev parent reply other threads:[~2001-07-13 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 1:26 hacking - need feedback Tim Hockin
2001-07-13 6:58 ` David Woodhouse [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=24388.995007503@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=thockin@sun.com \
/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