From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net
Subject: What's in linux1394-2.6.git?
Date: Thu, 17 Jan 2008 22:07:56 +0100 (CET) [thread overview]
Message-ID: <tkrat.99a95666fea52a5e@s5r6.in-berlin.de> (raw)
Not much, and all of it is meant to be merged post 2.6.24. The most
notable updates are fixes to firewire-ohci which fundamentally improve
isochronous reception via libdc1394 v2.
After these fixes, the most notable remaining issues with
drivers/firewire are:
- difficulties to detect SBP-2 (storage) devices on some hosts
(need to collect debug data for this ASAP),
- DV reception broken on OHCI 1.0 variants of VIA VT630x,
- IP over 1394 still not implemented/ ported.
So, distributors of kernel packages, be advised that the firewire
drivers are still not as functional as the classic ieee1394 driver
stack. As always, more details on this are captured at
wiki.linux1394.org.
I will follow up to this post with two combo patches, reflecting the
merge queue for drivers/ieee1394 and drivers/firewire respectively,
because several of the patches have not been seen on lkml yet, only on
linux1394-devel. All of the patches have been in -mm though (except for
a refresh of two small patches which happened after -rc8-mm1).
Shortlog and diffstat:
David Moore (3):
firewire: fw-ohci: Fix for dualbuffer three-or-more buffers
firewire: fw-ohci: Bug fixes for packet-per-buffer support
firewire: fw-ohci: Dynamically allocate buffers for DMA descriptors
Jay Fenlason (1):
firewire: fw-sbp2: quiet logout errors on device removal
Joe Perches (1):
ieee1394: Add missing "space"
Nick Piggin (1):
ieee1394: nopage
Rabin Vincent (1):
firewire: Fix extraction of source node id
Stefan Richter (11):
ieee1394: sbp2: prepare for s/g chaining
ieee1394: sbp2: s/g list access cosmetics
ieee1394: small cleanup after "nopage"
ieee1394: remove unused code
ieee1394: sbp2: raise default transfer size limit
ieee1394: ohci1394: don't schedule IT tasklets on IR events
firewire: fw-sbp2: refactor workq and kref handling
firewire: fw-sbp2: prepare for s/g chaining
firewire: fw-sbp2: remove unused misleading macro
firewire: fw-ohci: CycleTooLong interrupt management
firewire vs. ieee1394: clarify MAINTAINERS
MAINTAINERS | 4 +-
drivers/firewire/fw-ohci.c | 390 +++++++++++++---------
drivers/firewire/fw-sbp2.c | 84 +++--
drivers/firewire/fw-transaction.c | 2 +-
drivers/ieee1394/dma.c | 39 +--
drivers/ieee1394/ieee1394_transactions.c | 68 ----
drivers/ieee1394/ohci1394.c | 12 +-
drivers/ieee1394/raw1394.c | 4 +-
drivers/ieee1394/sbp2.c | 52 ++--
drivers/ieee1394/sbp2.h | 1 -
10 files changed, 340 insertions(+), 316 deletions(-)
--
Stefan Richter
-=====-==--- ---= =---=
http://arcgraph.de/sr/
next reply other threads:[~2008-01-17 21:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 21:07 Stefan Richter [this message]
2008-01-17 21:09 ` What's in linux1394-2.6.git? - drivers/ieee1394 queue Stefan Richter
2008-01-17 21:10 ` What's in linux1394-2.6.git? - drivers/firewire queue Stefan Richter
2008-04-02 21:52 What's in linux1394-2.6.git? Stefan Richter
2008-07-14 11:42 Stefan Richter
2008-07-14 12:37 ` Stefan Richter
2008-10-10 18:30 Stefan Richter
2008-10-13 12:18 ` Mauro Carvalho Chehab
2008-12-22 20:59 Stefan Richter
2009-03-17 21:11 Stefan Richter
2009-06-14 10:46 Stefan Richter
2009-06-14 10:48 ` Stefan Richter
2009-11-24 17:34 Stefan Richter
2010-02-25 21:12 Stefan Richter
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=tkrat.99a95666fea52a5e@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--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®