public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Keith Packard <keithp@keithp.com>
Cc: Dave Airlie <airlied@linux.ie>, linux-kernel@vger.kernel.org
Subject: Re: [git pull] agp patches for 2.6.28-rc1.
Date: Mon, 20 Oct 2008 04:27:20 +0200	[thread overview]
Message-ID: <200810200427.21040.andres@anarazel.de> (raw)
In-Reply-To: <1224469147.5303.47.camel@koto.keithp.com>

Hi,

On Monday 20 October 2008 04:19:07 you wrote:
> On Mon, 2008-10-20 at 03:58 +0200, Andres Freund wrote:
> > Its basically only this, right?
> > Barring that I have absolutely idea about the code and all related stuff,
> > do I see it correct, that this also will result in problems if the kernel
> > doesn't have the related fix?
> Yes, on this hardware, the kernel is smashing the last few stolen
> entries with a bad value, so running a new driver against an old kernel
> will fail as well. There's not a lot we can do about this direction
> though; until we have all of this hardware management in one place,
> we're stuck trying to synchronize fixes across two code bases.
Ugly situation. So the distribution can't really do anything, because it will 
get locked either way.

> > If its really only a that small portion of hardware... At least the
> > T500/T400 series, containing the same hw as mine, from Lenovo propably is
> > not yet really wide spread (Laptop is 4weeks old or so and wasn't
> > available before).
> I haven't even received my x200s yet as they've just entered production.
> The problem here was that the prototype hardware had a different
> behavior than what is now shipping, so we didn't catch this mistake
> until the first production machines were tested.
Life is fun.

> If you care to try the above fix against your current driver sources,
> that would be helpful for us.
Will do so tomorrow morning, its 4am here ;-) and I finished the work I had to 
do tonight...


Greetings,

Andres

  reply	other threads:[~2008-10-20  2:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16  6:59 [git pull] agp patches for 2.6.28-rc1 Dave Airlie
2008-10-19 23:11 ` Andres Freund
2008-10-19 23:25   ` Dave Airlie
2008-10-19 23:44     ` Andres Freund
2008-10-20  0:19       ` Keith Packard
2008-10-20  0:34         ` Andres Freund
2008-10-20  1:00         ` Andres Freund
2008-10-20  1:04           ` Dave Airlie
2008-10-20  1:18             ` Andres Freund
2008-10-20  1:35           ` Keith Packard
2008-10-20  1:58             ` Andres Freund
2008-10-20  2:19               ` Keith Packard
2008-10-20  2:27                 ` Andres Freund [this message]
2008-10-20  9:50                 ` Andres Freund
2008-10-20 10:29                   ` Andres Freund

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=200810200427.21040.andres@anarazel.de \
    --to=andres@anarazel.de \
    --cc=airlied@linux.ie \
    --cc=keithp@keithp.com \
    --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