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
 
[an error occurred while processing this directive]
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 13 Dec 2008 16:38:50 +0200
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	Nick Kossifidis <mickflemm@...il.com>
Cc:	Bob Copeland <me@...copeland.com>,
	linux-pm@...ts.linux-foundation.org, ath5k-devel@...ts.ath5k.org,
	linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [ath5k-devel] Bugs on aspire one A150

On Sat, 2008-12-13 at 16:36 +0200, Maxim Levitsky wrote:
> On Sat, 2008-12-13 at 16:08 +0200, Nick Kossifidis wrote:
> > 2008/12/13 Maxim Levitsky <maximlevitsky@...il.com>:
> > >
> > > Hi,
> > >
> > > Indeed gpio #3 controls the led.
> > > I patched ath5k to use it, and led works now fine.
> > >
> > >
> > 
> > Please share your patch with the rest and also post an lspci -vnn for
> > your card so we can handle this in a generic way
> 
> This just a one liner hack
> 
> diff --git a/drivers/net/wireless/ath5k/base.c
> b/drivers/net/wireless/ath5k/base.c
> index 9d2c597..a447937 100644
> --- a/drivers/net/wireless/ath5k/base.c
> +++ b/drivers/net/wireless/ath5k/base.c
> @@ -2595,6 +2595,11 @@ ath5k_init_leds(struct ath5k_softc *sc)
>  		sc->led_pin = 1;
>  		sc->led_on = 1;  /* active high */
>  	}
> +
> +	__set_bit(ATH_STAT_LEDSOFT, sc->status);
> +	sc->led_pin = 3;
> +	sc->led_on = 1;
> +
>  	if (!test_bit(ATH_STAT_LEDSOFT, sc->status))
>  		goto out;
> 
> 
> 

> 
> Best regards,
> 	Maxim Levitsky
> 

Note: thus makes led to be off by default, otherwise set
sc->led_on = 0

this also works

Regards,
	Maxim Levitsky

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ