From owner-freebsd-mobile Mon Apr 12 7:44:24 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [210.74.174.3]) by hub.freebsd.org (Postfix) with ESMTP id 1925B14E0C for ; Mon, 12 Apr 1999 07:44:10 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id WAA00575 for freebsd-mobile@freebsd.org; Mon, 12 Apr 1999 22:42:04 +0800 (CST) (envelope-from robinson) Date: Mon, 12 Apr 1999 22:42:04 +0800 (CST) From: Michael Robinson Message-Id: <199904121442.WAA00575@netrinsics.com> To: freebsd-mobile@freebsd.org Subject: new-bus/newconfig (was: Any success) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson writes: >The reason device attachment points are not specified in the config file >is that I don't think the user should need to care how the hardware in >their machine works in order to get FreeBSD working. There's that "should" again. I think people generally agree that it would be nice if users did not need to know anything about their hardware to get FreeBSD working. I think people also generally agree that there are many common situations where users will not, in fact, be able to get FreeBSD working if they do not know how their hardware works, or if they are not able to communicate that knowledge to the device configuration code. I don't think people generally understand, though, exactly how new-bus addresses the manual configuration problem, nor do people generally understand exactly how newconfig handles the automatic configuration problem. Could we get specific details on these specific points from the respective designers? -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message