linux-kernel - Re: [PATCH] Sony laptop: Some Sony Vaia laptops do not enable wwan power by default.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090423085021.GA24761@kamineko.org>
Date:	Thu, 23 Apr 2009 17:50:21 +0900
From:	Mattia Dongili <malattia@...ux.it>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Tim Gardner <timg@....com>, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Sony laptop: Some Sony Vaia laptops do not enable wwan
	power by default.

On Wed, Apr 22, 2009 at 09:11:15PM +0100, Matthew Garrett wrote:
> On Wed, Apr 22, 2009 at 02:07:14PM -0600, Tim Gardner wrote:
> 
> > The laptop model that doesn't power up wwan on cold boot contains a
> > "Sony Programmable IO Control Driver" ("VGN-" according to the DMI
> > info). It appears that only laptops with a "Sony Notebook Control
> > Driver" enjoy rfkill goodness. I don't know for sure if those models
> > fail to power up wwan when rfkill is disabled.
> 
> Right. It'd need porting to the rfkill infrastructure, rather than just 
> being a sysfs attribute.

Agreed, the only thing I'm missing is how to read the initial device
state (same for bluetooth and wifi).
I've been throwing some values at the SPIC device with much success for
now. Tracing in windows is a big no-no as it dies on me as soon as I
start any tracing utility.
I'm open for suggestions.
-- 
mattia
:wq!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/