FirewireStack

Differences between revisions 3 and 4
Revision 3 as of 2010-07-08 19:53:50
Size: 1228
Editor: cpe-70-114-236-114
Comment:
Revision 4 as of 2010-07-08 19:56:47
Size: 1490
Editor: cpe-70-114-236-114
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
=== reporting test results ===
 * Please report test results to Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>
 * Subject [FIREWIRE CFT] Maverick: <tested on hardware> <works ok/does not work>
   Message: Include any data that you would like to share.

Purpose

  • To test the new Firewire stack for Maverick in as many ways and on as many different devices as possible to identify possible issues prior to the release.

Testing

mythtv firewire tester

Myth TV has a firewire test tool that might come handy.

  • install libraw1394-devel libiec61883-devel
  • gcc -Wall -o firewire_tester firewire_tester.c -liec61883 -lraw1394
  • you may need to add the following to the code #include <getopt.h>

manual testing

You may also manually test firewire

  • connect firewire disk and make sure you are able to transfer large amounts of data and the checksums are ok
  • connect digital camera and make sure dvgrab and kino works

reporting test results

  • Please report test results to Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>

  • Subject [FIREWIRE CFT] Maverick: <tested on hardware> <works ok/does not work>

    • Message: Include any data that you would like to share.

Installation

  • Nothing needs to be installed to complete this testing. The bits needed are already available in the latest Maverick kernel.

Reporting issues

Should you encounter a bug during your testing, please file a new bug for the issue ensuring that you identify the bug as being related to this Call for Testing. It is also a good idea to ping the Kernel Triager(JFo) about the new bug. This is to ensure that issues do not get lost in other bugs.

Kernel/Testing/FirewireStack (last edited 2010-07-09 08:42:00 by 212-139-208-82)