From: "Andrew Chew" <AChew@nvidia.com>
To: "Jeff Garzik" <jgarzik@pobox.com>, "Juerg Billeter" <juerg@paldo.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Broken nForce2 IDE module loading via hotplug
Date: Mon, 16 May 2005 12:54:28 -0700 [thread overview]
Message-ID: <DBFABB80F7FD3143A911F9E6CFD477B00604C7BC@hqemmail02.nvidia.com> (raw)
I think the kernel config option to disable the generic entry is a good
idea. Jeff, want me to submit a patch for this?
-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Friday, May 13, 2005 11:05 AM
To: Juerg Billeter
Cc: Andrew Chew; linux-kernel@vger.kernel.org
Subject: Re: Broken nForce2 IDE module loading via hotplug
Juerg Billeter wrote:
> Hi
>
> (please cc me)
>
> The sata_nv patch[1] (merged in 2.6.11-rc4) to enable future NVIDIA
SATA
> pci ids catches all NVIDIA pci devices with the ide class. This breaks
> automatic module loading for e.g. nForce2 ide controllers and thereby
> renders nForce systems loading modules already in initramfs/initrd via
> hotplug/coldplug non-bootable.
>
> I don't know what solutions are possible besides reverting. Is it
> somehow possible to influence the order of the modules.pcimap file,
i.e.
> moving the generic matching lines below the more specific ones?
It might be fair to add a kernel config option to disable the generic
entry.
Jeff
next reply other threads:[~2005-05-16 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 19:54 Andrew Chew [this message]
2005-05-16 19:58 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 20:06 Andrew Chew
2005-05-25 13:34 ` Jeff Garzik
2005-06-06 16:01 ` Bartlomiej Zolnierkiewicz
2005-04-16 16:33 Juerg Billeter
2005-05-13 18:04 ` Jeff Garzik
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=DBFABB80F7FD3143A911F9E6CFD477B00604C7BC@hqemmail02.nvidia.com \
--to=achew@nvidia.com \
--cc=jgarzik@pobox.com \
--cc=juerg@paldo.org \
--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
all inboxes | Powered by JetHome®