Date: Wed, 05 Sep 2001 00:10:07 +0900 From: Katsushi Kobayashi <ikob@koganei.wide.ad.jp> To: Julian Elischer <julian@elischer.org> Cc: current@FreeBSD.ORG Subject: Re: Firewire driver available Message-ID: <3B94EECF.DA264707@koganei.wide.ad.jp> References: <3B843FF7.F9B04318@vpop.net> <200108230407.f7N47DW80946@harmony.village.org> <3B84F30B.456E9FBE@koganei.wide.ad.jp> <3B93ADEB.BD097426@koganei.wide.ad.jp> <3B93DC65.249BF99E@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I have read the specification of OHCI USB only once. I guess the OHCI specification for firewire and USB has no concern, even if both basic concept to reduce driver developing effort for each vender's products are the same. You can obtain an OHCI chipset specification from http://developer.intel.com/technology/1394/download/ohci_11.htm Of cource I refered USB driver code before rewriting the firewire driver. However, I believe it is difficult to merge USB and fiirewire OHCI. Julian Elischer wrote: > Moved to current: > > Is there any chance that the OHCI code inthe firewire driver and the OHCI > code in the USB drivers might be rationalised? > > Both seem to talk with the CAM system (from quick reading) as well, > so it might seem that there is some common functionality. > > BTW is the struct ahb_softc{} seems to suggest it's from the ahb driver.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B94EECF.DA264707>