public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Dave Airlie <airlied@gmail.com>
Cc: David Miller <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] X doesn't work with 2.6.33 (can't find any input devices)
Date: Sat, 6 Mar 2010 20:13:35 -0500	[thread overview]
Message-ID: <20100307011335.GA5149@thunk.org> (raw)
In-Reply-To: <21d7e9971003042111n5b5145c5sd9b62b53522cfd86@mail.gmail.com>

On Fri, Mar 05, 2010 at 03:11:53PM +1000, Dave Airlie wrote:
> On Fri, Mar 5, 2010 at 2:40 PM,  <tytso@mit.edu> wrote:
> > See Linus's complaints over the nouveau driver; it's the same
> > principle; something is really broken.
> 
> Not really, this is just somebody doing something stupid one would hope,
> 
> does lshal on both kernels give similiar results?

No, it's quite different.    See attached.

--- lshal-2.6.33	     2010-03-06 10:15:44.837265508 -0500
+++ lshal-2.6.32-git4	     2010-03-06 18:45:35.782582002 -0500
@@ -1,17 +1,2446 @@
 
-Dumping 23 device(s) from the Global Device List:
+Dumping 149 device(s) from the Global Device List:
 -------------------------------------------------
...


It looks like it's fixed as of 2.6.33-git10.  Hopefully whoever fixed
it will backport it to 2.6.33-STABLE, since this will seriously screw
up anyone wanting to use 2.6.33 at least on Ubuntu; I don't know about
other distributions.

					- Ted

  reply	other threads:[~2010-03-07  1:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 15:17 [REGRESSION] X doesn't work with 2.6.33 (can't find any input devices) tytso
2010-03-03 15:20 ` David Miller
2010-03-05  4:40   ` tytso
2010-03-05  5:11     ` Dave Airlie
2010-03-07  1:13       ` tytso [this message]
2010-03-05  5:18 ` Dave Airlie

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=20100307011335.GA5149@thunk.org \
    --to=tytso@mit.edu \
    --cc=airlied@gmail.com \
    --cc=davem@davemloft.net \
    --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