[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21d7e9971002041239i5e842698pd8a775f833fc5d51@mail.gmail.com>
Date: Fri, 5 Feb 2010 06:39:50 +1000
From: Dave Airlie <airlied@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Dave Airlie <airlied@...ux.ie>, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.sf.net
Subject: Re: [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off
switch out of staging."
On Wed, Feb 3, 2010 at 1:44 AM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Dave Airlie <airlied@...ux.ie> wrote:
>
>> > It's the moving of radeom KMS out of staging after -rc6 that causes it,
>> > because it brought it into the scope of my testing:
>> >
>> > f71d018: drm/radeon/kms: move radeon KMS on/off switch out of staging.
>> >
>> > So at least on this box it's clearly not ready for mainline enablement
>> > yet. I've attached the revert patch further below.
>>
>> Its not enabled by default so reverting this doesn't make much sense.
>
> I boot allyesconfig kernels regularly, which testing method works fine with
> another 2000+ upstream drivers. (including the dozens of drivers which match
> to active hardware components on that box)
Okay this was something I wondered about, since these are *not* allyesconfig
.configs, I've generated some and CONFIG_FB_RADEON is always on here, and
you seem to not have that enabled (not that enabling it is a good idea
it is in fact
a really bad idea).
So do you have something you are running after allyesconfig to fix things? or
have you just got a config that is close enough to allyesconfig.
I'm building kernels with your .config now and boot testing them on
the full range of
hardware I have/
Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists