Re: [9fans] detaching devices in kernel

[presotto@plan9.bell-labs.com]

[-- Attachment #1: Type: text/plain, Size: 633 bytes --]

It would be a control message to the appropriate device that in turn
calls the devtab[whatever]->config routine.  The first argument is
0 or 1, meaning unconfigure or configure.  Look at etherconfig in
bitsy/devether.c.  Its already in devtab, but noone uses it except
bitsy/devpcmcia.c.  I was going to make it a bit more universal but
it was just at the time pb was doing the pccard interface for the
pc and I got deflected.  I'ld like the pcmcia/pccard interface on the
pc's to work the same way as the one in the bitsy.  Maybe in my next
lifetime or maybe someone out there will decide its a good idea and
find the time.

[-- Attachment #2: Type: message/rfc822, Size: 2321 bytes --]

From: Ronald G Minnich <rminnich@lanl.gov>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] detaching devices in kernel
Date: Fri, 4 Oct 2002 12:38:41 -0600 (MDT)
Message-ID: <Pine.LNX.4.33.0210041237570.8559-100000@xed.acl.lanl.gov>

On Fri, 4 Oct 2002 presotto@plan9.bell-labs.com wrote:

> Once the device is notices, it's there forever.  The exception is
> the bitsy were we've started putting in stuff to take out pccards.
> We need to move that work everywhere, just haven't gotten around
> to it.

thanks for the clarification.

What would be the process by which a device is removed. A new function in
the interface (detach?) or some sequence of existing functions?

ron