All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
To: Christian Zigotzky
	<chzigotzky-KCoaydhb8eAb1SvskN2V4Q@public.gmane.org>,
	Maling list - DRI developers
	<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	Alex Deucher
	<alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: Darren Stevens <darren-YHtdit1eIT3easaKlIn9Lw@public.gmane.org>,
	Julian Margetson <runaway-zqC88Q5qmK4@public.gmane.org>,
	"R.T.Dickinson" <rtd2-kGM0oXzJM5p02iOg2JU2CQ@public.gmane.org>
Subject: Re: ATI FirePro 2260 doesn't work after the update 'drm-next-2018-12-14'
Date: Thu, 3 Jan 2019 12:03:35 +0100	[thread overview]
Message-ID: <d62eb7a9-5dd7-8052-6010-63898c51fd05@daenzer.net> (raw)
In-Reply-To: <845b2222-7014-0211-3246-55d1acc7686b-KCoaydhb8eAb1SvskN2V4Q@public.gmane.org>

On 2019-01-01 4:03 p.m., Christian Zigotzky wrote:
> Hello,
> 
> An end user reportet that his ATI FirePro 2260 doesn't work anymore with
> the latest Git kernel. We are a first level Linux support and we usually
> compile Git kernels during the merge window time for testing. After the
> update 'drm-next-2018-12-14', his ATI FirePro 2260 doesn't work anymore.
> We removed the update 'drm-next-2018-12-14' and after that he reported
> that his ATI FirePro 2260 works again.

Please ask them to file a bug report at
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Radeon
, but note that somebody will likely need to bisect the commit which
introduced it.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2019-01-03 11:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-17 23:20 [BUG/REGRESSION] Radeon HDMI casuses oops on Acube Sam460ex amcc 460ex power board Julian Margetson
2015-05-18 16:08 ` Alex Deucher
2015-05-18 17:48   ` Julian Margetson
2015-05-18 20:59     ` Alex Deucher
2015-05-18 22:41       ` Julian Margetson
2015-05-18 23:00         ` Alex Deucher
2015-05-19  0:43           ` Julian Margetson
2015-05-22 11:57           ` Julian Margetson
2015-05-31 11:48             ` Julian Margetson
2015-12-28 15:58       ` [BUG] Radeon TAHITI_vce.bin firmware " Julian Margetson
2016-01-22  0:12         ` [BUG] Radeon TAHITI_vce.bin firmware casuses oops on Acube Sam460ex amcc 460ex and other Power PC motherboards Julian Margetson
2016-01-22  5:15           ` Alex Deucher
2016-01-22  8:17             ` Christian König
2016-01-22 11:06               ` Julian Margetson
2016-01-25 12:46               ` [BUG/REGRESSION] Kernel 4.5-rc1 on Acube Sam460ex AMCC 460ex " Julian Margetson
2016-01-25 19:20                 ` Dan Williams
2016-01-25 20:35                   ` Julian Margetson
2016-01-27  1:43                     ` Dan Williams
2016-01-27 10:18                       ` Julian Margetson
2016-01-27 19:34                         ` Dan Williams
2016-01-28 10:41                           ` Julian Margetson
2016-01-28 15:47                             ` Dan Williams
2016-01-28 18:21                               ` Julian Margetson
2016-01-28 18:42                                 ` Dan Williams
     [not found]           ` <56A173FA.2090405-zqC88Q5qmK4@public.gmane.org>
2019-01-01 15:03             ` ATI FirePro 2260 doesn't work after the update 'drm-next-2018-12-14' Christian Zigotzky
     [not found]               ` <845b2222-7014-0211-3246-55d1acc7686b-KCoaydhb8eAb1SvskN2V4Q@public.gmane.org>
2019-01-03 11:03                 ` Michel Dänzer [this message]
     [not found]                   ` <d62eb7a9-5dd7-8052-6010-63898c51fd05-otUistvHUpPR7s880joybQ@public.gmane.org>
2019-01-03 19:30                     ` Christian Zigotzky

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=d62eb7a9-5dd7-8052-6010-63898c51fd05@daenzer.net \
    --to=michel-otuistvhuppr7s880joybq@public.gmane.org \
    --cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=chzigotzky-KCoaydhb8eAb1SvskN2V4Q@public.gmane.org \
    --cc=darren-YHtdit1eIT3easaKlIn9Lw@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=rtd2-kGM0oXzJM5p02iOg2JU2CQ@public.gmane.org \
    --cc=runaway-zqC88Q5qmK4@public.gmane.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.