Debian Bug report logs - #584744
linux-2.6: radeonfb builtin on sparc and powerpc

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: linux-2.6: radeonfb builtin on sparc and powerpc

Date: Sun, 6 Jun 2010 11:07:51 +0200

[Message part 1 (text/plain, inline)]

Package: linux-2.6
Version: 2.6.32-10
Severity: important

Hi,

the sid kernel has radeonfb builtin on some archs:
debian/config/powerpc/config:CONFIG_FB_RADEON=y
debian/config/sparc/config:CONFIG_FB_RADEON=y

This is likely to conflict with the fb provided by the radeon drm driver
with kms.  Maybe they can be made =m instead?

Cheers,
Julien

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 584744@bugs.debian.org (full text, mbox, reply):

From: Bastian Blank <waldi@debian.org>

To: Julien Cristau <jcristau@debian.org>, 584744@bugs.debian.org

Subject: Re: Bug#584744: linux-2.6: radeonfb builtin on sparc and powerpc

Date: Sun, 6 Jun 2010 14:36:12 +0200

On Sun, Jun 06, 2010 at 11:07:51AM +0200, Julien Cristau wrote:
> the sid kernel has radeonfb builtin on some archs:
> debian/config/powerpc/config:CONFIG_FB_RADEON=y
> debian/config/sparc/config:CONFIG_FB_RADEON=y
> This is likely to conflict with the fb provided by the radeon drm driver
> with kms.  Maybe they can be made =m instead?

That is a problem. Both powerpc and sparc have no text console.

Bastian

-- 
The face of war has never changed.  Surely it is more logical to heal
than to kill.
		-- Surak of Vulcan, "The Savage Curtain", stardate 5906.5

Message #15 received at 584744@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Bastian Blank <waldi@debian.org>, 584744@bugs.debian.org

Subject: Re: Bug#584744: linux-2.6: radeonfb builtin on sparc and powerpc

Date: Tue, 29 Jun 2010 23:32:24 +0100

[Message part 1 (text/plain, inline)]

On Sun, Jun  6, 2010 at 14:36:12 +0200, Bastian Blank wrote:

> On Sun, Jun 06, 2010 at 11:07:51AM +0200, Julien Cristau wrote:
> > the sid kernel has radeonfb builtin on some archs:
> > debian/config/powerpc/config:CONFIG_FB_RADEON=y
> > debian/config/sparc/config:CONFIG_FB_RADEON=y
> > This is likely to conflict with the fb provided by the radeon drm driver
> > with kms.  Maybe they can be made =m instead?
> 
> That is a problem. Both powerpc and sparc have no text console.
> 
So do you have another suggestion to avoid the conflict?

Cheers,
Julien

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 584744@bugs.debian.org (full text, mbox, reply):

From: Sascha Silbe <sascha-debian-bugs-584744@silbe.org>

To: Debian Bug Tracking System <584744@bugs.debian.org>

Subject: linux-2.6: built-in radeonfb breaks DRM

Date: Sun, 25 Jul 2010 18:23:22 +0200

Package: linux-2.6
Severity: normal


With the built-in radeonfb and KMS enabled by default, DRM is broken on eMacs.
See e.g. FDO#27502 [1].
Disabling KMS in /etc/modprobe.d/radeon-kms.conf works around the issue.

Not sure what a real fix would be in this case - is there a framebuffer driver that can coexist with drm?


[1] https://bugs.freedesktop.org/show_bug.cgi?id=27502

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.32-5-powerpc
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Message #25 received at 584744-done@bugs.debian.org (full text, mbox, reply):

From: Ben Hutchings <ben@decadent.org.uk>

To: 584744-done@bugs.debian.org

Subject: Re: Bug#584744: linux-2.6: built-in radeonfb breaks DRM

Date: Sun, 25 Jul 2010 18:11:37 +0100

[Message part 1 (text/plain, inline)]

On Sun, 2010-07-25 at 18:23 +0200, Sascha Silbe wrote:
> Package: linux-2.6
> Severity: normal
> 
> 
> With the built-in radeonfb and KMS enabled by default, DRM is broken on eMacs.
> See e.g. FDO#27502 [1].
> Disabling KMS in /etc/modprobe.d/radeon-kms.conf works around the issue.
> 
> Not sure what a real fix would be in this case - is there a framebuffer driver that can coexist with drm?

When you enable KMS, the DRM driver is a framebuffer driver.  You are
asking for two framebuffer drivers to handle the same hardware, which is
of course impossible.

> [1] https://bugs.freedesktop.org/show_bug.cgi?id=27502

Which says exactly what I just told you (comment 7).

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.