From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: APUS and IOs question
Date: Tue, 07 Nov 2006 07:14:48 +1100 [thread overview]
Message-ID: <1162844088.28571.319.camel@localhost.localdomain> (raw)
In-Reply-To: <454F5259.3020107@hogyros.de>
On Mon, 2006-11-06 at 16:18 +0100, Simon Richter wrote:
> Hi,
>
> Benjamin Herrenschmidt wrote:
>
> > Somebody who understands APUS around ?
>
> I have one, but I don't understand all of it. :-)
>
> > In include/asm-ppc/io.h, we have a special definition of the PCI IO
> > accessors readw,writew,readl and writel for APUS that don't do byteswap
> > and also don't do barriers.
>
> APUS PCI is weird, to say the least. The PCI extension is basically
> built to accomodate a single PCI device, which happens to be a Permedia2
> graphics chip that allows byte-swapped mappings of both register and
> framebuffer space and is never told to do DMA because nobody knows what
> kind of interesting effects that would have, so the only synchronisation
> that is needed is between accesses to the framebuffer and the GPU.
>
> That, and that the 604e+ probably doesn't reorder accesses that much
> anyway that the barriers would do any good here. :-)
Still, it annoys me to have an APUS-specific definition of accessors
that would otherwise be common to everybody...
Anyway, I decided not to change asm-ppc/io.h, so this will only become
an issue if we ever move APUS over to arch/powerpc
Ben.
next prev parent reply other threads:[~2006-11-06 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 22:55 APUS and IOs question Benjamin Herrenschmidt
2006-11-06 15:18 ` Simon Richter
2006-11-06 16:45 ` Segher Boessenkool
2006-11-06 20:14 ` Benjamin Herrenschmidt [this message]
[not found] ` <454F5E44.4040301@genesi-usa.com>
[not found] ` <1162844529.28571.327.camel@localhost.localdomain>
[not found] ` <455081AC.3010301@hogyros.de>
[not found] ` <1162931605.28571.491.camel@localhost.localdomain>
2006-11-09 14:34 ` Simon Richter
2006-11-09 22:48 ` Benjamin Herrenschmidt
2006-11-10 1:39 ` Geert Uytterhoeven
2006-11-10 2:02 ` Roman Zippel
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=1162844088.28571.319.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=Simon.Richter@hogyros.de \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.