Date: Fri, 02 Feb 2001 01:15:53 -0800 From: Peter Wemm <peter@netplex.com.au> To: Warner Losh <imp@harmony.village.org> Cc: Dag-Erling Smorgrav <des@ofug.org>, mobile@FreeBSD.ORG Subject: Re: NEWCARD success story Message-ID: <200102020915.f129FrW23978@mobile.wemm.org> In-Reply-To: <200102020227.f122Rh935286@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh wrote:
> In message <200102020213.f122D8W20029@mobile.wemm.org> Peter Wemm writes:
> : Thinking about it some more, network interface config is one of the few
> : things that we actually need a user hookable notification on. ATA and CAM
> : can (and should) self rescan - no userland intervention is required to get
> : those up and running. The same pretty much goes for sio devices. What els
e
> : is there?
>
> Well, that's not quite right. CAM doesn't do a rescan right now. sio
> also might want to have ppp come up.
Yes, CAM does have rescan support. umass.c triggers it. The pccard/cardbus
drivers have just not picked up the magic code.
> I also have a program with oldcard that burns CF cards when you insert
> them into a machine specially dedicated to the purpose.
>
> It has to be a generic device thing rather than a specific network
> thing.
I didn't say we should only do the network socket, but I did observe that
the network socket would cover 99% of the cases of what people need right
now. It would be trivially easy to get that up and running right now while
we decide how to implement generic device add/remove notification support.
(remember, network interfaces are not "devices" in the kernel or /dev, so
there are no devfs hooks we can check)
There are exactly two sorts of things that have insert/remove in pccard.conf
right now.. network cards needing pccard_ether, and scsi cards that do not
have the cam rescan calls and callbacks (see umass.c:umass_cam_rescan() -
it is pretty easy too).
Besides, it is a bug^H^H^Hoversight that the routing socket doesn't notify
on interface add/remove right now anyway.. the routing socket messages were
done in the days of static interface configuration and the sole on/off
change was administrative up or down. Now we have interface add/removal on
a regular basis and network daemons should be able to find out about this.
An all-singing, all-dancing generic system would probably be able to monitor
several different sources of events anyway, be it somebody doing a chmod on
a node in a devfs /dev, or a sio or CF card being added/removed, etc.
I know, send patches... (and I just might :-)
Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102020915.f129FrW23978>