Linux kernel stable tree https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=master 2010-10-11T12:48:03+00:00 2010-10-11T12:48:03+00:00 Stefan Richter stefanr@s5r6.in-berlin.de 2010-10-09T22:12:20+00:00 urn:sha1:66fa12c571d35e3cd62574c65f1785a460105397 The drivers - ohci1394 (controller driver) - ieee1394 (core) - dv1394, raw1394, video1394 (userspace ABI) - eth1394, sbp2 (protocol drivers) are replaced by - firewire-ohci (controller driver) - firewire-core (core and userspace ABI) - firewire-net, firewire-sbp2 (protocol drivers) which are more featureful, better performing, and more secure than the older drivers; all with a smaller and more modern code base. The driver firedtv in drivers/media/dvb/firewire/ contains backends to both ieee1394 and firewire-core. Its ieee1394 backend code can be removed in an independent commit; firedtv as-is builds and works fine without ieee1394. The driver pcilynx (an incomplete controller driver) is deleted without replacement since PCILynx cards are extremely rare. Owners of these cards use them with the stand-alone bus sniffer driver nosy instead. The drivers nosy and init_ohci1394_dma which do not interact with either of the two IEEE 1394 stacks are not affected by the ieee1394 subsystem removal. There are still some issues with the newer firewire subsystem compared to the older one: - The rare and quirky controllers ALi M52xx, Apple UniNorth v1, NVIDIA NForce2 are even less well supported by firewire-ohci than by ohci1394. I am looking into the M52xx issue. - The experimental firewire-net is reportedly less stable than its experimental cousin eth1394. - Audio playback of a certain group of audio devices (ones based on DICE chipset with EAP; supported by prerelease FFADO code) does not work yet. This issue is still under investigation. - There were some ieee1394 based out-of-the-mainline drivers. Of them, only lisight, an audio driver for iSight webcams, seems still useful. Work is underway to reimplement it on top of firewire-core. All these remainig issues are minor; they should not stand in the way of overall better user experience of IEEE 1394 on Linux, together with a reduction in support efforts and maintenance burden. The coexistence of two IEEE 1394 kernel driver stacks in the mainline since 2.6.22 shall end now, as announced earlier this year. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> 2009-01-04T22:50:32+00:00 Stefan Richter stefanr@s5r6.in-berlin.de 2008-11-26T00:35:21+00:00 urn:sha1:b17a55096071898454d7b5b6fb30cca7faedf9f1 These are never modified. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> 2008-07-14T11:06:02+00:00 Stefan Richter stefanr@s5r6.in-berlin.de 2008-05-19T20:07:28+00:00 urn:sha1:055a7da0bb7b14f2f5009bf1c486a6e965e1e7ac This prepares video1394 for removal of the BKL (big kernel lock): It allows video1394_open() to be called while video1394_init_module() is still in progress. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> 2007-07-09T22:07:41+00:00 Stefan Richter stefanr@s5r6.in-berlin.de 2007-06-24T13:31:54+00:00 urn:sha1:53c96b41742a2dadd14e65c23fc119f2a2fd9f05 Based on patch "the scheduled removal of RAW1394_REQ_ISO_{SEND,LISTEN}" from Adrian Bunk, November 20 2006. This patch also removes the underlying facilities in ohci1394 and disables them in pcilynx. That is, hpsb_host_driver.devctl() and hpsb_host_driver.transmit_packet() are no longer used for iso reception and transmission. Since video1394 and dv1394 only work with ohci1394 and raw1394's rawiso interface has never been implemented in pcilynx, pcilynx is now no longer useful for isochronous applications. raw1394 will still handle the request types but will complete the requests with errors that indicate API version conflicts. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> 2007-04-29T22:00:28+00:00 Stefan Richter stefanr@s5r6.in-berlin.de 2007-03-05T02:06:23+00:00 urn:sha1:afd6546d8d2d8ba1dbe1d2508baf81eebdca3d79 Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> 2007-04-29T22:00:27+00:00 Stefan Richter stefanr@s5r6.in-berlin.de 2007-03-05T02:05:32+00:00 urn:sha1:ef8153348f82688af87e19d594162ca81741fe6a Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> 2006-12-07T20:20:30+00:00 Stefan Richter stefanr@s5r6.in-berlin.de 2006-09-07T23:30:04+00:00 urn:sha1:0e930f437eab6db6de5e3f0efbf10dafffca401a struct hpsb_highlevel's struct module *owner is neither used by the IEEE 1394 core nor set by any of the in-tree drivers or the two out-of-tree highlevel drivers I know about (dfg1394, mem1394) --- nor is this member documented. An unscheduled removal seems acceptable. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> 2006-07-03T16:02:29+00:00 Stefan Richter stefanr@s5r6.in-berlin.de 2006-07-03T16:02:29+00:00 urn:sha1:de4394f13cc843fae2a3ba2df752ee20e6e779a8 Remove unnecessary includes, add missing includes. Use forward type declarations for some structs. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> Signed-off-by: Ben Collins <bcollins@ubuntu.com> 2006-07-03T16:02:28+00:00 Stefan Richter stefanr@s5r6.in-berlin.de 2006-07-03T16:02:28+00:00 urn:sha1:e1d118f16dca0f54faba3e8dd5b6adbbf7ac68c8 Adjust tabulators, line wraps, empty lines, and comment style. Update comments in ieee1394_transactions.h and highlevel.h. Fix typo in comment in csr.h. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> Signed-off-by: Ben Collins <bcollins@ubuntu.com> 2005-04-16T22:20:36+00:00 Linus Torvalds torvalds@ppc970.osdl.org 2005-04-16T22:20:36+00:00 urn:sha1:1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!