From: David Woodhouse <dwmw2@infradead.org>
To: ebiederman@lnxi.com (Eric W. Biederman)
Cc: linux-mtd@lists.infradead.org
Subject: Re: Q: interleave logic?
Date: Thu, 03 May 2001 22:43:12 +0100 [thread overview]
Message-ID: <17354.988926192@redhat.com> (raw)
In-Reply-To: <m38zketfse.fsf@DLT.linuxnetworx.com>
ebiederman@lnxi.com said:
> What do we have nasty half incomplete interleave logic all throughout
> the cfi code?
> It looks like it could be done more cleanly with a wrapper around the
> probe code, and a wrapper around the mapping driver.
The chip driver needs to know about the interleave to some extent - it's
got to be able to deal with errors on individual chips in the interleave.
(How well we actually do that at the moment is a different question, of
course.)
I thought the macros that were introduced (by Nico?) were roughly the right
thing. If you have better suggestions, though, I'm interested.
--
dwmw2
next prev parent reply other threads:[~2001-05-03 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 19:04 Q: interleave logic? Eric W. Biederman
2001-05-03 21:43 ` David Woodhouse [this message]
2001-05-04 1:41 ` 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=17354.988926192@redhat.com \
--to=dwmw2@infradead.org \
--cc=ebiederman@lnxi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.