From: Jes Sorensen <jes@linuxcare.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] FB cleanups
Date: 13 Apr 2001 18:48:28 +0200 [thread overview]
Message-ID: <d3eluwrbj7.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: Matthew Wilcox's message of "Thu, 12 Apr 2001 00:36:06 +0100"
>>>>> "Matthew" == Matthew Wilcox <matthew@wil.cx> writes:
Matthew> On Thu, Apr 12, 2001 at 12:56:01AM +0200, Jes Sorensen wrote:
>> Then Linus changed his mind. You are still *only* supposed to use
>> readb/writeb on PCI (and possible ISA) on PCI like devices.
Matthew> I've heard this before. But no-one ever came up with an
Matthew> example of what _was_ `PCI-like'. Since right now our writeb
Matthew> is #defined to gsc_writeb, that leads me to believe GSC is
Matthew> sufficiently PCI-like.
Well time to go study the bus behaviors and compare them then. How
does gsc behave wrt cache coherency, read-around-write, write ordering
etc etc.
Using writeb on a gsc is misleading everybody else who reads the code
into believing that it's a PCI device.
Jes
next prev parent reply other threads:[~2001-04-13 16:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 20:13 [parisc-linux] FB cleanups Matthew Wilcox
2001-04-11 20:30 ` Jes Sorensen
2001-04-11 20:34 ` Matthew Wilcox
2001-04-11 20:43 ` Jes Sorensen
2001-04-11 22:51 ` Matthew Wilcox
2001-04-11 22:56 ` Jes Sorensen
2001-04-11 23:00 ` Alan Cox
2001-04-12 18:48 ` Jes Sorensen
2001-04-13 7:04 ` Grant Grundler
2001-04-13 12:52 ` Alan Cox
2001-04-13 17:52 ` Grant Grundler
2001-04-13 18:13 ` Alan Cox
2001-04-11 23:36 ` Matthew Wilcox
2001-04-13 16:48 ` Jes Sorensen [this message]
2001-04-13 18:11 ` Alan Cox
2001-04-17 18:04 ` Jes Sorensen
2001-04-17 18:22 ` Matthew Wilcox
2001-04-17 19:57 ` Alan Cox
2001-04-13 7:02 ` Grant Grundler
2001-04-13 16:49 ` Jes Sorensen
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=d3eluwrbj7.fsf@lxplus015.cern.ch \
--to=jes@linuxcare.com \
--cc=matthew@wil.cx \
--cc=parisc-linux@parisc-linux.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