From: Dave Airlie <airlied@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dave Airlie <airlied@linux.ie>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
dri-devel@lists.sf.net
Subject: Re: [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off switch out of staging."
Date: Fri, 5 Feb 2010 06:39:50 +1000 [thread overview]
Message-ID: <21d7e9971002041239i5e842698pd8a775f833fc5d51@mail.gmail.com> (raw)
In-Reply-To: <20100202154450.GC27314@elte.hu>
On Wed, Feb 3, 2010 at 1:44 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Dave Airlie <airlied@linux.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.
next prev parent reply other threads:[~2010-02-04 20:39 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 2:20 [git pull] drm fixes Dave Airlie
2010-02-01 2:53 ` Dave Airlie
2010-02-02 8:17 ` [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off switch out of staging." Ingo Molnar
2010-02-02 8:25 ` Dave Airlie
2010-02-02 15:44 ` Ingo Molnar
2010-02-04 20:39 ` Dave Airlie [this message]
2010-02-04 20:46 ` Ingo Molnar
2010-02-04 21:14 ` Dave Airlie
2010-02-05 0:43 ` Dave Airlie
2010-02-05 7:32 ` Ingo Molnar
2010-02-02 8:35 ` Dave Airlie
2010-02-02 8:37 ` Dave Airlie
2010-02-02 15:42 ` Ingo Molnar
2010-02-02 15:46 ` Ingo Molnar
2010-02-02 20:34 ` Dave Airlie
2010-02-04 6:26 ` Ingo Molnar
2010-02-04 6:39 ` Dave Airlie
2010-02-04 7:36 ` Ingo Molnar
2010-02-04 7:49 ` Dave Airlie
2010-02-04 7:17 ` hung bootup with " Ingo Molnar
2010-02-04 16:48 ` Matthew Garrett
2010-02-04 17:08 ` Ingo Molnar
2010-02-04 17:15 ` Linus Torvalds
2010-02-04 17:36 ` Ingo Molnar
2010-02-04 17:36 ` Matthew Garrett
2010-02-04 17:54 ` Ingo Molnar
2010-02-04 17:59 ` Matthew Garrett
2010-02-04 18:12 ` Ingo Molnar
2010-02-04 18:15 ` Matthew Garrett
2010-02-04 18:56 ` Ingo Molnar
2010-02-04 19:00 ` Matthew Garrett
2010-02-04 19:19 ` Ingo Molnar
2010-02-04 19:28 ` Jerome Glisse
2010-02-04 20:34 ` Ingo Molnar
2010-02-04 18:30 ` Alex Deucher
2010-02-04 19:06 ` Ingo Molnar
2010-02-04 19:18 ` Alex Deucher
2010-02-04 19:24 ` Linus Torvalds
2010-02-04 19:34 ` Dave Airlie
2010-02-04 20:27 ` Ingo Molnar
2010-02-04 19:32 ` Ingo Molnar
2010-02-04 19:53 ` Jesse Barnes
2010-02-04 20:22 ` Ingo Molnar
2010-02-04 20:27 ` david
2010-02-04 20:33 ` Jesse Barnes
2010-02-04 20:57 ` Ingo Molnar
2010-02-04 20:48 ` Matthew Garrett
2010-02-04 21:05 ` Ingo Molnar
2010-02-04 21:09 ` Matthew Garrett
2010-02-05 7:56 ` Ingo Molnar
2010-02-05 8:34 ` Dave Airlie
2010-02-05 9:00 ` Ingo Molnar
2010-02-05 9:18 ` Dave Airlie
2010-02-05 10:47 ` Ingo Molnar
2010-02-04 21:23 ` Andrew Morton
2010-02-04 21:34 ` Jesse Barnes
2010-02-04 21:35 ` Dave Airlie
2010-02-06 11:10 ` Felipe Contreras
2010-02-02 8:58 ` [crash, PATCH] Revert " Domenico Andreoli
2010-02-02 11:59 ` Jerome Glisse
2010-02-02 15:11 ` Domenico Andreoli
2010-02-02 11:56 ` Jerome Glisse
2010-02-02 15:42 ` Ingo Molnar
2010-02-02 23:15 ` Jerome Glisse
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=21d7e9971002041239i5e842698pd8a775f833fc5d51@mail.gmail.com \
--to=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).