linux-kernel - Notes on migrating to the new FireWire driver stack

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <46CCA7F3.3070404@s5r6.in-berlin.de>
Date:	Wed, 22 Aug 2007 23:17:39 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	linux-kernel@...r.kernel.org
CC:	linux1394-user@...ts.sourceforge.net
Subject: Notes on migrating to the new FireWire driver stack

As many of you certainly noticed, Linux 2.6.22 has got a new FireWire
driver subsystem (nicknamed Juju) which is available as an independent
alternative to the classic IEEE 1394 subsystem.  Prompted by incoming
feedback, I now posted some basic hints on /if/ and /how/ to migrate to
the new FireWire drivers at
    http://wiki.linux1394.org/JujuMigration

In short, kernel packagers who want to provide FireWire support in Linux
2.6.22 and 2.6.23 should
  - build only the old drivers, or
  - build the old and the new drivers but blacklist the new drivers
    like described on the wiki, or
  - implement the necessary userspace integration for the new drivers.
    (That's what was done in Fedora 7.)  NB, neither does the wiki
    currently cover everything necessary for complete userspace
    integration, nor are the new drivers and respective compatibility
    extensions in FireWire userspace libraries feature-complete yet.

Kudos to all you out there who reported problems with the new drivers,
are helping us debugging the drivers, and contributed migration how-tos.
You know who you are.
-- 
Stefan Richter
-=====-=-=== =--- =-==-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/