>hmmm.. Is there a reason why this would be -needed-? It wouldn't be
>hard to implement, but I would rather not have drivers dealing with a
>list whose normal state is defined as "mostly sorted"...
That's the wrong definition. The list is "sorted by probe order".
--
Justin
-
To unsubscribe fr
"Justin T. Gibbs" wrote:
> How often is the list manipulated? My guess is not very often.
Modified very infrequently... at boot, and for each hotplug insertion
or removal. It's not even read very often.
> You can allow people to read the list without taking a spinlock and
> only acquire the
>I would prefer to sort the list at probe not boot time. That makes it
>easy to reverse the order on the fly, depending on what the driver
>requests at runtime. It's SMP-friendly, because I can grab a private
>copy of the PCI device list, sort it, and scan it. You don't have to
>re-sort at ever
Linus Torvalds wrote:
> I suspect it's easier to just make the PCI layer call the probe function
> in that order, instead of working around it in your driver.
That seems like a really good idea, especially in light of the fact that
some drivers are doing (have to do?) -reverse- order PCI scanning
Aaron Tiensivu wrote:
>
> > I suspect it's easier to just make the PCI layer call the probe function
> > in that order, instead of working around it in your driver. Jeff?
>
> Would 'pci=reverse' do the trick already?
Get a unknown option warning message when using that.
--
Rafael
-
To un
> I suspect it's easier to just make the PCI layer call the probe function
> in that order, instead of working around it in your driver. Jeff?
Would 'pci=reverse' do the trick already?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL P
In article <[EMAIL PROTECTED]>,
Justin T. Gibbs <[EMAIL PROTECTED]> wrote:
>>I've a Super P6SBS motherboard with a builtin dual channel Adaptec 7890
>>Ultra II scsi controller. I'm attaching the console grab when booting
>>2.4.3-pre2. The controller BIOS is configured to boot off the disk with
>>s
>I've a Super P6SBS motherboard with a builtin dual channel Adaptec 7890
>Ultra II scsi controller. I'm attaching the console grab when booting
>2.4.3-pre2. The controller BIOS is configured to boot off the disk with
>scsi id 0 on channel B.
It looks like Doug was right to think that the function
"Justin T. Gibbs" wrote:
> Can you provide me with a dmesg from a boot with aic7xxx=verbose?
> I just tested this on a 3940AUW and the behavior was as expected.
> Perhaps you have a motherboard based controller that has no seeprom?
> I don't know how to detect flipped channels in that configuratio
>> Can you provide me with a dmesg from a boot with aic7xxx=verbose?
>> I just tested this on a 3940AUW and the behavior was as expected.
>> Perhaps you have a motherboard based controller that has no seeprom?
>> I don't know how to detect flipped channels in that configuration
>> but I'll see wha
"Justin T. Gibbs" wrote:
>
> >This is just to report on a the behavior of this driver. I've a dual
> >channel Adaptec 7895 controller. The adapter BIOS is configured to boot
> >from devices in channel B. I boot from a disk connected to channel B
> >and when the kernel loads the driver the disks
>This is just to report on a the behavior of this driver. I've a dual
>channel Adaptec 7895 controller. The adapter BIOS is configured to boot
>from devices in channel B. I boot from a disk connected to channel B
>and when the kernel loads the driver the disks from channel A are seen
>first, resu
>This is just to report on a the behavior of this driver. I've a dual
>channel Adaptec 7895 controller. The adapter BIOS is configured to boot
>from devices in channel B. I boot from a disk connected to channel B
>and when the kernel loads the driver the disks from channel A are seen
>first, resu
> from devices in channel B. I boot from a disk connected to channel B
> and when the kernel loads the driver the disks from channel A are seen
> first, resulting in the drive names changing from, say sda to sdb. This
> does not happen with 2.2.18 or 2.4.2. Is there an option to reverse the
> ord
This is just to report on a the behavior of this driver. I've a dual
channel Adaptec 7895 controller. The adapter BIOS is configured to boot
from devices in channel B. I boot from a disk connected to channel B
and when the kernel loads the driver the disks from channel A are seen
first, resulting
15 matches
Mail list logo