From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Building sensor drivers outside the kernel tree
Date: Fri, 06 Mar 2009 08:14:18 +0000 [thread overview]
Message-ID: <20090306091418.3f0e5306@hyperion.delvare> (raw)
In-Reply-To: <49AAFDC8.20607@gmx.de>
Hallo Reinhard,
On Sun, 01 Mar 2009 22:27:36 +0100, Reinhard Nissl wrote:
> is there a chance to compile for example Asus atk0110 driver for
> my distros default kernel?
No, this is not possible. You could compile the atk0110 driver itself
easily, however it requires a hook in the ACPI subsystem which is
missing in standard kernels. So unfortunately you need to rebuild your
kernel for this part.
> I'd like to stay with openSUSE-11.1's kernel-default-2.6.27.19-3.2.1.
>
> I'm used to build modules outside of the kernel tree in the
> v4l-dvb project. So I wonder why it shouldn't be possible to
> achieve the same for the above driver.
In general it is possible. We don't have an external tree but the hwmon
API is so simple that it is very stable, which means that you can
often pick the latest version of a driver in the upstream kernel tree,
an build it for your kernel using a standalone Makefile. The only case
where it doesn't work is when a given hwmon driver builds on other APIs
which _did_ change. This is the case of acpi for the atk0110 driver, or
of i2c for a number of other hwmon drivers. Sometimes it is possible to
update the code to take API changes into account backwards, but when
there was no equivalent API in the old kernel (which is the case for the
atk0110 driver) this is simply not possible.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2009-03-06 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 21:27 [lm-sensors] Building sensor drivers outside the kernel tree Reinhard Nissl
2009-03-06 8:14 ` 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=20090306091418.3f0e5306@hyperion.delvare \
--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.