From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: Philipp Rumpf <prumpf@suse.de>
Cc: Grant Grundler <grundler@cup.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux-cvs] grundler
Date: Thu, 2 Sep 1999 16:43:43 +0200 [thread overview]
Message-ID: <19990902164343.V493@mencheca.ch.genedata.com> (raw)
In-Reply-To: <19990902110831.I629@suse.de>; from Philipp Rumpf on Thu, Sep 02, 1999 at 11:08:31AM +0200
On Thu, Sep 02, 1999 at 11:08:31AM +0200, Philipp Rumpf wrote:
> - use of readb aso instead of gsc_readb aso
>
> gsc_readb is there for a reason.
Let me amplify on this a little. As I understand it, Linus has decreed
that readb/writeb/(etc) shall work on busses which `look like PCI'.
All other busses (zorro, podule, sbus, ...) shall define their own
*_readb/writeb/... functions. People have proposed auto-detecting which
bus is being written to and doing the right thing, but Linus disagrees.
So that's why we have gsc_readb, because GSC looks insufficiently
like PCI. Does this make sense?
--
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson
next prev parent reply other threads:[~1999-09-02 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199909012302.RAA04044@puffin.external.hp.com>
1999-09-02 9:08 ` [parisc-linux-cvs] grundler Philipp Rumpf
1999-09-02 14:43 ` Matthew Wilcox [this message]
[not found] <199909012302.RAA04026@puffin.external.hp.com>
1999-09-02 9:12 ` Philipp Rumpf
1999-09-02 17:20 ` Grant Grundler
1999-09-03 11:15 ` Philipp Rumpf
1999-09-03 16:22 ` Alex deVries
[not found] <199909012302.RAA04035@puffin.external.hp.com>
1999-09-02 8:40 ` Philipp Rumpf
1999-09-02 14:26 ` Philipp Rumpf
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=19990902164343.V493@mencheca.ch.genedata.com \
--to=matthew.wilcox@genedata.com \
--cc=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=prumpf@suse.de \
/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