linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Tino Schmidt <mailtinoshomepage@gmx.net>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
	linux-input@vger.kernel.org, "Miloslav Trmac" <mitr@volny.cz>,
	"Martin Večeřa" <ja@marvec.org>,
	"Jonathan Woithe" <jwoithe@physics.adelaide.edu.au>,
	"Éric Piel" <eric.piel@tremplin-utc.net>,
	631664@bugs.debian.org
Subject: Re: Wishlist: Add support for software-rf-switch in Fujitsu-Siemens notebook
Date: Mon, 17 Oct 2011 05:03:47 +0100	[thread overview]
Message-ID: <1318824232.3340.1.camel@deadeye> (raw)
In-Reply-To: <4E9B3DCC.7050106@gmx.net>


[-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --]

On Sun, 2011-10-16 at 22:25 +0200, Tino Schmidt wrote:
[...]  
> Hi,
> I'm sorry for the long delay but I can use the laptop only on weekend. 
> Here is the output:
> 
> # modprobe wistron_btns force=1
> FATAL: Error inserting wistron_btns 
> (/lib/modules/2.6.26-2-686/kernel/drivers/input/misc/wistron_btns.ko): 
> No such device

It looks like this model is rather different, maybe not a Wistron design
at all.

I would prefer you to test against Linux 3.0, but it appears that the
model detection has not changed since 2.6.26.

> # dmesg
> [  168.628474] wistron_btns: BIOS entry point not found
> 
> and
> # grep . /sys/class/dmi/id/*_{vendor,name,version}
> /sys/class/dmi/id/bios_vendor:FUJITSU SIEMENS
> /sys/class/dmi/id/board_vendor:FUJITSU SIEMENS
> /sys/class/dmi/id/chassis_vendor:FUJITSU SIEMENS
> /sys/class/dmi/id/sys_vendor:FUJITSU SIEMENS
> /sys/class/dmi/id/board_name:AMILO A1655
> /sys/class/dmi/id/product_name:AMILO A Series
> /sys/class/dmi/id/bios_version:1.0C-8044-8A20
> /sys/class/dmi/id/board_version:Rev0.4b
> /sys/class/dmi/id/chassis_version:N/A
> /sys/class/dmi/id/product_version:0100

Please build and test the attached driver (make && insmod
amilo-rfkill.ko).  It provides a standard rfkill device which you can
control with e.g. the 'rfkill' command, and will only bind to specific
models.

If this works, I'll submit the code upstream.

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


[-- Attachment #1.2: amilo-rfkill.tar.gz --]
[-- Type: application/x-compressed-tar, Size: 1874 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2011-10-17  4:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110625211738.3615.21718.reportbug@lisa>
     [not found] ` <1317441406.4068.43.camel@deadeye>
2011-10-02 22:12   ` Wishlist: Add support for software-rf-switch in Fujitsu-Siemens notebook Jonathan Nieder
2011-10-04  8:25     ` ja
2011-10-16 20:25     ` Tino Schmidt
2011-10-17  4:03       ` Ben Hutchings [this message]
2011-10-31 17:30         ` Tino Schmidt
2011-11-01  4:33           ` Ben Hutchings
2011-11-06 21:04             ` Tino Schmidt

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=1318824232.3340.1.camel@deadeye \
    --to=ben@decadent.org.uk \
    --cc=631664@bugs.debian.org \
    --cc=eric.piel@tremplin-utc.net \
    --cc=ja@marvec.org \
    --cc=jrnieder@gmail.com \
    --cc=jwoithe@physics.adelaide.edu.au \
    --cc=linux-input@vger.kernel.org \
    --cc=mailtinoshomepage@gmx.net \
    --cc=mitr@volny.cz \
    /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;
as well as URLs for NNTP newsgroup(s).