----- Original Message -----
>Date: Thu, 21 May 2009 13:50:23 -0400
>From: Andrew Gallatin <[email protected]>
>To: Masa Murayama <[email protected]>
>CC: Adam Chunn <[email protected]>,
> solaris driver <[email protected]>
>Subject: Re: [driver-discuss] How do I turn off the boot-archive check on
> boot-up?
>
>
>Masa Murayama wrote:
>
> > I'm developping nic drivers. I don't put my drivers into /kernel/drv
> > directory when they aren't stable. Instead of that, I load the drivers
> > into kernel space explicitly by using "modload my_driver".
>
>Does your /kernel/drv/my_driver.conf file get re-read when
>just using modload? If not, is there a way to force a re-read
>in some other way?
>
>FWIW, I do sort of the same thing as you, except I softlink my drivers
>into /kernel/drv and use add_drv / rem_drv. My method worked great
>when I started on S10GA before the evil bootarchive. But with
>bootarchive, I have problems rebooting similar to the OP. My
>workaround is to just always make sure I have a working serial
>console (which I tend to want for kmdb anway).
>
>Drew
To update .conf, I use update_drv.
I show the script below that I use to re-load atge driver for testing.
I forgot why I use modunload twice. I'm using snv-90 now and the script
works for me.
-masa
#! /bin/csh -vf
set ARCH=`isainfo -k`
set DRV=atge
set UNIT=1
set line = `modinfo | grep $DRV | head -1 | awk '{ print $1 }'`
echo $line
echo $ARCH
ifconfig $DRV$UNIT down
#sleep 1
ifconfig $DRV$UNIT unplumb
#sleep 1
modunload -i $line
#sleep 1
update_drv $DRV
#sleep 1 # XXX
modunload -i $line
#sleep 1
modload ${ARCH}/$DRV
#sleep 1
ifconfig $DRV$UNIT plumb
#sleep 1
#ifconfig $DRV$UNIT `hostname`1 up
#ifconfig $DRV$UNIT `hostname`100 up
ifconfig $DRV$UNIT `hostname`200 up
#ifconfig $DRV$UNIT `hostname`300 up
#sleep 1
tail -f /var/adm/messages
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
