From owner-freebsd-hackers Fri Jan 31 15:19:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA18349 for hackers-outgoing; Fri, 31 Jan 1997 15:19:26 -0800 (PST) Received: from eldorado.net-tel.co.uk ([193.122.171.253]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA18344; Fri, 31 Jan 1997 15:19:17 -0800 (PST) From: Andrew.Gordon@net-tel.co.uk Received: (from root@localhost) by eldorado.net-tel.co.uk (8.6.12/8.6.10) id XAA21559; Fri, 31 Jan 1997 23:18:42 GMT Received: from "/PRMD=NET-TEL/ADMD=GOLD 400/C=GB/" by net-tel.co.uk (Route400-RFCGate); Fri, 31 Jan 97 23:14:24 +0000 X400-Received: by mta "eldorado" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Fri, 31 Jan 97 23:14:24 +0000 X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Fri, 31 Jan 97 23:14:22 +0000 X400-Received: by "/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"; Relayed; Fri, 31 Jan 97 23:14:22 +0000 X400-MTS-Identifier: ["/PRMD=NET-TEL/ADMD=Gold 400/C=GB/";hst:8655-970131231422-4E17] X400-Content-Type: P2-1984 (2) X400-Originator: Andrew.Gordon@net-tel.co.uk Original-Encoded-Information-Types: IA5-Text X400-Recipients: non-disclosure:; Date: Fri, 31 Jan 97 23:14:22 +0000 X400-Content-Identifier: Re: PCI LKM: How Message-Id: <"271-970131231413-CE37*/G=Andrew/S=Gordon/O=NET-TEL Computer Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS> To: se@freebsd.org Cc: hackers@freebsd.org In-Reply-To: <19970131213621.EQ13588@x14.mi.uni-koeln.de> Subject: Re: PCI LKM: How to find object file from PCI ID ... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Since USB uses very similar device IDs and will require loading and > unloading of LKMs whenever a device is connected or deconnected (USB > supports hot-pluggable devices !), I would like to find a solution > that applies to USB, too. It is for that reason, that I consider the > real and CPU times required to identify the LKM ... Note that CardBus is essentially PCI squeezed into a PCMCIA card shape, so this stuff will also affect pccardd in due course. As people have been posting in the past few days about re-writing pccardd and its config file format, perhaps this aspect needs considering sooner rather than later?