From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Charles@schwieters.org
Cc: linux-acpi@vger.kernel.org
Subject: Re: experimental patch for toshiba_acpi
Date: Sat, 28 Feb 2009 09:13:37 +0300 [thread overview]
Message-ID: <200902280913.45040.arvidjaar@mail.ru> (raw)
In-Reply-To: <E1LdAJL-0003Jk-EQ@tan.cit.nih.gov>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
On 28 февраля 2009 00:31:59 Charles@schwieters.org wrote:
> Hello Andrey--
>
> > >This patch comes from
> > > http://memebeam.org/free-software/toshiba_acpi/. With this patch,
> > > the module conflicts with the toshiba module (which works only on
> > > non-acpi-enabled kernels).
> >
> > Could you please elaborate? Because (Portege 4000):
> >
> > {pts/2}% lsmod | grep tosh
> > toshiba 4012 0
> > toshiba_acpi 7540 0
> > rfkill 10480 1 toshiba_acpi
> > backlight 4560 2 toshiba_acpi,video
> > input_polldev 4012 1 toshiba_acpi
> > {pts/2}% sudo fan
> > Fan is on.
>
> My understanding is that with the experimental patch, both toshiba
> and toshiba_acpi use /dev/toshiba. Do you have the experimental patch
> applied? Does fan work if you remove the toshiba module?
>
May be I misunderstood you then; do you mean that *if* this patch is
applied module toshiba works on non-ACPI kernels only? That would be the
case then.
But then I do not understand why you need this in toshiba_acpi in the
first place. We already have in-kernel module (toshiba) that provides
raw user space HCI access to those who need it. Why is it necessary to
duplicate this functionality in toshiba_acpi in the first place?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-28 6:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 21:15 experimental patch for toshiba_acpi Andrey Borzenkov
2009-02-27 21:31 ` Charles
2009-02-28 6:13 ` Andrey Borzenkov [this message]
2009-02-28 18:00 ` Charles
2009-03-01 7:00 ` Andrey Borzenkov
2009-03-01 10:31 ` Charles
-- strict thread matches above, loose matches on Subject: below --
2009-02-25 14:54 Charles
2009-02-25 15:24 ` Matthew Garrett
2009-02-25 16:18 ` Jonathan Buzzard
2009-02-25 16:51 ` Matthew Garrett
2009-02-25 17:12 ` Jonathan Buzzard
2009-02-25 17:28 ` Matthew Garrett
2009-02-25 17:53 ` Jonathan Buzzard
2009-02-25 17:59 ` Matthew Garrett
2009-02-25 20:18 ` Charles
2009-02-26 0:22 ` Jonathan Buzzard
2009-02-26 8:39 ` Richard Hughes
2009-02-26 10:34 ` Jonathan Buzzard
2009-02-26 12:52 ` Richard Hughes
2009-02-26 13:27 ` Jonathan Buzzard
2009-02-26 13:59 ` Richard Hughes
2009-02-26 15:49 ` Jonathan Buzzard
2009-02-25 17:33 ` Azael Avalos
2009-02-26 13:12 ` John Belmonte
2009-02-26 14:03 ` Richard Hughes
2009-02-26 15:51 ` Jonathan Buzzard
2009-02-26 16:01 ` Matthew Garrett
2009-02-27 16:49 ` Richard Hughes
2009-02-27 17:18 ` Jonathan Buzzard
2009-02-28 15:19 ` Henrique de Moraes Holschuh
2009-03-13 1:17 ` Len Brown
2009-03-14 0:37 ` Charles
2009-03-14 7:02 ` Andrey Borzenkov
2009-03-14 12:05 ` Matthew Garrett
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=200902280913.45040.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=Charles@schwieters.org \
--cc=linux-acpi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox