From: "Malte Schröder" <malte@tnxip.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 4.1-rc4 display-port on radeon not working
Date: Thu, 21 May 2015 09:50:14 +0200 [thread overview]
Message-ID: <555D8E36.5080909@tnxip.de> (raw)
In-Reply-To: <CADnq5_Mu4MC9Rqx6Xp_U=b6+1VzGs6x3qvkTWkYyLCb4zYW29Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On 05/21/15 00:04, Alex Deucher wrote:
> On Wed, May 20, 2015 at 12:57 PM, Malte Schröder <malte@tnxip.de> wrote:
>> On 05/20/15 17:37, Alex Deucher wrote:
>>> On Tue, May 19, 2015 at 6:03 PM, Malte Schröder <malte@tnxip.de> wrote:
>>>> Hi,
>>>> with 4.1-rc display-port on my Tahiti XT stopped working. I used the
>>>> firmware from http://people.freedesktop.org/~agd5f/radeon_ucode/ as of
>>>> today.
>>>> Note: the display is an Asus PB278, it used to have problems with
>>>> display port negotiation, but those disappeared like a year ago.
>>>>
>>>
>>> Does booting with radeon.auxch=0 on the kernel command line in grub
>>> help? Can you bisect?
>>>
>>> Alex
>>>
>>
>> Yes, radeon.auxch=0 helps. As for bisecting, I can try, but I won't have
>> time for that until next week.
>
> No need to bisect. if auxch=0 helps, I know what commit broke it.
> Does the attached patch help?
Yes, this patch does fix the problem for me :)
>
> Alex
--
Gruß
Malte Schröder
---------------------------------------------------------------------
MalteSch@gmx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-05-21 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 22:03 4.1-rc4 display-port on radeon not working Malte Schröder
2015-05-20 15:37 ` Alex Deucher
2015-05-20 15:37 ` Alex Deucher
2015-05-20 16:57 ` Malte Schröder
2015-05-20 22:04 ` Alex Deucher
2015-05-20 22:04 ` Alex Deucher
2015-05-21 7:50 ` Malte Schröder [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=555D8E36.5080909@tnxip.de \
--to=malte@tnxip.de \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@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.