From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: acrux <acrux_it@libero.it>, dri-devel@lists.freedesktop.org
Subject: Re: linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
Date: Thu, 16 Feb 2012 07:28:10 +1100 [thread overview]
Message-ID: <1329337690.3772.37.camel@pasglop> (raw)
In-Reply-To: <1329291578.2859.371.camel@thor.local>
On Wed, 2012-02-15 at 08:39 +0100, Michel Dänzer wrote:
> > > Btw, to sum up the list of Power Architecture machines with PCIE that
> > > aim to be a desktop/workstation: Apple iMac G5 (iSight), Apple PowerMac
> > > Quad G5, YDL Powerstation 2x970MP and Acube Sam460ex . And the last
> > > two, on present evidence (my attempts), aren't able to boot up if
> > > bootkernel has kms enabled.
> >
> > Which radeon card, kernel log please ?
>
> See
> http://lists.freedesktop.org/archives/dri-devel/2012-February/018792.html (start of this thread) and http://lists.freedesktop.org/archives/dri-devel/2012-February/018791.html .
Ok, so for the 460EX, I am not surprised things aren't working with KMS
& DRI2... the 460 is not cache coherent, and this is not handled by TTM
as far as I can tell.
The second case with no firmware is a bit more surprising, looks like
something bad happened on the PCI express bus or the kernel tried to
access something that the card rejected (target abort or PCIe equivalent
most likely), thus triggering a PLB error . That could be investigated a
bit more.
Note that you say this is smoe kind of "SAM460EX" card... but it claims
to be a Canyonlands in the device-tree... is that expected or do we have
yet another case of a vendor claiming to be the eval board they based
their design upon and generally screwing up in a major way ? IE. does it
indeed work with an -identical- device-tree to a canyonland and no
patches added to the machine support at all ?
Cheers,
Ben.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-02-15 20:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 1:56 linux-3.2.2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie acrux
2012-02-04 23:38 ` linux-3.3-rc2 " acrux
2012-02-07 17:32 ` Michel Dänzer
2012-02-11 20:00 ` acrux
2012-02-12 10:00 ` Michel Dänzer
2012-02-12 10:14 ` Michel Dänzer
2012-02-15 2:23 ` acrux
2012-02-15 2:50 ` Benjamin Herrenschmidt
2012-02-15 7:39 ` Michel Dänzer
2012-02-15 20:28 ` Benjamin Herrenschmidt [this message]
2012-02-16 1:05 ` acrux
2012-02-16 7:50 ` Michel Dänzer
2012-02-16 8:02 ` Benjamin Herrenschmidt
2012-02-16 8:26 ` Michel Dänzer
2012-02-16 8:52 ` Benjamin Herrenschmidt
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=1329337690.3772.37.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=acrux_it@libero.it \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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.