From owner-freebsd-questions@FreeBSD.ORG Thu Jul 5 13:56:33 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F04416A46C for ; Thu, 5 Jul 2007 13:56:33 +0000 (UTC) (envelope-from zhangweiwu@realss.com) Received: from bossdog.realss.com (bossdog.realss.com [211.157.108.128]) by mx1.freebsd.org (Postfix) with ESMTP id 1CDCC13C457 for ; Thu, 5 Jul 2007 13:56:33 +0000 (UTC) (envelope-from zhangweiwu@realss.com) Received: from localhost (unknown [127.0.0.1]) by bossdog.realss.com (Postfix) with ESMTP id B9A551C8008 for ; Thu, 5 Jul 2007 21:56:58 +0800 (CST) Received: from bossdog.realss.com ([127.0.0.1]) by localhost (bossdog.realss.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28926-18 for ; Thu, 5 Jul 2007 21:56:57 +0800 (CST) Received: from [218.193.55.202] (unknown [125.77.224.188]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by bossdog.realss.com (Postfix) with ESMTP id EDEA31C8007 for ; Thu, 5 Jul 2007 21:56:56 +0800 (CST) From: Zhang Weiwu To: freebsd-questions@freebsd.org In-Reply-To: <447ipf3s3r.fsf@be-well.ilk.org> References: <1183637747.9913.21.camel@esmeralda> <447ipf3s3r.fsf@be-well.ilk.org> Content-Type: text/plain; charset=utf-8 Organization: Real Softservice Date: Thu, 05 Jul 2007 21:56:11 +0800 Message-Id: <1183643772.9913.59.camel@esmeralda> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at bossdog.realss.com Subject: Re: /boot/device.hints only work for some devices in FreeBSD 6.2? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2007 13:56:33 -0000 在 2007-07-05四的 09:19 -0400，Lowell Gilbert写道： > Zhang Weiwu writes: > > > Where can I get knowledge of how device.hints works? e.g. maybe it can > > only work with device that is not managed by a PNP BIOS or maybe it only > > manage ISA devices but not PCI devices? > > It sounds like you haven't read "man device.hints". > That is a good place to start. Thanks for pointing out which TFM to read, I am feeling much more welcomed than if someone just drop me a message to RTFM. Are you referring to this section of device.hints(5)? They are most often used by ISA device drivers to specify where the driver will probe for the relevant devices, and what resources it will attempt to use. My uhci0 on pci is using IRQ 11, so does my ep0 which is on 16-bit PCMCIA slot. At first I thought this is impossible because I learnt ISA interrupt share is difficult or impossible; but later I think, maybe my ep0 is an "ISA" device (PC Card Type II slot is shrinked version of ISA slot) but the PC Card bridget is on PCI, thus it can share interrupts. The fact "cbb0" sits on PCI (in dmesg) also looks like a prove of this. Not sure if my understanding is correct. cbb0: mem 0x20822000-0x20822fff at device 2.0 on pci0 pccard0: <16-bit PCCard bus> on cbb0 Thanks again for comment:)