Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@linuxcare.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] FB cleanups
Date: 17 Apr 2001 20:04:53 +0200	[thread overview]
Message-ID: <d366g3xv0a.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: Alan Cox's message of "Fri, 13 Apr 2001 19:11:52 +0100 (BST)"

>>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

>> 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.

Alan> And ISA is noticable for the fact it doesnt behave quite like
Alan> PCI. You use readb/readw/readl on ISA.

Yes, except that ISA has stronger semantics than PCI.

>> Using writeb on a gsc is misleading everybody else who reads the
>> code into believing that it's a PCI device.

Alan> Rubbish.

Unfortunately not, look at the fb code to see the chaos.

Jes

  reply	other threads:[~2001-04-17 18:04 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
2001-04-13 18:11               ` Alan Cox
2001-04-17 18:04                 ` Jes Sorensen [this message]
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=d366g3xv0a.fsf@lxplus015.cern.ch \
    --to=jes@linuxcare.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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