From owner-freebsd-hackers Mon Jan 1 08:51:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA26728 for hackers-outgoing; Mon, 1 Jan 1996 08:51:48 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA26723 for ; Mon, 1 Jan 1996 08:51:45 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0tWn7U-0000zcC; Mon, 1 Jan 96 10:29 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tWn2q-000C1dC; Mon, 1 Jan 96 10:25 WET Message-Id: Date: Mon, 1 Jan 96 10:25 WET To: hackers@freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Mon Jan 1 1996, 10:25:08 CST Subject: Re: FreeBSD, Zappa & PCI Sender: owner-hackers@freebsd.org Precedence: bulk [0]Is this a serious problem? What does the class=bridge[not supported] [0]mean? [1]The confusing `not supported' message has been changed meanwhile into [1]`no driver assigned'. This is not a problem, since the BIOS usually [1]has initialized the device, it's only telling that FreeBSD doesn't [1]provide any handling of its own for it. Perhaps we should change the message to "using hardware defaults" or "no special handling" or just don't say anything at all if we aren't doing anything special. Both "Not Supported" and "No driver assigned" sound a lot like something isn't supported or configured properly (ie, perhaps the kernel could not find the driver on disk, etc.). This looks like a question-generator to me. Frank Durda IV |New 1996 quotes being loaded... ...letni!rwsys!nemesis!uhclem |