From owner-freebsd-hardware Tue Apr 21 00:29:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14288 for freebsd-hardware-outgoing; Tue, 21 Apr 1998 00:29:26 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14231; Tue, 21 Apr 1998 07:29:08 GMT (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id JAA09833; Tue, 21 Apr 1998 09:28:37 +0200 (MET DST) Date: Tue, 21 Apr 1998 09:25:42 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Mike Smith cc: "Gregory P. Smith" , freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, Mark Willey Subject: Re: FreeBSD USB project, help requested In-Reply-To: <199804201907.MAA01295@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm not sure I follow you here. You can locate [OU]HCI devices by their > PCI class/subclass codes without needing to resort to vendor/product > IDs. > > > The final result should be according to [OU]HCI spec and chipset > > independent, I agree, but for the moment we do not have the knowledge > > nor the base to claim that it is chipset independent. > > If we cleave to the standard to start with, we'll be better off than > trying to separate the standard-compliant parts from the > chipset-specific parts later on... We are talking about the same thing, I think. It's just that I do not want to put the label 'UHCI compliant' on it when I have tested it with only one chip. Second, you need to recognise the chip to be able to apply the quirks: PIIX4: Switch on interrupt, supports power protection, etc. Three, from the code you would be able to derive that PIIX4 is only mentioned in the uhc_pci.c code to print a nice string at boot time. Four, I need alpha testers to see if, working from the UHCI spec and not the chip spec (I only found out last sunday that the PIIX4 supports power protection), I created something which is UHCI compliant. It is just too early to claim that. I am not working at a marketing company like MicroSchoft. Nick STA-ISIS, Joint Research Centre, Italy building: 27A tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message