On Sun, May 18, 2003 at 07:45:18PM -0700, Peter Wemm wrote: > Scott Long wrote: > > Peter Wemm wrote: > > > Wilko Bulte wrote: > > > > > >>On Sun, May 18, 2003 at 02:30:52PM -0700, David O'Brien wrote: > > >> > > >>>On Sun, May 18, 2003 at 11:31:30AM +0300, Ruslan Ermilov wrote: > > >>> > > >>>>Index: sys/alpha/conf/GENERIC > > >>>>=================================================================== > > >>>>RCS file: /home/ncvs/src/sys/alpha/conf/GENERIC,v > > >>>>retrieving revision 1.159 > > >>>>diff -u -r1.159 GENERIC > > >>>>--- sys/alpha/conf/GENERIC 21 Apr 2003 16:44:04 -0000 1.159 > > >>>>+++ sys/alpha/conf/GENERIC 18 May 2003 08:26:10 -0000 > > >>>>_at__at_ -95,6 +95,7 _at__at_ > > >>>> # SCSI Controllers > > >>>> device ahc # AHA2940 and onboard AIC7xxx devices > > >>>> device isp # Qlogic family > > >>>>+device ispfw # Firmware module for Qlogic host adapt > > > > > > ers > > > > > >>>Why? The isp(4) and ispfw(4) maintainer has purposely not done this. > > >> > > >>Matt (mjacob) has learned me that having the right firmware > > >>loaded via ispfw.ko can be quite crucial to have isp operate correctly. > > >>ispfw.ko is rather big, due to the various different isp f/w > > >>revs/cards it supports. > > > > > > > > > Yes, but he had intended that it be used as a module so that it could be > > > unloaded when finished. It is only used once, to bootstrap the cards. > > > Putting it in GENERIC prevents the unload. > > > > > > > Is the isp(4) driver smart enough to load the ispfw module in a default > > install with no user intervention? I'm having trouble locating any code > > in the isp driver that would do this. > > No, it doesn't. There was a loader.conf hook to load it, just like all the > other module hooks. > > BTW; was this change made for i386 as well? It has the same isp cards that > would presumably need the same firmware loaded. The same on ia64 - most of > the older machines have ISP cards in there. > sparc64 already had both isp and ispfw in GENERIC. release/{i386,pc98}/dokern.sh do not install ispfw.ko, so no change was done here. The change was done semi-automatically -- if dokern.sh and/or drivers.conf expect thing to be present in GENERIC, it should either be present there, or it should be removed from dokern.sh and drivers.conf. I can see the point in having only a module, but then I could say I was confused by sparc64/GENERIC which has both. Cheers, -- Ruslan Ermilov Sysadmin and DBA, ru_at_sunbay.com Sunbay Software AG, ru_at_FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:08 UTC