mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Kristian Høgsberg" <krh@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/4] New firewire stack - updated patches
Date: Wed, 20 Dec 2006 11:42:52 +0100	[thread overview]
Message-ID: <458913AC.7080300@s5r6.in-berlin.de> (raw)
In-Reply-To: <20061220005822.GB11746@devserv.devel.redhat.com>

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/

  reply	other threads:[~2006-12-20 10:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20  0:58 Kristian Høgsberg
2006-12-20 10:42 ` Stefan Richter [this message]
2006-12-20 17:35   ` Kristian Høgsberg
2006-12-20 18:57     ` Stefan Richter
2006-12-20 20:06       ` Kristian Høgsberg
2006-12-20 21:52         ` Stefan Richter
2006-12-20 23:01           ` Stefan Richter
2006-12-20 20:34       ` Stefan Richter
2006-12-20 15:29 ` Pieter Palmers
2006-12-20 18:39   ` Kristian Høgsberg
2006-12-21 23:03 ` Stefan Richter
2006-12-21 11:47 Duncan Beadnell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=458913AC.7080300@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=krh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®