linux-kernel - Re: [ath5k-devel] Bugs on aspire one A150

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: <20081231135914.GA31780@rhlx01.hs-esslingen.de>
Date:	Wed, 31 Dec 2008 14:59:15 +0100
From:	Andreas Mohr <andi@...as.de>
To:	Andreas Mohr <andi@...as.de>
Cc:	Maxim Levitsky <maximlevitsky@...il.com>,
	Bob Copeland <me@...copeland.com>, ath5k-devel@...ts.ath5k.org,
	linux-kernel@...r.kernel.org
Subject: Re: [ath5k-devel] Bugs on aspire one A150

Hi,

On Wed, Dec 31, 2008 at 10:18:45AM +0100, Andreas Mohr wrote:
> Hi,
> 
> > Sure, will test, I am also sure that this will work.
> 
> A110L, 2.6.28, success (also inverted here, traffic blanks it).
> 
> Note that CONFIG_LEDS_TRIGGER_DEFAULT_ON=m, might be related
> (possibly ath5k is just mis-using LEDs API, in light of this setting?).

Nope, genuinely inverted,  modprobe ledtrig-default-on and
# echo default-on > /sys/class/leds/ath5k-phy0\:\:*x/trigger
actually blanks the LED.
ledtrig-heartbeat exhibits a weird inverted but actually heartbeat-like pattern,
too.

IOW, our hardware _is_ inverted for real I believe and the driver needs
to be fixed.

Oh, and what about the second LED on the left side? That one would be
available for driver implementation, too, right?
Or is that one hard-wired (via Embedded Controller?)
to rfkill mechanical switch?

(default use for those two would then be rfkill / Rx/Tx triggers, right?)

Andreas Mohr
--
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/