From owner-freebsd-hackers Mon Apr 20 12:13:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17288 for freebsd-hackers-outgoing; Mon, 20 Apr 1998 12:13:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17194; Mon, 20 Apr 1998 19:12:43 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA01295; Mon, 20 Apr 1998 12:07:47 -0700 (PDT) Message-Id: <199804201907.MAA01295@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nick Hibma cc: Mike Smith , "Gregory P. Smith" , freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, Mark Willey Subject: Re: FreeBSD USB project, help requested In-reply-to: Your message of "Mon, 20 Apr 1998 20:21:57 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Apr 1998 12:07:47 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > x Programmers interested in taking part in the project by implementing > > > > bits and pieces: > > > > x Implementation of OHCI standard (similar to UHCI) > > > > x Support for other UHCI/OHCI chipsets > > > > > > I volunteer for OHCI standard and support for the SiS 5598 OHCI chipset > > > (gee, can you guess what my motherboard has :). > > > > Get the OHCI standard and work from that. (Which is what I have done > > for my unknown Toshiba chipset.) The whole idea behind OHCI is that > > you don't have to know what sort of chipset you have, and we shouldn't > > care at all. > > Same for UHCI spec. Be aware of the fact though that without support for > separate chipsets you will not be able to figure out the way to do it > according to the specs. 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... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message