From: Mike Anderson <andmike@us.ibm.com>
To: Luben Tuikov <ltuikov@yahoo.com>
Cc: Alexis Bruemmer <alexisb@us.ibm.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aic94xx: Widens the Range of Recognized FLASH Manufactures
Date: Wed, 6 Sep 2006 15:29:57 -0700 [thread overview]
Message-ID: <20060906222957.GA17348@us.ibm.com> (raw)
In-Reply-To: <20060906062438.72183.qmail@web31810.mail.mud.yahoo.com>
Luben Tuikov <ltuikov@yahoo.com> wrote:
> Flash part discovery and interfacing can be *generalized*
> in all of the following ways:
> a) by flash part manufacturer, and
> b) by flash part interface (8 or 8/16 bit), and
> c) by how the flash part is connected to the chip.
> In other words, there exists flash part discovery and interface code
> which is flash part manufacturer agnostic, 8/16 bit part agnostic
> and connection agnostic.
>
> For the aic94xx you may not need such an enterprise level solution,
> (since you'd need to know intricate details about the HW design),
> but you can _still generalize per sequence_, in which case you'd
> not need to know anything about the manufacturer of the flash part.
> That is, you can at least generalize by manufacturer, so that
> you wouldn't need the switch() { case ...} statements at all.
>
In looking through the code I cannot see any user of the data we obtain
from the flash. It appears that we could simplify the function to just a
check for FLASHEX unless I am missing something.
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2006-09-06 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 16:20 [PATCH] aic94xx: Widens the Range of Recognized FLASH Manufactures Alexis Bruemmer
2006-09-06 6:24 ` Luben Tuikov
2006-09-06 22:29 ` Mike Anderson [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=20060906222957.GA17348@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=alexisb@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.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