[lkml]   [2002]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] 2.5.5-pre1 IDE cleanup 9
On Fri, 22 Feb 2002, Greg KH wrote:

> On Thu, Feb 21, 2002 at 10:01:14PM +0100, Gérard Roudier wrote:
> >
> > I have investigated it, but it didn't seem to allow the boot order set by
> > user in sym53c8xx HBA NVRAMs to be applied, breaking as a result all
> > systems depending on it. Since it is transparently handled by the
> > sym53c8xx driver and just behaves _as_ user expects, my guess is that
> > numerous users may just have their system relying on it.
> But as Jeff noted, it is _required_ for PCI hotplug functionality.
> Because allmost all of the SCSI drivers are not using this over 2 year
> old interface, they will not work properly on large machines that now
> support PCI hotplug. Much to my dismay.
> Init order works off of PCI probing order. If the network people can
> handle this, the SCSI people can :)

Does INT13/INT19 Bios call mean anything?

Last time I checked, ethernet devices are not invoked here but I could be
wrong given PXE.

> > Propose a kernel API that does not break more features that it adds and I
> > will be glad to use it.
> Huh? This is not a new API. What does it break for you?

The problem is how do you deal with multiple HOSTs given there drivers are
not (have not checked lately) capable of discrete HOST addition and

SCSI/ATA share the same problem IIRC, the host/chipset drivers load all
the device hosts who match that driver code.

What am I missing?


Andre Hedrick
Linux Disk Certification Project Linux ATA Development

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.128 / U:39.216 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site