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

Message-Id: <200901210523.01282.ionut.leonte@gmail.com>
Date:	Wed, 21 Jan 2009 05:23:01 +0200
From:	Ionut Leonte <garglkml@...il.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.28 changes in-kernel name for UVC device ?

On Tuesday 20 January 2009 19:13:45 you wrote:
> Kay Sievers wrote:
> > You may just disable the firefire drivers if you don't need them.
>
> It is not even necessary to disable the drivers; it would be sufficient
> to not force-load the video1394 module.  (Or to fix the udev rule.)
> Presence of a Firewire card does not cause video1394 to be auto-loaded;
> 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 - the only modules I 
have are out-of-tree ones (like the binary nvidia driver and ndiswrapper). 
Perhaps it's time I reconsidered my monolithic aproach to kernel building and 
start compiling stuff as modules again.
--
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/