All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [Fwd: sensors, kernel 2.4.19, bttv ...]
Date: Thu, 19 May 2005 06:24:22 +0000	[thread overview]
Message-ID: <20031026193437.2790a178.khali@linux-fr.org> (raw)
In-Reply-To: <1067191364.14649.3.camel@lenny.homelinux.net>


> It's me again... i just would like to add a word : I've just read i2c
> 2.8.0 was included in kernels after 2.4.21.

No, it isn't. Where did you read that? It might be that *distributions*
patch the 2.4.21 kernels they are packaging with i2c 2.8.0, but it isn't
part of the vanilla sources.

> Does it mean that simply upgrading my kernel from 2.4.19 to - say -
> 2.4.22 will do the trick ?

No, it won't.

> I mean, then I'll only have to compile lm_sensors and everything will
> be fine (bttv and i2c sensors ?)

You're invited to point your browser to:
http://www.ensicaen.ismra.fr/~delvare/devel/i2c/
and read carefully everything that is written there. You'll find the
patches you need to be able to use i2c-2.8.x and still have bttv
working. Basically, all you'll have to do is patch your kernel sources
using one of the provided patches (i2c 2.8.0 for Linux 2.4.21 or i2c
2.8.1 for Linux 2.4.22), then installing lm_sensors (same version as
i2c) will be done as usual.

Let us know how it work for you.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

      parent reply	other threads:[~2005-05-19  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 [Fwd: sensors, kernel 2.4.19, bttv ...] Pascal Ronecker
2005-05-19  6:24 ` Pascal Ronecker
2005-05-19  6:24 ` Pascal Ronecker
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Pascal Ronecker
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` 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=20031026193437.2790a178.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@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.