From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Alex Deucher <alexdeucher@gmail.com>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Date: Mon, 24 Nov 2014 16:19:16 +1100 [thread overview]
Message-ID: <1416806356.4998.18.camel@kernel.crashing.org> (raw)
In-Reply-To: <1416805719.4998.15.camel@kernel.crashing.org>
On Mon, 2014-11-24 at 16:08 +1100, Benjamin Herrenschmidt wrote:
> Hi Linus !
>
> This series fix a nasty issue with radeon adapters on powerpc servers,
> it's all CC'ed stable and has the relevant maintainers ack's/reviews.
Hrm... git request-pull can't find the commit on the server (it's been
quite a while now, maybe some mirroring issue), so didn't put the
branch name in properly.
The branch name is "merge", ie:
git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git merge
Cheers
Ben.
> Basically, some (radeon) adapters have issues with MSI addresses above
> 1T (only support 40-bits). We had powerpc specific quirk but it only
> listed a specific revision of an adapter that we shipped with our
> machines and didn't properly handle the audio function which some distros
> enable nowadays.
>
> So we made the quirk generic and fixed both the graphic and audio drivers
> properly to use it.
>
> Without that, ppc64 server machines will crash at boot with a radeon adapter.
>
> Note: This has been brewing for a while, it just needed a last respin which
> got delayed due to us moving ozlabs to a new location in town and other such
> things taking priority.
>
> Cheers,
> Ben.
prev parent reply other threads:[~2014-11-24 5:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 5:08 linuxppc-dev list <linuxppc-dev@ozlabs.org> Benjamin Herrenschmidt
2014-11-24 5:19 ` Benjamin Herrenschmidt [this message]
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=1416806356.4998.18.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=alexdeucher@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).