From: Pete Zaitcev <zaitcev@redhat.com>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, vojtech@suse.cz, zaitcev@redhat.com
Subject: Re: [PATCH][2.4 Backport] x445 usb legacy fix
Date: Mon, 19 Jul 2004 20:06:08 -0700 [thread overview]
Message-ID: <20040719200608.280d17a1@lembas.zaitcev.lan> (raw)
In-Reply-To: <1090289222.1388.461.camel@cog.beaverton.ibm.com>
On Mon, 19 Jul 2004 19:07:03 -0700
john stultz <johnstul@us.ibm.com> wrote:
The patch looks a little dirty in small places, e.g. the double
semicolon, the HZ/100 instead of HZ/10, space, two variables
named "base" in two blocks. I do not believe Vojtech wrote it.
He must have gotten it from someone else.
> While Greg was cautious that this method couldn't always be used, I've
> added to Vojtech's patch a boot option which allows you to specify
> "no-usb-legacy". Additionally this patch enables the "no-usb-legacy"
> option by default for x440/x445 systems.
The boot option may be useful, but in the core of the patch looks
like like a roundabout way to do things. Why don't you trigger
the meat of the quirk from, say, a DMI scan?
> + { PCI_FIXUP_FINAL, PCI_ANY_ID, PCI_ANY_ID, quirk_usb_disable_smm_bios },
This looks like a bizzare place to use as a hook. The x400 and x445
obviously have their own bridges with own IDs (their NUMA cannot
be using Intel parts, right?). So why don't hook off that?
IIRC, we don't have 7 level of initcalls in 2.4, so perhaps you
need that particular hook location. But it just looks wrong.
The routines to take ownership look sane from USB HC access
(not sane from C programming standpoint, as I mentioned above).
But in any case, it's not something I can decide. Marcelo has that
power for stock kernels, and for Red Hat kernels there's a process
which starts with Bugzilla.
-- Pete
next prev parent reply other threads:[~2004-07-20 3:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 2:07 john stultz
2004-07-20 3:06 ` Pete Zaitcev [this message]
2004-07-20 5:13 ` Vojtech Pavlik
2004-07-20 5:51 ` Pete Zaitcev
2004-07-20 12:58 ` Vojtech Pavlik
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=20040719200608.280d17a1@lembas.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®