public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: john stultz <johnstul@us.ibm.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][2.4 Backport] x445 usb legacy fix
Date: Tue, 20 Jul 2004 14:58:03 +0200	[thread overview]
Message-ID: <20040720125802.GA395@ucw.cz> (raw)
In-Reply-To: <20040719225104.7defc877@lembas.zaitcev.lan>

On Mon, Jul 19, 2004 at 10:51:04PM -0700, Pete Zaitcev wrote:

> On Tue, 20 Jul 2004 07:13:53 +0200
> Vojtech Pavlik <vojtech@suse.cz> wrote:
> 
> > Actually USB Legacy SMM emulation triggers problems on many many more
> > systems. The quirk does exactly the same thing the USB HCI drivers do in
> > their init code, it only does it early in the boot process, so that
> > even if the USB drivers are modules, the i8042 controller and PS/2 mouse
> > and keyboard initialization proceeds correctly.
> 
> I guessed it, but I hoped it wasn't "many more systems", but rather
> "a few", so matching would made sense.
> 
> It would be comforting to know that we ran this in 2.6 or elsewhere
> before recommending it for Marcelo. Did you guys actually ship it
> with SLES or something? For how long?

It's being shipped in SL9.1 and SLES9, since may. 

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2004-07-20 12:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20  2:07 [PATCH][2.4 Backport] x445 usb legacy fix john stultz
2004-07-20  3:06 ` Pete Zaitcev
2004-07-20  5:13   ` Vojtech Pavlik
2004-07-20  5:51     ` Pete Zaitcev
2004-07-20 12:58       ` Vojtech Pavlik [this message]
2004-07-20 17:22   ` john stultz
2004-07-20 18:17     ` Marcelo Tosatti
     [not found]       ` <20040816113314.GD14159@logos.cnet>
     [not found]         ` <1092678515.2429.4.camel@cog.beaverton.ibm.com>
2004-08-25 16:53           ` Greg KH

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=20040720125802.GA395@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /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