9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] detaching devices in kernel
Date: Fri,  4 Oct 2002 14:33:01 -0400	[thread overview]
Message-ID: <369b4bf86b28f222780348113b23861a@plan9.bell-labs.com> (raw)

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

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.

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

From: andrey mirtchovski <andrey@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] detaching devices in kernel
Date: Fri, 4 Oct 2002 09:50:14 -0600 (MDT)
Message-ID: <20021004094303.Q71774-100000@fbsd.acl.lanl.gov>

hi,

a 9p file server can be detached by clunk-ing the connection,
however there doesn't seem to be a way one can detach a kernel-
level driver?

there's devattach, devopen, devclose, etc, but the only thing
reminiscent of 'devdetach' is 'devremove', which of course is
different...

there is detach code in the bitsy kernel for the wavelan ethernet,
but nothing in /sys/src/9/pc...

do i assume that once bound a device cannot be 'unbound'? if
devremove the answer?

andrey

             reply	other threads:[~2002-10-04 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 18:33 presotto [this message]
2002-10-04 18:38 ` Ronald G Minnich
  -- strict thread matches above, loose matches on Subject: below --
2002-10-04 18:47 presotto
2002-10-04 16:03 Russ Cox
2002-10-04 15:50 andrey mirtchovski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=369b4bf86b28f222780348113b23861a@plan9.bell-labs.com \
    --to=presotto@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).