From: Axel.Thimm@ATrpms.net (Axel Thimm)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] lm87 support on Centos 4.3 (kernel 2.6.9-34.EL) /
Date: Sat, 15 Apr 2006 17:54:27 +0000 [thread overview]
Message-ID: <20060415175427.GA655@neu.nirvana> (raw)
In-Reply-To: <443C3FF8.9080002@sedonanetworks.com>
Hi,
On Sat, Apr 15, 2006 at 03:40:07PM +0200, Jean Delvare wrote:
> > > Oh exept one. You can try to build the kernel outside the kernel
> > > tree. But his implies you can run make modules_prepare in in the
> > > 2.6.9 kernel and you must have proper configuration file
> > > (.config) installed.
> >
> > I thought out-of-tree builds were not supported anymore for 2.6
> > kernels. If they are I could pick them up again and create rpms
> > for them (kmdls) like for the 2.4 kernels. That would solve Doug's
> > issue, too, as I package for RHEL4, too.
>
> But what would you be packaging exactly? Remember that the kernel
> modules in lm_sensors2 CVS are *not* suitable for 2.6 kernels. What
> Rudolf was proposing was to backport one given driver from a recent
> 2.6 kernel to 2.6.9. This would be done on an individual
> basis. There is no out-of-tree set of hardware monitoring drivers
> working for every 2.6 kernel, like we had for 2.4 kernels.
Ah, OK, I misunderstood Rudolf's advice, I thought that maybe
out-of-tree builds had been reintroduced for 2.6. and I didn't notice.
Then wrt the original issue: It is very unlikely that RHEL4 will ever
upgrade to something else than 2.6.9, but backports are very
likely. Doug, you could try bugzilla.redhat.com to file a request. I
guess since you're using CentOS you don't have a customer relation to
Red Hat, but they may still consider it.
Also note that there are development kernels for the next RHEL4 update
where you can check whether any support you need has already happened:
http://people.redhat.com/~jbaron/rhel4/
--
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/20060415/5dbac2b8/attachment.bin
next prev parent reply other threads:[~2006-04-15 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 23:47 [lm-sensors] lm87 support on Centos 4.3 (kernel 2.6.9-34.EL) / Doug - Sedona Networks
2006-04-13 17:01 ` [lm-sensors] lm87 support on Centos 4.3 (kernel 2.6.9-34.EL) Rudolf Marek
2006-04-13 22:43 ` Info - Sedona Networks
2006-04-15 12:41 ` Axel Thimm
2006-04-15 13:40 ` [lm-sensors] lm87 support on Centos 4.3 (kernel 2.6.9-34.EL) / Jean Delvare
2006-04-15 17:54 ` Axel Thimm [this message]
2006-04-18 2:13 ` [lm-sensors] lm87 support on Centos 4.3 (kernel 2.6.9-34.EL) Info - Sedona Networks
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=20060415175427.GA655@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.