All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel.Thimm@ATrpms.net (Axel Thimm)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] grafting lm-sensors 2.10.1 onto red hat kernel
Date: Thu, 26 Oct 2006 06:56:33 +0000	[thread overview]
Message-ID: <20061026065633.GC23679@neu.nirvana> (raw)
In-Reply-To: <Pine.LNX.4.64.0610251056560.7544@snowball.fnal.gov>

On Wed, Oct 25, 2006 at 08:13:38PM -0500, Steven Timm wrote:
> >>
> >> The kernel as distributed by Red Hat in RHEL4 update 4
> >> (2.6.9-42.0.3) has got
> >> an lm_sensors and i2c in there already but it is a very old version,
> >> 2.8.7.  That is not new enough to support certain chips on new hardware,
> >> particularly the w83792 sensor.  Has anyone successfully
> >> been able to patch the latest 2.10.1 lm_sensors against that
> >> old kernel, and if so, how?
> >
> > The lm-sensors project has two parts:
> > 1) a userspace part, including the sensors(1) program and libsensors(3) library
> > 2) the Linux kernel drivers for the i2c bus and sensor chips
> >
> > We maintain the kernel drivers for the 2.6 series directly in Linus' tree now.
> > The trouble is, you're using 2.6.9-something which does not contain support
> > for your device - not surprising since 2.6.9 is a few days over 2 years old
> > by now.
> 
> What was 2.6.9 in Linus' tree and what Red HAt distributes are quite 
> different.  They grab a lot of the newer patches from the newer kernels
> but evidently not these ones.  I guess I am just going to have to
> open a ticket with Red Hat and ask them to include these into
> their next version.

I think that's the best option. See for example

  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x171507

where a similar request resulted in an updated RHEL4 kernel in May
(officially released as errata in August).

> > To support the w83792 sensor on that old kernel, someone will have to back-
> > port the current driver so that it works with 2.6.9.  My guess is that you
> > will not get any volunteers to do this (not particularly interesting) work.
> > Although, it shouldn't be very hard for a decent C programmer to do it...
> > maybe that is you or someone you work with.
> 
> IF we do this we have to get the latest i2c as well as the latest 
> lm_sensors back-ported there, don't we?
> >
> > Another option could be to upgrade to a newer kernel that does support the
> > device.
> >
> Not an option here because we are depending on Red Hat for security 
> updates on this kernel and thus want to leave the underlying kernel
> as untouched as possible.  This was possible in the 2.4 kernel series.
> I can't believe we are the only site in this situation.  There are a lot
> of others that try to run with the enterprise kernels and it would
> seem there should be quite a bit of interest in this.

In that case post the bugzilla URL here and invite people to join the
request. If the demand is demonstrated to some extend the next RHEL4
update may have updated i2c/lm_sensors bits which everyone would
welcome.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20061026/459ddba3/attachment.bin 

  parent reply	other threads:[~2006-10-26  6:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 15:59 [lm-sensors] grafting lm-sensors 2.10.1 onto red hat kernel Steven Timm
2006-10-25 17:26 ` Jean Delvare
2006-10-25 17:36 ` Steven Timm
2006-10-26  0:33 ` Mark M. Hoffman
2006-10-26  1:13 ` Steven Timm
2006-10-26  6:56 ` Axel Thimm [this message]
2006-10-30 17:17 ` Steven Timm
2006-10-30 22:33 ` Axel Thimm
2006-10-30 22:58 ` Steven Timm
2006-10-31  7:40 ` Jean Delvare
2006-10-31 14:25 ` Steven Timm
2006-10-31 15:26 ` 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=20061026065633.GC23679@neu.nirvana \
    --to=axel.thimm@atrpms.net \
    --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.