On Sunday, September 18, 2016 2:19:33 PM CEST John Crispin wrote:
> On 18/09/2016 14:17, Martin Blumenstingl wrote:
> > On Sun, Sep 18, 2016 at 2:01 PM, John Crispin wrote:
> >> On 08/09/2016 23:58, Christian Lamparter wrote:
> >>> So yes, if it needs to go in a different location, that would be f
On 18/09/2016 14:17, Martin Blumenstingl wrote:
> On Sun, Sep 18, 2016 at 2:01 PM, John Crispin wrote:
>>
>>
>> On 08/09/2016 23:58, Christian Lamparter wrote:
>>> So yes, if it needs to go in a different location, that would be fine.
>>> Based on your suggestion, I think the owl-loader.c code c
On Sun, Sep 18, 2016 at 2:01 PM, John Crispin wrote:
>
>
> On 08/09/2016 23:58, Christian Lamparter wrote:
>> So yes, if it needs to go in a different location, that would be fine.
>> Based on your suggestion, I think the owl-loader.c code can be moved to:
>> target/linux/generic/files/drivers/net
On 08/09/2016 23:58, Christian Lamparter wrote:
> So yes, if it needs to go in a different location, that would be fine.
> Based on your suggestion, I think the owl-loader.c code can be moved to:
> target/linux/generic/files/drivers/net/wireless/ath9k/owl-loader.c
>
> and the module definition f
On 10/09/2016 11:24, Martin Blumenstingl wrote:
> On Thu, Sep 8, 2016 at 11:58 PM, Christian Lamparter
> wrote:
>> Hello,
>>
>> On Thursday, September 8, 2016 9:34:07 AM CEST John Crispin wrote:
>>> Hi,
>>>
>>> why is this code located under package/ and not as a kernel patch under
>>> target/li
On Thu, Sep 8, 2016 at 11:58 PM, Christian Lamparter
wrote:
> Hello,
>
> On Thursday, September 8, 2016 9:34:07 AM CEST John Crispin wrote:
>> Hi,
>>
>> why is this code located under package/ and not as a kernel patch under
>> target/linux/generic ?
could you please explain why you would prefer t
Hello,
On Thursday, September 8, 2016 9:34:07 AM CEST John Crispin wrote:
> Hi,
>
> why is this code located under package/ and not as a kernel patch under
> target/linux/generic ?
well, there isn't a good reason. In fact, it started as a copy of
gpio-button-hotplug's skeleton and evolved it fro
Hi,
why is this code located under package/ and not as a kernel patch under
target/linux/generic ?
John
On 05/09/2016 06:59, Chris Blake wrote:
> From: Christian Lamparter
>
> Some devices (like the Cisco Meraki Z1 Cloud Managed Teleworker Gateway)
> need to be able to initialize the
From: Christian Lamparter
Some devices (like the Cisco Meraki Z1 Cloud Managed Teleworker Gateway)
need to be able to initialize the PCIe wifi device. Normally, this is done
during the early stages of booting linux, because the necessary init code
is read from the memory mapped SPI and passed to
