From: David Woodhouse <dwmw2@infradead.org>
To: "Kári Davíðsson" <kd@flaga.is>
Cc: mtd@infradead.org
Subject: Re: Abstractation
Date: Fri, 09 Mar 2001 13:44:28 +0000 [thread overview]
Message-ID: <11524.984145468@redhat.com> (raw)
In-Reply-To: <EADB10BAC266A14A85ECBF8686A73E310A910E@kolkrabbi.flaga.is>
kd@flaga.is said:
> I need to add a cfi_cmdset_0003 to support a Intel chip that we have
> in our boards.
You'll probably find it works if you just hack cfi_probe to invoke
cfi_cmdset_0001 instead. See the list archives - this came up quite
recently.
> Why does I as the cmdset writer have to know all this stuff about the
> buswith, number of chips etc?
You need to handle multiple chips interleaved on a wide bus anyway.
Numchips isn't too difficult and by doing it at the command set level we
eliminate the need for external wrapper functions which make multiple calls
to the single-chip version of the access function.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-03-09 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 13:33 Abstractation Kári Davíðsson
2001-03-09 13:44 ` David Woodhouse [this message]
2001-03-09 14:46 ` Abstractation Florian Schirmer / TayTron
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=11524.984145468@redhat.com \
--to=dwmw2@infradead.org \
--cc=kd@flaga.is \
--cc=mtd@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