From: ebiederman@lnxi.com (Eric W. Biederman)
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
Date: 13 Jul 2004 01:05:49 -0600 [thread overview]
Message-ID: <m33c3widyq.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <1089699909.8822.9.camel@imladris.demon.co.uk>
David Woodhouse <dwmw2@infradead.org> writes:
> On Mon, 2004-07-12 at 21:13 -0600, Eric W. Biederman wrote:
> > I would like to have the probe functions fill in
> > not the CmdSet number but a structure full of function pointers.
> > And of course the upper layers need to be modified to cope.
>
> > I have both Intel and AMD chips to test against. CFI and non CFI
> > all being used as motherboard BIOS chips. So I should be able
> > to catch the vast majority of problems in testing. All but the
> > delicate chip interleave case, but I should not actually be touching
> > that part of the code, and at least I am aware of the issue.
>
> And I just rewrote that part of the code too :)
That part does not look to bad...
Although there has been some error handling from cfi_cmdset_0002.c which
disturbs me. Seeing as I'm good at finding flaky NOR flash parts...
> > Does anyone have any problems with this refactoring?
>
> No, it seems like a good idea. It'll let us drop half of cfi_cmdset_0020
> too.
>
> Once I've done some testing on the new interleave / map access code I
> was planning to send an update to Linus this week. That _really_ needs
> to happen this week, so if you're going to do this then either do it
> today, or wait a month. Personally I favour the former -- the whole
> thing needs testing now anyway.
>
> Can you get to #mtd on irc.freenode.net?
I can do that, although tomorrow is a little busy. IRC isn't my best medium.
I'm just winding down for bed so and won't be back for 8 hours or so. It
looks like we both have some definite ideas so a quick chat might be helpful.
That time line is a bit challenging. My safe guess was about a week to get
everything written and tested...
Anyway I will do what I can. I don't want to even think about how
complex a network I had to setup to get IPv6 going behind our firewall
at work this morning. I stopped waiting for the sysadmins to set
things up properly....
Anyway see you in a couple of hours.
Eric
next prev parent reply other threads:[~2004-07-13 7:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 3:13 [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe Eric W. Biederman
2004-07-13 6:25 ` David Woodhouse
2004-07-13 7:05 ` Eric W. Biederman [this message]
2004-07-13 8:02 ` David Woodhouse
2004-07-13 14:23 ` Eric W. Biederman
2004-07-13 14:45 ` Thayne Harbaugh
2004-07-13 15:04 ` Eric W. Biederman
2004-07-13 15:21 ` Thayne Harbaugh
2004-07-13 15:40 ` Eric W. Biederman
2004-07-13 16:00 ` Eric W. Biederman
2004-07-14 5:44 ` Eric W. Biederman
2004-08-12 7:39 ` Eric W. Biederman
2004-07-13 15:25 ` Eric W. Biederman
2004-07-13 16:17 ` Josh Boyer
2004-08-12 7:13 ` Eric W. Biederman
2004-08-16 14:13 ` Josh Boyer
2004-07-13 16:36 ` Dan Post
2004-07-13 16:52 ` Nicolas Pitre
2004-07-13 17:33 ` Dan Post
2004-07-13 18:17 ` Nicolas Pitre
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=m33c3widyq.fsf@maxwell.lnxi.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