From: Nick Warne <nick@linicks.net>
To: "Bas Bloemsaat" <bas.bloemsaat@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Vicam driver, device
Date: Mon, 4 Sep 2006 19:35:37 +0100 [thread overview]
Message-ID: <200609041935.37858.nick@linicks.net> (raw)
In-Reply-To: <7c4668e50609041128j4e382815me92cdbabb53d662d@mail.gmail.com>
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.
next prev parent reply other threads:[~2006-09-04 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 18:01 [PATCH] Vicam driver, device Bas Bloemsaat
2006-09-02 18:12 ` Mauro Carvalho Chehab
[not found] ` <7c4668e50609030111i5f3cb079j76e9c8651cf8d6b4@mail.gmail.com>
2006-09-03 8:38 ` Bas Bloemsaat
2006-09-03 16:30 ` Nick Warne
[not found] ` <7c4668e50609041128j4e382815me92cdbabb53d662d@mail.gmail.com>
2006-09-04 18:35 ` Nick Warne [this message]
2006-09-02 19:55 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609041935.37858.nick@linicks.net \
--to=nick@linicks.net \
--cc=bas.bloemsaat@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.