To Do

From IEEE 1394 FireWire Wiki
(Difference between revisions)
Jump to: navigation, search
(FireWire subsystem (a.k.a. Juju driver stack): prune old done tasks)
(IEEE1394 Subsystem (a.k.a. Linux1394 driver stack): prune obsolete items)
Line 73: Line 73:
 
== IEEE1394 Subsystem (a.k.a. Linux1394 driver stack) ==
 
== IEEE1394 Subsystem (a.k.a. Linux1394 driver stack) ==
  
Note, the new FireWire subsystem in Linux 2.6.22+ (linux/drivers/firewire) is meant to replace the old IEEE 1394 subsystem (linux/drivers/ieee1394) in the long run.  New development, bug fixing, and even janitorial work should therefore concentrate on the new subsystem.  While the new subsystem is catching up on features and stability, it makes less and less sense to fix bugs of the old subsystem which the new one doesn't have.  Many of the following to-do items could therefore as well be dropped.  There is also a [http://bugzilla.kernel.org/show_bug.cgi?id=10046 meta-bug in kernel.org's bugzilla] which tracks items on which nobody is working anymore because these bugs don't exist in the new firewire drivers or should be fixed in them.  Anybody who nevertheless wants to fix any of those superseded issues is of course welcome to do so.
+
The new FireWire subsystem in Linux 2.6.22+ (linux/drivers/firewire) is meant to replace the old IEEE 1394 subsystem (linux/drivers/ieee1394).  New development, bug fixing, and even janitorial work should therefore concentrate on the new subsystem.
  
=== Documentation ===
+
There is a [http://bugzilla.kernel.org/show_bug.cgi?id=10046 meta-bug in kernel.org's bugzilla] which tracks items on which nobody is working anymore because these bugs don't exist in the new firewire drivers or should be fixed in themAnybody who nevertheless wants to fix any of those superseded issues is of course welcome to do so, if it can be done with low risk of regressions.
 
+
* Update the documentation for individual drivers on this wiki.  See [[Special:Wantedpages]].  Drivers which have different usage under Linux 2.4 and 2.6, especially sbp2, should get separate pages with information targeted towards Linux 2.4 and 2.6 users respectively.
+
 
+
=== Subsystem and core driver ===
+
 
+
* [http://bugzilla.kernel.org/show_bug.cgi?id=8403 Bug 8403]:  If several Linux boxes are plugged into the same bus, they may go multiple forced bus resets, fighting over who gets to be IRM.  Our IRM code is too pessimistic if errors happen when querying the remote IRM for its capabilities.
+
* Handle same node being connected to multiple local hosts (multi-pathing).
+
* Report driver (de)attach for information purposes (like usb does). (Why?)
+
* <s>Redo entire bus reset handling scheme.</s>  (implemented in the new FireWire subsystem)
+
* <s>[http://bugzilla.kernel.org/show_bug.cgi?id=8017 Bug 8017]:  Packet sizes can currently not exceed PAGE_SIZE, which is usually 4096 bytes.</s>  (implemented in the new FireWire subsystem)
+
* <s>Complete Bus Manager functionality.</s>  (implemented in the new FireWire subsystem)
+
* <s>Complete IRM functionality.</s> (implemented in the new FireWire subsystem)
+
* <s>1394b compatibility.</s>  (done)
+
 
+
=== sbp2 ===
+
 
+
* [http://bugzilla.kernel.org/show_bug.cgi?id=1872 Bug 1872]:  Fix serialize_io=0.
+
* [http://bugzilla.kernel.org/show_bug.cgi?id=6393 Bug 6393]:  Fix operation without physical DMA.  Implement it in a portable fashion.
+
* Implement per-node queueing options (look at sym2 driver for example).
+
* Host and device sysfs attributes.  (Do we need more than ieee1394_id?)
+
* <s>[http://bugzilla.kernel.org/show_bug.cgi?id=7794 Bug 7794]:  Implement operation with filtered physical DMA.</s>  (implemented in the new FireWire subsystem)
+
Also see sbp2's TODO list in the source.
+
 
+
=== ether1394 ===
+
 
+
* Improve reliability ([http://bugzilla.kernel.org/show_bug.cgi?id=8361 bug 8361], [http://bugzilla.kernel.org/show_bug.cgi?id=8704 bug 8704]).
+
* Fix "Waking dma ctx=0 ... processing is probably too slow", perhaps by increasing the AR DMA buffer size in ohci1394.
+
* Make it work with the bonding driver.  There are [http://marc.info/?l=linux1394-devel&m=119228969504105 changes to the bonding driver pending] to have it support IP over Infiniband.  These might take care of issues between bonding and eth1394 as well.
+
* Implement MCAP and multicast support.
+
 
+
=== ohci1394 ===
+
 
+
* <s>[http://bugzilla.kernel.org/show_bug.cgi?id=8174 Bug 8174]:  Implement atomic config ROM updates according to the procedure described in OHCI 1.1.</s>  (implemented in the new FireWire subsystem)
+
 
+
=== raw1394 ===
+
 
+
* Userspace:  Implement access to RAW1394_REQ_MODIFY_ROM in libraw1394.  This should be used instead of RAW1394_REQ_UPDATE_ROM.  Make sure that the RAW1394_REQ_MODIFY_ROM accessor can be ported to the ROM manipulation ioctl of the new firewire-core ABI, which should eventually be fully supported by libraw1394 too.
+
* [http://bugzilla.kernel.org/show_bug.cgi?id=4779 Bug 4779]:  Test and fix 32bit userland on 64bit kernel.  It appears that only address range mapping is still buggy as of Linux 2.6.23.
+

Revision as of 20:25, 24 February 2010

Linux1394 Project TODO List

This page is targeted towards users (to see which things don't work yet) as well as to developers (to pick a project which caught their interest). People new to FireWire low-level development may find our lists of specifications and books useful. Almost all FireWire related specifications are open, some of them even gratis.

See also our list of bugs at bugzilla.kernel.org for a whole lot of TODO items. There are also bugs filed in distributors' bug trackers but they are not as easy to query.


Contents


FireWire subsystem (a.k.a. Juju driver stack)

Documentation

  • Add documentation for individual drivers on this wiki. See Special:Wantedpages.
  • Derive documentation suitable for distribution with the mainline kernel sources, i.e. linux/Documentation/...?
  • Finish kerneldoc comments of all exported functions and struct types that are part of the firewire-core APIs.
  • Add a template to linux/Documentation/DocBook to pull firewire-core's kerneldoc comments in. Ideally, arrange the documentation in chapters for the userspace API, high-level API, and low-level API.

support in userspace

  • Add support in FFmpeg's libavformat.
  • Finish support by libraw1394. E.g. use OHCI timestamps when the respective kernel patch is merged. patch
  • Add support in libdc1394 v1?

firewire-core

  • Finish the transaction layer:
    • The transaction timeout needs to be counted from the time when the request hit the bus, not from the time when the request was handed over from upper layers to fw-core.
    • The transaction timeout should be taken from the SPLIT_TIMEOUT CSRs.
    • These CSRs need to be writable from the bus. It is desirable for some IIDC devices and necessary for many audio devices to be able to increase the timeout from userspace.
    • The bus manager code should ensure that all nodes have got the same timeout.
  • Implement gap count optimization based on round-trip delay measurement alternatively to the present hop count table based gap count optimization. The latter cannot be used if 1394b repeater nodes are present.
  • Implement proper FCP register support: Allow multiple clients to register for listening to FCP_COMMAND and FCP_RESPONSE. Multiplex incoming FCP frames to all listeners. This is required to use more than one AV/C device on a bus at a time. — Merged in Linux 2.6.33-rc3.
  • Design and implement an FCP transactions serializing infrastructure? See this posting for requirements.
  • Fedora bug 449252: A Panasonic AG-DV 2500 tape deck is not recognized, perhaps due to an issue with unexpected config ROM contents. — Proposed fix posted, pending for Linux 2.6.34-rc1.

firewire-ohci

  • Move all (or as much as possible) of the isochronous receive and transmit context tasklets into the IRQ handler. This is most desirable for low latency as required for audio I/O. Note, such a change may also affect other drivers. It may for example be necessary to add a tasklet to firewire-net for ARP/ broadcast/ multicast reception.
  • Bug 10935: ALi controllers don't work yet.
  • Fedora bug 228073: Apple UniNorth v1 built-in controllers do not seem to fully work.
  • Bug 8828, Fedora bug 244576: Come up with a quirk fix for NForce2. The person to do so will most certainly require direct access to this hardware. Note, the NForce2 workaround in ohci1394 is unacceptable by today's standards as it involves busy-waiting in the interrupt handler. Either we find something better for firewire-ohci, or NForce2 remains unsupported in firewire-ohci.
  • Fedora bug 492718 comments 5 and 6: Implement a workaround for Texas Instruments' erratum SLLZ012, "Errata for the 1394 Physical Layer Devices"?

firewire-sbp2

  • Move all very time-consuming work into one-off threads (mainline's slow_work, see LWN article or documentation) or convert to concurrency-managed workqueues if the latter get merged into the mainline. Move the remaining workqueue items back into the global workqueue and remove firewire-sbp2's private workqueue.
    Notably, everything which issues SCSI commands is very time consuming: __scsi_add_device, scsi_remove_device. At the moment, __scsi_add_device may seriously block firewire-sbp2's private workqueue from reconnects to other targets, while scsi_remove_device may block system-wide work in the shared workqueue.
  • Implement dynamically appended ORB lists for performance improvement. Note, the old sbp2 driver's implementation of ORB lists is very buggy (default: off) but nevertheless results in better throughput with some hardware combinations.
  • Implement SBP-3 FASTSTART protocol which is rumored to be supported by newer OxSemi bridges and INIC-2430. — None of my (Stefan R.'s) OxSemi 912/ 924/ 934/ 336 or Initio 2430 based devices' firmwares offer FASTSTART support. It seems too rare to justify to add it to the driver.
  • Implement operation without physical DMA.
  • Implement hand-over from OpenFirmware login. When an Apple PC boots from a FireWire disk, the OpenFirmware is already logged in but does apparently not log out after it loaded the kernel image. When then the kernel's firewire-sbp2 (or sbp2, for that matter) logs in, the target may deny access. This has been observed with Momobay CX-1. The old ieee1394 driver stack somehow overcomes this because of timing subtleties, but firewire-sbp2 ends up with failed login due to denied access.
  • Bug 3225: Integrate with scsi_wait_scan module?

firewire-net

  • Stabilize.
  • Implement IPv6 support as per RFC 3146.

firedtv

  • Make it work with firewire alternatively to ieee1394. Merged in kernel 2.6.33-rc1.
  • Use firewire-core's channel and bandwidth allocation function in firedtv for proper cooperation with non-FireDTV AV/C devices on the same bus.

New drivers

  • Implement an audio i/o driver to enable FFADO to run smoother with less effort. There was a Google Summer of Code project registered for it which produced some initial results.
  • Implement a V4L2 driver which exposes DV and HDV devices (IEC 61883-2...-4 camcorders, tapes, analogue tuners, TV sets) as /dev/video* devices? This has been suggested in order to offer an interface that is supported by a broad variety of multimedia application programs.
  • Implement an SBP-2 target using the in-kernel SCSI target framework as an alternative to Endpoint (Oracle's SBP-2 target implementation in userspace).
  • ohci1394_earlyinit: Add support for more architectures besides x86-64. Add interrupt handling to re-enable physical DMA after bus reset. Add hand-over of interrupt handling from ohci1394_earlyinit to firewire-ohci.


IEEE1394 Subsystem (a.k.a. Linux1394 driver stack)

The new FireWire subsystem in Linux 2.6.22+ (linux/drivers/firewire) is meant to replace the old IEEE 1394 subsystem (linux/drivers/ieee1394). New development, bug fixing, and even janitorial work should therefore concentrate on the new subsystem.

There is a meta-bug in kernel.org's bugzilla which tracks items on which nobody is working anymore because these bugs don't exist in the new firewire drivers or should be fixed in them. Anybody who nevertheless wants to fix any of those superseded issues is of course welcome to do so, if it can be done with low risk of regressions.

Personal tools