public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Renato S. Yamane" <renatoyamane@mandic.com.br>
To: linux-acpi <linux-acpi@vger.kernel.org>
Cc: Rolf Eike Beer <eike-kernel@sf-tec.de>,
	"Renato S. Yamane" <renatoyamane@mandic.com.br>,
	Richard Hughes <hughsient@gmail.com>,
	John Belmonte <john@neggie.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Bastien Nocera <hadess@hadess.net>,
	Mathieu.Berard@crans.org, mjg59@srcf.ucam.org, jaimeff@gmail.com
Subject: Re: Add INPUT support to toshiba_acpi
Date: Tue, 03 Jul 2007 09:59:42 -0300	[thread overview]
Message-ID: <468A483E.6060207@mandic.com.br> (raw)
In-Reply-To: <200707030738.39980.eike-kernel@sf-tec.de>

Rolf Eike Beer wrote:
> Renato S. Yamane wrote:
>> Rolf Eike Beer wrote:
>>> Richard Hughes wrote:
>>>>
>>>> Yes, although this is out of my area or expertise, sorry.
>>>
>>> I've looked a bit but can't find any driver interaction of those
>>> programs. Any further ideas welcome.
>>
>> Do you try omnibook driver?
>> svn export https://svn.sourceforge.net/svnroot/omnibook/omnibook/trunk
>>
>> toshiba_acpi don't work on my Toshiba M45-S355 (Toshiba BIOS) and I try
>> this module above and now I can change brightness writing in
>> /proc/omnibook/lcd and kpowersave can change brightness too.
>
> Oh wow! Even my Multimedia keys get recognized. Thanks very much for your 
> pointer.

I think that is a good idea more support to Toshiba Laptops, so 
omnibook+toshiba_acpi is a perfect couple, because some functions works 
with toshiba_acpi and others works with omnibook.

Jaime (in cc too) do a very useful module that work in some laptop 
models that not work on toshiba_acpi and omnibook driver.

So, I think that is a very good idea all work together to do a more 
powerful (and compatible) module in next kernel releases.

Regards,
Renato S. Yamane

      reply	other threads:[~2007-07-03 12:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 12:36 Add INPUT support to toshiba_acpi Richard Hughes
2007-05-31 12:53 ` Bastien Nocera
2007-05-31 13:43   ` Richard Hughes
2007-05-31 15:46     ` Richard Hughes
2007-05-31 16:46       ` Andreas Mohr
2007-05-31 23:09         ` Richard Hughes
2007-06-01 16:45       ` Dmitry Torokhov
2007-06-02 12:50         ` Richard Hughes
2007-06-02 14:23           ` Matthew Garrett
2007-06-03  4:48             ` Dmitry Torokhov
2007-06-07 16:58               ` Richard Hughes
2007-06-08 14:23                 ` Dmitry Torokhov
2007-06-08 14:30                   ` Richard Hughes
2007-06-11 13:26                 ` Renato S. Yamane
2007-06-23 14:56 ` Rolf Eike Beer
2007-06-25  9:52   ` Richard Hughes
2007-06-25 11:03     ` Rolf Eike Beer
2007-06-26  5:03     ` Rolf Eike Beer
2007-06-26  8:56       ` Richard Hughes
2007-06-28 11:27         ` Rolf Eike Beer
2007-06-28 12:22           ` Renato S. Yamane
2007-07-03  5:38             ` Rolf Eike Beer
2007-07-03 12:59               ` Renato S. Yamane [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=468A483E.6060207@mandic.com.br \
    --to=renatoyamane@mandic.com.br \
    --cc=Mathieu.Berard@crans.org \
    --cc=eike-kernel@sf-tec.de \
    --cc=hadess@hadess.net \
    --cc=hughsient@gmail.com \
    --cc=jaimeff@gmail.com \
    --cc=john@neggie.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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