All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: /proc/acpi/ibm/wan stopped appearing
Date: Wed, 27 Aug 2008 16:27:00 -0700	[thread overview]
Message-ID: <48B5E2C4.7060803@goop.org> (raw)
In-Reply-To: <20080827231223.GB18081@khazad-dum.debian.net>

Henrique de Moraes Holschuh wrote:
> 2. The proper way to control ANY radio's rfkill functions is through the
> rfkill sysfs interface.  That includes thinkpad-acpi's  bluetooth and WWAN.
>   

Do you know what UI-level programs make use of these interfaces now?

> IOW, we may have a regression here.  Please compile thinkpad-acpi with debug
> mode enabled, load it with the "debug=0xffff" and "experimental=1"
> parameters (as far as I remember, WWAN requires "experimental=1" to work,
> without that it will NOT load, and you will NOT get /proc/acpi/ibm/wan or
> anything else WWAN related from thinkpad-acpi), and send me the resulting
> log output from thinkpad-acpi.

Actually, that may be it.  I think I used to load it as a module, and
modprobe.conf set experimental=1, but I don't have an equivalent on the
kernel command line.

I think I'll submit a patch to remove the need for experimental; it's
been working fine for me for 3 years now.

    J

  reply	other threads:[~2008-08-27 23:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 22:11 /proc/acpi/ibm/wan stopped appearing Jeremy Fitzhardinge
2008-08-27 23:12 ` Henrique de Moraes Holschuh
2008-08-27 23:27   ` Jeremy Fitzhardinge [this message]
2008-08-28  1:46     ` Henrique de Moraes Holschuh
2008-08-28  4:04       ` [PATCH] ACPI: thinkpad-acpi: wan radio control is not experimental Jeremy Fitzhardinge
2008-08-28 13:39         ` Henrique de Moraes Holschuh
2008-08-28 17:25         ` Andi Kleen

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=48B5E2C4.7060803@goop.org \
    --to=jeremy@goop.org \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@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.