linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ja@marvec.org
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Tino Schmidt" <mailtinoshomepage@gmx.net>,
	linux-input@vger.kernel.org, "Miloslav Trmac" <mitr@volny.cz>,
	"Ben Hutchings" <ben@decadent.org.uk>,
	"Jonathan Woithe" <jwoithe@physics.adelaide.edu.au>,
	"Éric Piel" <eric.piel@tremplin-utc.net>
Subject: Re: Wishlist: Add support for software-rf-switch in Fujitsu-Siemens notebook
Date: Tue, 04 Oct 2011 10:25:28 +0200	[thread overview]
Message-ID: <2ccea6c74fe05a97c2fd92a16b92def5@marvec.org> (raw)
In-Reply-To: <20111002221253.GA18253@elie>

 Hello,

 I never tried integrating the code into any "standard way". I just 
 needed a quick fix and I do not have much experience with Kernel 
 programming.

 I agree that running the code without checking the presence of this HW 
 can have bad side effects (however, I did not experienced any on several 
 different laptops).

 I do not have the hardware easily accessible now to provide requested 
 information. I would really appreciate if anybody could take the code 
 and put it into some standard Kernel module.

 Please note, that it is not possible to switch the wifi on by emulating 
 some software keys. It really needs to write to some HW ports. I 
 obtained these numbers by reverse engineering the original 
 Fujitsu-Siemens Windows driver.

 Cheers,
 Martin

 On Sun, 2 Oct 2011 17:12:54 -0500, Jonathan Nieder wrote:
> Hi,
>
> Tino Schmidt wrote[1]:
>
>> My notebook is an Fujitsu Siemens Amilo A1655G, which has a
>> software-based RF-Switch. My wireless network card (
>> Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN
>> Controller (rev 02), ID 14e4:4318) would be unusable if there wasn't 
>> a
>> project like http://sourceforge.net/projects/fsaa1655g/ which brings
>> support at least for kernel 2.6.26. But there isn't any support 
>> beyond
>> kernel 2.6.26.
>
> I notice that the wistron_btns driver has support for some other 
> Amilo
> laptops.  The source says:
>
>  /*
>   * If your machine is not here (which is currently rather likely),
> please send
>   * a list of buttons and their key codes (reported when loading this 
> module
>   * with force=1) and the output of dmidecode to $MODULE_AUTHOR.
>   */
>
> Tino (or anyone with this hardware), could you send dmesg output from
>
> 	modprobe wistron_btns force=1
>
> and dmidecode (or "grep . /sys/class/dmi/id/*_{vendor,name,version}"
> as Ben suggested)?
>
> Thanks,
> Jonathan
>
> [1] http://bugs.debian.org/631664


  reply	other threads:[~2011-10-04  8:32 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 [this message]
2011-10-16 20:25     ` Tino Schmidt
2011-10-17  4:03       ` Ben Hutchings
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=2ccea6c74fe05a97c2fd92a16b92def5@marvec.org \
    --to=ja@marvec.org \
    --cc=ben@decadent.org.uk \
    --cc=eric.piel@tremplin-utc.net \
    --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).