From owner-freebsd-current Thu Sep 18 01:52:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA19756 for current-outgoing; Thu, 18 Sep 1997 01:52:21 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19751 for ; Thu, 18 Sep 1997 01:52:16 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id BAA27752; Thu, 18 Sep 1997 01:52:13 -0700 (PDT) Message-ID: <19970918015212.63324@hydrogen.nike.efn.org> Date: Thu, 18 Sep 1997 01:52:13 -0700 From: John-Mark Gurney To: FreeBSD Current Subject: sio aware pnp driver and resource conflict detection Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well... I was wondering if people would like for me to import my changes to make sio a PnP aware driver... I would provide a PnP flag that would prevent the card from being probed... but if I do import this code, I will need to add a temporary fix to the resource system to search attached pnp devices for resource conflicts... (prevent the modem from being attached twice which does happen and causes wierd results)... currently the pnp system doesn't prevent you from doing stupid things like configuring two pnp cards to colid with each other... and I could possibly fix this before the snap comes out... comments? -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD