On 20 April 2015 at 22:16, Arend van Spriel ar...@broadcom.com wrote:
On 04/20/15 20:49, Rafał Miłecki wrote:
On 20 April 2015 at 19:12, Arend van Sprielar...@broadcom.com wrote:
On 04/20/15 13:26, Rafał Miłecki wrote:
On 17 April 2015 at 10:50, Arend van Sprielar...@broadcom.com wrote:
On 04/21/15 12:16, Rafał Miłecki wrote:
On 20 April 2015 at 22:16, Arend van Sprielar...@broadcom.com wrote:
On 04/20/15 20:49, Rafał Miłecki wrote:
On 20 April 2015 at 19:12, Arend van Sprielar...@broadcom.com wrote:
On 04/20/15 13:26, Rafał Miłecki wrote:
On 17 April 2015 at 10:50,
On 04/20/15 20:49, Rafał Miłecki wrote:
On 20 April 2015 at 19:12, Arend van Sprielar...@broadcom.com wrote:
On 04/20/15 13:26, Rafał Miłecki wrote:
On 17 April 2015 at 10:50, Arend van Sprielar...@broadcom.com wrote:
Another option is to add the parsing stuff in that nvram code and have
On 17 April 2015 at 10:50, Arend van Spriel ar...@broadcom.com wrote:
On 04/17/15 09:45, Rafał Miłecki wrote:
Huh, why dropping linux-wireless (and top posting btw)? Please let
everyone follow the discussion :)
On 15 April 2015 at 21:20, Hante Meulemanmeule...@broadcom.com wrote:
As I
On 04/20/15 13:26, Rafał Miłecki wrote:
On 17 April 2015 at 10:50, Arend van Sprielar...@broadcom.com wrote:
On 04/17/15 09:45, Rafał Miłecki wrote:
Huh, why dropping linux-wireless (and top posting btw)? Please let
everyone follow the discussion :)
On 15 April 2015 at 21:20, Hante
On 20 April 2015 at 19:12, Arend van Spriel ar...@broadcom.com wrote:
On 04/20/15 13:26, Rafał Miłecki wrote:
On 17 April 2015 at 10:50, Arend van Sprielar...@broadcom.com wrote:
Another option is to add the parsing stuff in that nvram code and have an
api to get the appropriate portion
