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: Sun, 14 Jun 2009 12:46:25 +0200 (CEST) [thread overview]
Message-ID: <tkrat.70eb865eb2fae29b@s5r6.in-berlin.de> (raw)
There are two batches in the FireWire/ IEEE 1394 repo, one to be merged
soon, and another one which I'm not entirely sure of yet. Both batches
deal with the newer firewire drivers only, the older ieee1394 stack is
left untouched this time.
As usual, the updates can be fetched from
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git
or browsed at
http://git.kernel.org/?p=linux/kernel/git/ieee1394/linux1394-2.6.git
I will send a pull request for the 1st batch in the next few days.
Batch 1: origin..for-linus
==========================
This contains (1.) a few small fixes, (2.) a small addition to
firewire-core's sysfs ABI in order to considerably simplify udev rules
to set /dev/fw* ownership and ACLs, and (3.) preparations to add more
drivers. Of these preparations, the bigger functional enhancements were
actually already merged in 2.6.30-rc1; the remaining ones are small
functional additions and a total reorganization of files, as you can see
in the diffstat.
After the udev related change went into mainline, I will send the
respective udev rules update to linux-hotplug for inclusion into
mainline udev.
Stefan Richter (14):
firewire: core: improve check for local node
firewire: core: check for missing struct update at build time, not run time
firewire: core: add sysfs attribute for easier udev rules
firewire: share device ID table type with ieee1394
firewire: also use vendor ID in root directory for driver matches
firewire: ohci: access bus_seconds atomically
firewire: clean up includes
firewire: reorganize header files
firewire: rename source files
firewire: add parent-of-unit accessor
firewire: core: include linux/uaccess.h instead of asm/uaccess.h
firewire: core: prepare for non-core children of card devices
firewire: core: don't update Broadcast_Channel if RFC 2734 conditions aren't met
firewire: core: use more outbound tlabels
drivers/firewire/Makefile | 8 +-
drivers/firewire/{fw-card.c => core-card.c} | 25 +-
drivers/firewire/{fw-cdev.c => core-cdev.c} | 13 +-
drivers/firewire/{fw-device.c => core-device.c} | 154 ++++-
drivers/firewire/{fw-iso.c => core-iso.c} | 6 +-
.../firewire/{fw-topology.c => core-topology.c} | 24 +-
.../{fw-transaction.c => core-transaction.c} | 36 +-
drivers/firewire/core.h | 293 ++++++++
drivers/firewire/fw-device.h | 202 -----
drivers/firewire/fw-topology.h | 77 --
drivers/firewire/fw-transaction.h | 446 ------------
drivers/firewire/{fw-ohci.c => ohci.c} | 19 +-
drivers/firewire/{fw-ohci.h => ohci.h} | 6 +-
drivers/firewire/{fw-sbp2.c => sbp2.c} | 58 +-
include/linux/firewire.h | 357 +++++++++
15 files changed, 898 insertions(+), 826 deletions(-)
rename drivers/firewire/{fw-card.c => core-card.c} (97%)
rename drivers/firewire/{fw-cdev.c => core-cdev.c} (99%)
rename drivers/firewire/{fw-device.c => core-device.c} (88%)
rename drivers/firewire/{fw-iso.c => core-iso.c} (99%)
rename drivers/firewire/{fw-topology.c => core-topology.c} (97%)
rename drivers/firewire/{fw-transaction.c => core-transaction.c} (98%)
create mode 100644 drivers/firewire/core.h
delete mode 100644 drivers/firewire/fw-device.h
delete mode 100644 drivers/firewire/fw-topology.h
delete mode 100644 drivers/firewire/fw-transaction.h
rename drivers/firewire/{fw-ohci.c => ohci.c} (99%)
rename drivers/firewire/{fw-ohci.h => ohci.h} (98%)
rename drivers/firewire/{fw-sbp2.c => sbp2.c} (97%)
create mode 100644 include/linux/firewire.h
Batch 2: for-linus..for-next
============================
This contains Jay Fenlason's IPv4-over-1394 driver, which is one of the
last two or so bigger steps to make drivers/firewire/ a functional superset
of drivers/ieee1394/. Alas, the code in here has not been seen on LKML
yet, and I recently encountered some stability issues in stress tests of
the driver.
Jay Fenlason (1):
firewire: add IPv4 support
Stefan Richter (5):
firewire: net: add Kconfig item, rename driver
firewire: net: style changes
firewire: net: allow for unordered unit discovery
firewire: net: remove unused code
firewire: net: adjust net_device ops
drivers/firewire/Kconfig | 12 +
drivers/firewire/Makefile | 4 +-
drivers/firewire/core-card.c | 2 +
drivers/firewire/core-iso.c | 7 +
drivers/firewire/core.h | 87 --
drivers/firewire/net.c | 1655 ++++++++++++++++++++++++++++++++++
drivers/ieee1394/Kconfig | 2 +-
include/linux/firewire.h | 87 ++
8 files changed, 1767 insertions(+), 89 deletions(-)
create mode 100644 drivers/firewire/net.c
--
Stefan Richter
-=====-==--= -==- -===-
http://arcgraph.de/sr/
next reply other threads:[~2009-06-14 10:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 10:46 Stefan Richter [this message]
2009-06-14 10:48 ` Stefan Richter
2009-06-17 17:44 ` What's in linux1394-2.6.git? -- Part II.0/3 Stefan Richter
2009-06-17 17:47 ` What's in linux1394-2.6.git? -- Part II.1/3 Stefan Richter
2009-06-17 17:48 ` What's in linux1394-2.6.git? -- Part II.2/3 Stefan Richter
2009-06-17 17:50 ` What's in linux1394-2.6.git? -- Part II.3/3 Stefan Richter
-- strict thread matches above, loose matches on Subject: below --
2010-02-25 21:12 What's in linux1394-2.6.git? Stefan Richter
2009-11-24 17:34 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.70eb865eb2fae29b@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®