From: Perry Gilfillan <perrye@gilfillan.org>
To: sensors <lm78@stimpy.netroedge.com>,
kernel <linux-kernel@vger.kernel.org>
Subject: Any one using i2c-voodoo3 module on the 2.6 kernel?
Date: Thu, 13 May 2004 20:45:55 -0500 [thread overview]
Message-ID: <40A424D3.7060006@gilfillan.org> (raw)
Hello,
I've made some progress with the v3tv project. Using the recent 2.4
kernels, with various patches for v4l2, i2c-2.8.x, and sensors-2.8.x,
I've got all of the v4l modules to attach to the i2c-voodoo3 module.
I've also got a v4l2 radio device working on the 2.4 kernel :)
Now I'd like to start looking at the 2.6 kernel. At this point it does
not seem that the i2c-voodoo3 module is loading correctly. The module
is totaly silent in the logs, so I can't offer any immediate list of
symptoms, except to say I can find no reference to it in the sysfs and
proc directories.
The client module probe functions never see the Voodoo3 adapter.
The call to pci_module_init returns zero. Replacing that with a call to
pci_register_driver yeilds a one, but this may not be representative,
since pci_register_driver always returns a non-zero value.
I'm going to add more printk's to the pci-driver.c file, and reboot when
I have time for it.
I'd appreciate any advice on where to look first, and where in sysfs to
look for evidence that the module loaded correctly.
Has anyone used the Banshee or Voodoo3 card with the i2c-voodoo3 module
in the 2.6 kernel with success?
Thanks,
Perry
-----
Projects:
V3TV: http://www.gilfillan.org/v3tv/
VPX3224: http://www.gilfillan.org/vpx3224/
V3TV-radio: http://www.gilfillan.org/v3tv-v4l2/
snd-tvmixer: http://www.gilfillan.org/ALSA/
next reply other threads:[~2004-05-14 1:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 1:45 Perry Gilfillan [this message]
2004-05-15 6:06 ` Any one using i2c-voodoo3 module on the 2.6 kernel? Jean Delvare
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=40A424D3.7060006@gilfillan.org \
--to=perrye@gilfillan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm78@stimpy.netroedge.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox