linux-kernel - Re: Issue with firewire from 2.6.35.9 to 2.6.36.1

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101207092735.48b82c40@stein>
Date:	Tue, 7 Dec 2010 09:27:35 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Robin Cook <rcook@...ms.net>, Clemens Ladisch <clemens@...isch.de>
Cc:	Maxim Levitsky <maximlevitsky@...il.com>,
	linux-kernel@...r.kernel.org,
	linux1394-devel <linux1394-devel@...ts.sourceforge.net>
Subject: Re: Issue with firewire from 2.6.35.9 to 2.6.36.1

On Dec 06 Robin Cook wrote:
> 07:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403]
> 
> The modprobe firewire-ohci quirks=17 worked to get the devices being
> created again.

I wonder which of our options is preferable:
  - Change fw-ohci from MSI blacklisting to whitelisting.  Agere FW643
    rev 07 is the only chip that can be whitelisted.
  - Simply drop MSI support altogether.
-- 
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/