The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: felix-linuxkernel@fefe.de
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: Who is responsible for radeon driver bugs?
Date: Tue, 12 Mar 2013 17:06:35 +0100	[thread overview]
Message-ID: <20130312160635.GA5379@pd.tnic> (raw)
In-Reply-To: <20130312160249.GA32182@codeblau.de>

Let's add some more people to CC.

On Tue, Mar 12, 2013 at 05:02:49PM +0100, felix-linuxkernel@fefe.de wrote:
> The radeon driver does not work on my laptop.
> I sent a bug report here a week ago, but got no responses.
> What is the right place to send bug reports for the radeon driver?
> 
> The bug is that LVDS output does not work.  This is, according to lspci,
> a 5000M series Madison Radeon.
> 
> When I insmod the module, the screen stays in text mode and appears
> locked up.
> 
> If something is connected to the HDMI port, I get a framebuffer console
> there.  LVDS stays in broken text mode though.
> 
> When I start X, the HDMI screen turns dark and stays dark and the LVDS
> screen also stays dark and I have to reboot.
> 
> The driver loads the REDWOOD firmware OK.
> 
> Who is responsible for this?  Where do I send my bug report?
> 
> Thanks,
> 
> Felix

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-03-12 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 16:02 Who is responsible for radeon driver bugs? felix-linuxkernel
2013-03-12 16:06 ` Borislav Petkov [this message]
2013-03-12 16:16   ` Alex Deucher

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=20130312160635.GA5379@pd.tnic \
    --to=bp@alien8.de \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felix-linuxkernel@fefe.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox