Am 24.08.2016 um 09:54 schrieb Oswald Buddenhagen:
On Tue, Aug 23, 2016 at 09:14:36PM +0200, Mathias Kresin wrote:
With 12fe4b579801ea812b64fc7e689716cd39c895ec I switched the ath5k
eeprom extraction to an alternate code path. Unfortunately this code
seams to be broken since ages and broke the a
On 24/08/2016 09:54, Oswald Buddenhagen wrote:
> On Tue, Aug 23, 2016 at 09:14:36PM +0200, Mathias Kresin wrote:
>> With 12fe4b579801ea812b64fc7e689716cd39c895ec I switched the ath5k
>> eeprom extraction to an alternate code path. Unfortunately this code
>> seams to be broken since ages and broke
On 23/08/2016 21:14, Mathias Kresin wrote:
> With 12fe4b579801ea812b64fc7e689716cd39c895ec I switched the ath5k
> eeprom extraction to an alternate code path. Unfortunately this code
> seams to be broken since ages and broke the ath5k EEPROM extraction.
>
> Reported-by: Mohammed Berdai
> Signed
On Tue, Aug 23, 2016 at 09:14:36PM +0200, Mathias Kresin wrote:
> With 12fe4b579801ea812b64fc7e689716cd39c895ec I switched the ath5k
> eeprom extraction to an alternate code path. Unfortunately this code
> seams to be broken since ages and broke the ath5k EEPROM extraction.
>
i have no particular
With 12fe4b579801ea812b64fc7e689716cd39c895ec I switched the ath5k
eeprom extraction to an alternate code path. Unfortunately this code
seams to be broken since ages and broke the ath5k EEPROM extraction.
Reported-by: Mohammed Berdai
Signed-off-by: Mathias Kresin
---
...-lantiq-wifi-and-etherne
