[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <458913AC.7080300@s5r6.in-berlin.de>
Date: Wed, 20 Dec 2006 11:42:52 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Kristian Høgsberg <krh@...hat.com>
CC: linux-kernel@...r.kernel.org, linux1394-devel@...ts.sourceforge.net
Subject: Re: [PATCH 0/4] New firewire stack - updated patches
Kristian Høgsberg wrote:
...
> to sum up the changes:
>
> - Got rid of bitfields.
>
> - Tested on ppc, ppc64 x86-64 and x86.
>
> - ioctl interface tested on 32-bit userspace / 64-bit kernels.
>
> - ASCIIfied sources.
>
> - Incorporated Jeff Garziks comments.
>
> - Updated to work with the new workqueue API changes.
>
> - Moved subsystem to drivers/firewire from drivers/fw.
>
> plus a number of bug fixes.
Congrats. WRT the 1st, 3rd, and 5th item you are now ahead of mainline's
stack. :-)
> As mentioned last time, the stack still lacks isochronous receive
> functionality to be on par with the old stack, feature-wise. This is
> the one remaining piece of feature work kernel-side. When that is
> done, I have a couple of TODO items in user space:
Actually there are also eth1394 and pcilynx to be pulled over. Eth1394
should be quite easy to do for anybody after iso reception is settled in
your stack. Pcilynx could follow depending on developer interest. It's
increasingly rare hardware and the few old machines which have it can be
cheaply upgraded to OHCI (which performs better for SBP-2 anyway).
> - Make a libraw1394 compatibility library
Consider using libraw1394 right from the start of this porting project.
If there is only one libraw1394 (which works with raw1394 and with
fw-device-cdev), enthusiasts might have an easier time to test your stack.
> - Port libdv1394 to new isochronous API.
>
> which will allow us to move most user space applications to the new
> stack.
...
--
Stefan Richter
-=====-=-==- ==-- =-=--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists