public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Perry Gilfillan <perrye@gilfillan.org>
Cc: sensors@Stimpy.netroedge.com, linux-kernel@vger.kernel.org
Subject: Re: Any one using i2c-voodoo3 module on the 2.6 kernel?
Date: Sat, 15 May 2004 08:06:16 +0200	[thread overview]
Message-ID: <20040515080616.7587dc68.khali@linux-fr.org> (raw)
In-Reply-To: <40A424D3.7060006@gilfillan.org>

> 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.

It happens that I have an old Voodoo 3000 graphics card lying in a box
somewhere, so I thought I would try and plug it, and see what happens.

I was able to load the i2c-voodoo3 driver (Linux 2.6.6-rc3) and it seems
to work for me. I have the following line in the logs:

voodoo3 smbus 0000:01:00.0: Using Banshee/Voodoo3 I2C device at e8964000

After loading i2c-dev, "i2cdetect -l" sees two i2c busses on the card,
and I can use i2cdetect, i2cdump etc. So it seems to work fine.

I suspect that you have another driver requesting the card, such has a
framebuffer driver. The 2.4 driver doesn't request the device so no
conflict happens. The 2.6 driver does request it, because it is
considered Bad (TM) to use a device without requesting it. This probably
means that the i2c-voodoo3 driver should me merged into the framebuffer
driver, much like it was done for matroxfb and radeonfb. This also makes
sense because the framebuffer driver can use the DDC channel (which is
no more than I2C, renamed) to retrieve information about the monitor and
adapt its output. But this also raises the problem that people may want
to access the i2c busses without loading the full framebuffer driver...

> 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 not very qualified about PCI stuff, but this could confirm my
suspicion above.

> I'd appreciate any advice on where to look first, and where in sysfs
> to look for evidence that the module loaded correctly.

See what is done in proc/dump/i2cbusses.c (lm_sensors package). Looks
like you should point your shell to /sys/class/i2c-dev. This suggests
that you have actually loaded i2c-dev.

> Has anyone used the Banshee or Voodoo3 card with the i2c-voodoo3
> module in the 2.6 kernel with success?

Yes ;) although I didn't do anything useful with it after that.

-- 
Jean Delvare
http://khali.linux-fr.org/

      reply	other threads:[~2004-05-15  6:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14  1:45 Any one using i2c-voodoo3 module on the 2.6 kernel? Perry Gilfillan
2004-05-15  6:06 ` Jean Delvare [this message]

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=20040515080616.7587dc68.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perrye@gilfillan.org \
    --cc=sensors@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