On Fri, 10 Mar 2000, Eric Youngdale wrote:
>
> > Maybe(?) there is another approach... Please forgive my naivet�.
> > The real problem is that fact that anything not serviced by the boot SCSI
> > driver is subject to the SD_EXTRA_DEVS limit. For example, if my box has
> > an
> > Adaptec on the motherboard (w/ boot device attached), anything on the
> > Symbios/Qlogic/XX adapters would be subject to SD_EXTRA_DEVS.
> >
> > What kind of code gymnastics would be required to scan _all_ the SCSI
> > drivers installed before saying "this is all the devices we found"?
> > Extend the initial scan to include the buses attached to additional
> > adapters.
>
> Let me study the code a bit - I believe it would be a more minor
> re-arrangement to attach the devices after all of the compiled in drivers
> are scanned, but I won't commit to that without looking. I would feel more
> comfortable doing this for 2.3 - it would be Alan's call what is safe enough
> to go in 2.2, and until I have a rough idea of what changes are needed it
> would be hard to make a call on this.
I took a look, and offhand I don't see room for improvement. The
way things work now, we scan all of the busses for compiled in drivers,
and once this is done we size the arrays and connect them to upper level
drivers. Unless I am missing something here, it will only be for drivers
loaded as a result of a module load that the SD_EXTRA_DEVS will come into
play.
-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
