![Stefan Richter](/assets/img/avatar_default.png)
This adds debug printks for asynchronous transmission and reception and for self ID reception. They can be enabled at module load time, and at runtime via /sys/module/firewire_ohci/parameters/debug. Signed-off-by: Jarod Wilson <jwilson@redhat.com> Also added: Logging of interrupt event codes and of cancelled AT packets. The code now depends on a Kconfig variable. This makes it easier to build firewire-ohci without the feature or to make it an option in the future. The variable is currently hidden and always on. This feature inflates firewire-ohci.ko by 7 kB = 27% on x86-64 and by 4 kB = 23% on i686. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
77 lines
2.6 KiB
Text
77 lines
2.6 KiB
Text
comment "An alternative FireWire stack is available with EXPERIMENTAL=y"
|
|
depends on EXPERIMENTAL=n
|
|
|
|
config FIREWIRE
|
|
tristate "IEEE 1394 (FireWire) support - alternative stack, EXPERIMENTAL"
|
|
depends on EXPERIMENTAL
|
|
select CRC_ITU_T
|
|
help
|
|
This is the "Juju" FireWire stack, a new alternative implementation
|
|
designed for robustness and simplicity. You can build either this
|
|
stack, or the classic stack (the ieee1394 driver, ohci1394 etc.)
|
|
or both. Please read http://wiki.linux1394.org/JujuMigration before
|
|
you enable the new stack.
|
|
|
|
To compile this driver as a module, say M here: the module will be
|
|
called firewire-core. It functionally replaces ieee1394, raw1394,
|
|
and video1394.
|
|
|
|
NOTE:
|
|
|
|
You should only build ONE of the stacks, unless you REALLY know what
|
|
you are doing.
|
|
|
|
config FIREWIRE_OHCI
|
|
tristate "Support for OHCI FireWire host controllers"
|
|
depends on PCI && FIREWIRE
|
|
help
|
|
Enable this driver if you have a FireWire controller based
|
|
on the OHCI specification. For all practical purposes, this
|
|
is the only chipset in use, so say Y here.
|
|
|
|
To compile this driver as a module, say M here: The module will be
|
|
called firewire-ohci. It replaces ohci1394 of the classic IEEE 1394
|
|
stack.
|
|
|
|
NOTE:
|
|
|
|
You should only build ohci1394 or firewire-ohci, but not both.
|
|
If you nevertheless want to install both, you should configure them
|
|
only as modules and blacklist the driver(s) which you don't want to
|
|
have auto-loaded. Add either
|
|
|
|
blacklist firewire-ohci
|
|
or
|
|
blacklist ohci1394
|
|
blacklist video1394
|
|
blacklist dv1394
|
|
|
|
to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf
|
|
depending on your distribution. The latter two modules should be
|
|
blacklisted together with ohci1394 because they depend on ohci1394.
|
|
|
|
If you have an old modprobe which doesn't implement the blacklist
|
|
directive, use "install modulename /bin/true" for the modules to be
|
|
blacklisted.
|
|
|
|
config FIREWIRE_OHCI_DEBUG
|
|
bool
|
|
depends on FIREWIRE_OHCI
|
|
default y
|
|
|
|
config FIREWIRE_SBP2
|
|
tristate "Support for storage devices (SBP-2 protocol driver)"
|
|
depends on FIREWIRE && SCSI
|
|
help
|
|
This option enables you to use SBP-2 devices connected to a
|
|
FireWire bus. SBP-2 devices include storage devices like
|
|
harddisks and DVD drives, also some other FireWire devices
|
|
like scanners.
|
|
|
|
To compile this driver as a module, say M here: The module will be
|
|
called firewire-sbp2. It replaces sbp2 of the classic IEEE 1394
|
|
stack.
|
|
|
|
You should also enable support for disks, CD-ROMs, etc. in the SCSI
|
|
configuration section.
|