Re: My understanding of the IDE mess, and why it does not make sense to apply the proposed patch
- To: email@example.com, firstname.lastname@example.org
- Subject: Re: My understanding of the IDE mess, and why it does not make sense to apply the proposed patch
- From: Eduard Bloch <email@example.com>
- Date: Thu, 9 Mar 2006 10:51:24 +0100
- Message-id: <20060309095124.GA30840@debian>
- In-reply-to: <Pine.LNX.4.63.0603082219130.3583@bobcat>
- References: <20060307095358.GA20724@localhost.localdomain> <firstname.lastname@example.org> <20060308230800.GA22116@localhost.localdomain> <Pine.LNX.4.63.0603082219130.3583@bobcat>
* Jurij Smakov [Wed, Mar 08 2006, 10:35:38PM]:
> the native IDE drivers set this flag during their initialization (via82cxxx
> does it through the chain of calls ide_setup_pci_device() ->
> probe_hwif_init_with_fixup() -> hwif_init()). So, if ide-generic is loaded
> last, it will pick up only the interfaces, which have not been claimed by
> any native drivers, which is the desired result. Looking at the code I
> cannot see how the native drivers can depend in any way on the ide-generic
> being loaded before them.
I suggest going a bit further and _not_ loading ide-generic if a
specific driver has been loaded successfully and found some devices.
Reason? At least on my laptop ide-generic takes too long, about 30
seconds, apparently doing probing for devices that do not exist. I can
disable it with kernel commandline parameters but it still sucks.
And I really doubt that there are that many users out there that have
their root filesystem on a disk attached with a legacy ISA controller
when they have a much faster PCI IDE interface. And PCI interfaces have
been common since... 1995 or so? (at least in the x86 world)
"After watching my newly-retired dad spend two weeks learning how to
make a new folder, it became obvious that "intuitive" mostly means
"what the writer or speaker of intuitive likes".
- Bruce Ediger, email@example.com, on X the intuitiveness of a Mac interface