From owner-freebsd-mobile Thu Sep 21 15:11: 6 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 1F45A37B42C for ; Thu, 21 Sep 2000 15:11:03 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA02085; Thu, 21 Sep 2000 15:11:54 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009212211.PAA02085@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@yogotech.com (Nate Williams) Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Problems getting WaveLAN device (wi0) working In-reply-to: Your message of "Thu, 21 Sep 2000 15:50:23 MDT." <200009212150.PAA07960@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 15:11:54 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > FreeBSD sometimes seems to mis-assign resources > > > already in use. > > > > This is incorrect. > > No, this is true. The mobile code sometimes screws up, and attempts to > re-use an already active resource. This doesn't constitute "mis-assigning" a resource, since when pccardd submits the resource assignment to the kernel, it will be rejected by the resource manager (and thus the resources are not mis-assigned). > And, it's not just the mobile code. > Often because FreeBSD has no driver for a particular piece of hardware, > it's unaware of the resources being used by a piece of hardware (a > CardBus controller, or an unsupported sound card), so it assumes > (wrongly) that the resources it is using are free, when in fact the > hardware is still using the resources despite the fact there is no > driver for them. This is also incorrect. FreeBSD doesn't "assign" resources for anything at this point in time, with the dubious exception of pccardd. We just use the resources that the firmware has set up. To take your cardbus controller example; these are PCI devices. Unless your firmware is faulty, they don't have resource conflicts. In the case of an unsupported sound card, it's either PCI (resources are unique and can't ever be conflicted with) or ISA-PnP (resources are owned by the 'unknown' driver and are thus known to the resource manager) or ISA (in which case the administrator is responsible for conflict resolution). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message