From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: What's in linux1394-2.6.git?
Date: Thu, 25 Feb 2010 22:12:37 +0100 (CET) [thread overview]
Message-ID: <tkrat.2cce8c26bac5aa03@s5r6.in-berlin.de> (raw)
Hi all,
if there are no objections, I will see to get the following pulled into
the mainline early next week:
- three cycle timer related enhancements (hence mostly audio related):
hardware quirk fix for reliable cycle timer register access,
"quirks" module parameter for firewire-ohci, choice of clock for
local time in the read-cycle-timer ioctl,
- a few fixes (minor ones as far as I can tell),
- some refactoring like the config ROM text leaf accessor and dead
code removal.
Clemens Ladisch (2):
firewire: add fw_csr_string() helper function
firewire: ohci: work around cycle timer bugs on VIA controllers
Németh Márton (1):
firewire: make PCI device id constant
Stefan Richter (21):
firewire: core: fw_csr_string addendum
firewire: qualify config ROM cache pointers as const pointers
firewire: ohci: enable cycle timer fix on ALi and NEC controllers
firewire: get_cycle_timer optimization and cleanup
firewire: remove incomplete Bus_Time CSR support
Merge tag 'v2.6.33' for its firewire changes since last branch point
firewire: core: fix "giving up on config rom" with Panasonic AG-DV2500
firewire: core: don't fail device creation in case of too large config ROM blocks
firewire: core: increase stack size of config ROM reader
firewire: core: fix an information leak
firewire: core: rename an internal function
firewire: cdev: add more flexible cycle timer ioctl
firewire: cdev: increment ABI version number
firewire: core: change type of a data buffer
firewire: core: combine a bit of repeated code
firewire: ohci: remove unused dualbuffer IR code
firewire: ohci: reorder struct fw_ohci for better cache efficiency
firewire: ohci: use an ID table for quirks detection
firewire: ohci: add module parameter to activate quirk fixes
firewire: ohci: fix IR/IT context mask mixup
firewire: ohci: extend initialization log message
drivers/firewire/core-cdev.c | 368 +++++++++++++++----------------
drivers/firewire/core-device.c | 198 +++++++++++------
drivers/firewire/core-transaction.c | 17 +-
drivers/firewire/core.h | 2 +-
drivers/firewire/ohci.c | 364 ++++++++++--------------------
drivers/firewire/sbp2.c | 5 +-
drivers/media/dvb/firewire/firedtv-fw.c | 39 +---
include/linux/firewire-cdev.h | 40 +++-
include/linux/firewire.h | 11 +-
include/linux/pci_ids.h | 1 -
10 files changed, 493 insertions(+), 552 deletions(-)
--
Stefan Richter
-=====-==-=- --=- ==--=
http://arcgraph.de/sr/
next reply other threads:[~2010-02-25 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 21:12 Stefan Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-24 17:34 Stefan Richter
2009-06-14 10:46 Stefan Richter
2009-06-14 10:48 ` Stefan Richter
2009-03-17 21:11 Stefan Richter
2008-12-22 20:59 Stefan Richter
2008-10-10 18:30 Stefan Richter
2008-10-13 12:18 ` Mauro Carvalho Chehab
2008-07-14 11:42 Stefan Richter
2008-07-14 12:37 ` Stefan Richter
2008-04-02 21:52 Stefan Richter
2008-01-17 21:07 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.2cce8c26bac5aa03@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®