From owner-freebsd-hackers Tue Jul 15 12:09:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17808 for hackers-outgoing; Tue, 15 Jul 1997 12:09:05 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA17775 for ; Tue, 15 Jul 1997 12:08:42 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id BAA15546; Wed, 16 Jul 1997 01:07:24 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199707151907.BAA15546@hq.icb.chel.su> Subject: hot plugging & other sysV stuff To: terry@lambert.org (Terry Lambert) Date: Wed, 16 Jul 1997 01:07:23 +0600 (ESD) Cc: syssgm@dtir.qld.gov.au, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707151701.KAA03654@phaeton.artisoft.com> from "Terry Lambert" at Jul 15, 97 10:01:35 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Adding and removing hardware will be more difficult, but won't be > > handled by run states. It will have to be handled by device drivers. > > It's a lot easier, actually, to get arrival/departure events out > of what are, essentially, plugable interfaces (docking port, PCMCIA, > etc.). > > It can *not* be handled solely by the device drivers; a configuration > monitor is required, as is a list of possible configurations, and > what should occur as a result of leaving one configuration and > entering another. By the way, the next release of SysV from SCO will include the support for hot plug cards. They have added a driver call to transfer the system control events (before this) and now they added the configure/unconfigure functions to it. Another interesting thing they have is driver interface versioning and version dependent linking according to the specified version. By the way, they got rid of the off_t in the driver calls to make the drivers independent from it to allow it to change easily in the next versions. -SB