On Fri, 9 Feb 96 16:29:33 EST 
 Mike Long <mike.long@analog.com> wrote:

 > If I were arguing for specifying the order in
 > /sys/arch/i386/conf/GENERIC (etc.), then I would agree.  But where the
 > order needs to be specified is in /sys/dev/isa/files.isa.  Since it's
 > part of the source tree instead of something that would usually be
 > edited, I think it's OK for the order of items in it to be
 > significant.

Well, that's certainly not how it appears to me.  For example, the first 
thing in my cfdata[] array in my ioconf.c is "scsibus* at ahb0", though 
files.isa and files.eisa are included before files.scsi.

 > No matter how we do it, I think setting the "probe priority" should be
 > done when the kernel is configured, instead of after it boots.

I'm sorry ... I just have to disagree in *certain* cases.  In the case of 
most devices, it will certainly be done via config file order, because 
the subsequent priorities won't be greater than the first cfdata match.  
However, I find it completely unacceptable that a non-obvious ordering 
error in my kernel config file causes my brand-new ethernet card to take 
a dive.  To me, that's a very serious problem that ought to be fixed.  
I'm not going to probe-prioritize *every* device ... only the ones that 
can actually be *damaged* by a rogue probe.

--------------------------------------------------------------------------
Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffett Field, CA 94035                                Pager: 415.428.6939