From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Helge Deller <deller@gmx.de>
Cc: John David Anglin <dave.anglin@bell.net>,
Alex Ivanov <gnidorah@p0n4ik.tk>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: parisc debian kernel - missing modules for C8000 - linux-image-3.10-2-parisc64-smp
Date: Fri, 6 Sep 2013 10:52:03 +0200 [thread overview]
Message-ID: <20130906085203.GA15333@alpha.franken.de> (raw)
In-Reply-To: <5228F071.4040000@gmx.de>
On Thu, Sep 05, 2013 at 10:58:25PM +0200, Helge Deller wrote:
> Maybe section 4.5 (Chips et Coherency Issues) is relevant too: ?
> The Rage128 product revealed a weakness in some motherboard chipsets in that there is no mechanism to guarantee
but radeon is not r128, iirc.
My current state is:
- parisc AGP GART code writes IOMMU entries in the wrong byte order and
doesn't add the coherency information SBA code adds
- our PCI BAR setup doesn't really work very well together with the Radeon
DRM address setup. DRM will generate addresses, which are even outside
of the connected LBA
I've hacked around both problems, but it doesn't solve the ring test
issue. I even bought an PCI Radeon card to rule out any AGP oddities,
but nothing new came out of the experiments with the PCI card.
I've started checking drivers/video/aty to see what it does with
acceleration and compare that with radeon DRM. The aty driver uses
an endian config bit DRM doesn't use, but I haven't tested whether
this makes a difference and how it is connected to the overall picture.
What I'm still wondering is whether radeon DRM really works on 64bit
big endian boxes. Is there any prove, that someone has it running ?
Is it running on any big endian boxes ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2013-09-06 8:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <521A7589.5000503@gmx.de>
2013-08-31 17:13 ` parisc debian kernel - missing modules for C8000 - linux-image-3.10-2-parisc64-smp John David Anglin
2013-08-31 17:41 ` John David Anglin
[not found] ` <108451378018002@web28j.yandex.ru>
[not found] ` <BLU0-SMTP1273DDE4A968FD3A43C55D97370@phx.gbl>
2013-09-02 6:43 ` gnidorah
2013-09-02 14:10 ` John David Anglin
2013-09-04 18:34 ` Alex Ivanov
2013-09-04 18:36 ` Alex Ivanov
[not found] ` <52278FBD.2010304@bell.net>
2013-09-04 23:58 ` John David Anglin
2013-09-05 20:58 ` Helge Deller
2013-09-06 8:52 ` Thomas Bogendoerfer [this message]
2013-09-06 14:12 ` Alex Ivanov
2013-09-06 14:53 ` Thomas Bogendoerfer
2013-09-06 14:50 ` James Bottomley
2013-09-06 16:11 ` Thomas Bogendoerfer
2013-09-06 17:14 ` James Bottomley
2013-09-07 21:08 ` John David Anglin
2013-09-17 7:23 ` Alex Ivanov
2013-09-05 9:23 ` Alex Ivanov
[not found] ` <BLU0-SMTP629706DAEF1E3714BE163097330@phx.gbl>
2013-09-05 21:15 ` Alex Ivanov
2013-09-05 21:35 ` John David Anglin
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=20130906085203.GA15333@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=gnidorah@p0n4ik.tk \
--cc=linux-parisc@vger.kernel.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.