From owner-freebsd-hackers Tue May 5 22:56:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14931 for freebsd-hackers-outgoing; Tue, 5 May 1998 22:56:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA14866 for ; Tue, 5 May 1998 22:55:43 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA09523; Wed, 6 May 1998 05:55:56 +0200 From: Luigi Rizzo Message-Id: <199805060355.FAA09523@labinfo.iet.unipi.it> Subject: Re: ISA-PnP w\o BIOS support? To: archie@whistle.com (Archie Cobbs) Date: Wed, 6 May 1998 05:55:56 +0200 (MET DST) Cc: stefan@promo.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199805060028.RAA18956@bubba.whistle.com> from "Archie Cobbs" at May 5, 98 05:28:16 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I agree with Stefan's sentiment. It seems like this should be > the paradigm: ... > device foo0 port 0x220 irq 7 vector foointr i notice you did not put the "at isa?" specification -- is this deliberate or not ? because in this case one could differentiate between legacy isa and PnP stuff. In any case there are two major problems in my view: 1) to do automatic resource assignment you'd need to know which resources are available. Maybe the bios knows (more or less, since legacy isa devices with no driver cannot be easily detected, and the PnP detection of conflicts i am not sure how well it works), but i have no idea on how to fetch this info 2) providing a configuration in the kernel config file via "device..." entry is hard, since a single pnp device can have 8 io ports, 2 drq, 2 irq, 4 memory addresses ... how do you fit this info in the few bits available on the "device" line ? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message