Date: Fri, 14 Apr 2000 15:47:43 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Southwell <vizion@ptialaska.net> Cc: current@FreeBSD.ORG Subject: Re: IEEE 1394 Firewire issues Message-ID: <20000414154743.A14704@orion.ac.hmc.edu> In-Reply-To: <001f01bfa660$ff02ad60$83e346c6@demon.co.uk>; from vizion@ptialaska.net on Fri, Apr 14, 2000 at 02:30:03PM -0800 References: <001f01bfa660$ff02ad60$83e346c6@demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 14, 2000 at 02:30:03PM -0800, Southwell wrote: > Ok Guys > > Help needed -- I would be grateful for any information which would be > useful for a project to provide IEEE 1394 (firewire support) on FreeBSD 4.0. > In particular to start with > the Texas Instruments OHCI compliant controller. If it cannot be done with > that chip then I will look at other controllers. > > > At this stage I do not have enough information to know whether the project > is viable. > > Someone (Mike) mentioned on the -stable list that there could be some patent > issues involved - any further information on those dangers would be > appreciated. Five minutes with google turned up http://www.1394la.com/. It should tell you what you want to know, but I think you probably need a lawyer to say anything concrete. My read is that unless they change their license IEEE 1394 is DOA outside of commercial software. The only workable solution looks like value added commercial software a la OSS or LinDVD. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. 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?20000414154743.A14704>