linux-kernel - Re: [PATCH] Vicam driver, 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>] [day] [month] [year] [list]

Message-Id: <200609041935.37858.nick@linicks.net>
Date:	Mon, 4 Sep 2006 19:35:37 +0100
From:	Nick Warne <nick@...icks.net>
To:	"Bas Bloemsaat" <bas.bloemsaat@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Vicam driver, device

On Monday 04 September 2006 19:28, Bas Bloemsaat wrote:
> Yes, but not an oops as you describe. I get the following in the
> syslog when I modprobe it:
> kernel: videodev: "ViCam-based USB Camera" has no release callback.
> Please fix your driver for proper sysfs support, see
> http://lwn.net/Articles/36850/

No sorry, I worded it all wrong.  I meant on modprobe.  I then attempted to 
fix the code, which produced kernel oops, so it was my bad code that caused 
it - it needs someone that knows what they are doing ;-)

> When rmmodding, the only message I see is: "kernel: usbcore:
> deregistering driver vicam", which seems normal.

After my attempted fixes, this is when my kernel crashed.

> I didn't plan on using the webcam, I just couldn't stand that it
> didn't work while a driver was supposed to be available, and now it
> works.

I don't use mine now, but it would be nice to get this code brought up to 
date.

Nick
-- 
Every program has two purposes:
one for which it was written and another for which it wasn't.
-
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/