linux-kernel - Re: [PATCH] bw-qcam: Adds module parameter 'aggressive' to skip polite auto-detection prior to direct initialization.

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: <20071205004639.3a5cc948@the-village.bc.nu>
Date:	Wed, 5 Dec 2007 00:46:39 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Brett T. Warden" <brett.warden@...il.com>
Cc:	linux-kernel@...r.kernel.org, trivial@...nel.org,
	"Brett T. Warden" <brett.warden@...il.com>
Subject: Re: [PATCH] bw-qcam: Adds module parameter 'aggressive' to skip
 polite auto-detection prior to direct initialization.

On Tue,  4 Dec 2007 16:44:41 -0800
"Brett T. Warden" <brett.warden@...il.com> wrote:

> Setting aggressive=1 bypasses the friendly auto-detection by polling the status register, and instead attempts to initialize the qcam directly. Not friendly to other parallel devices, but much more reliable than the auto-detection.

Someone still has a bw-qcam device ?

The status polling ought to be rock solid - what values do you see ?
--
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/