linux-kernel - Re: 2.6.28 changes in-kernel name for UVC device ?

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

Message-ID: <4976DB7B.9030802@s5r6.in-berlin.de>
Date:	Wed, 21 Jan 2009 09:23:23 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Ionut Leonte <garglkml@...il.com>
CC:	linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>
Subject: Re: 2.6.28 changes in-kernel name for UVC device ?

Ionut Leonte wrote:
> On Tuesday 20 January 2009 19:13:45 you wrote:
>> only certain types of FireWire cameras cause respective uevents and thus
>> autoloading of the special-purpose driver video1394.  Ergo, Ionut's
>> userland has a configuration somewhere which loads video1394 explicitly.
> 
> It's most likely related to my kernel being monolithic -

Ah, right; I keep forgetting that there is also Y besides M.  :-)
Anyway, the best course of action is to get the udev device naming rules
fixed.

I suppose the simplest course of action would be to add the expression
SUBSYSTEM=="video4linux" to the v4l rule.  Then it won't be applied to
ieee1394 devices.
-- 
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/