+ Greg, +wilc1000 maintainers
On 3/1/2018 11:10 AM, Harsha Rao wrote:
On Wed, Feb 28, 2018 at 3:08 PM, Arend van Spriel
wrote:
On 2/28/2018 12:14 AM, Harsha Rao wrote:
My suspicion is that your device, is fundamentally a wilc1000 and that
the existing wilc1000
On Wed, Feb 28, 2018 at 3:08 PM, Arend van Spriel
wrote:
> On 2/28/2018 12:14 AM, Harsha Rao wrote:
>
> My suspicion is that your device, is fundamentally a wilc1000 and that
> >>>the existing wilc1000 driver will likely largely work for it and all
>
On 2/28/2018 12:14 AM, Harsha Rao wrote:
My suspicion is that your device, is fundamentally a wilc1000 and that
>>>the existing wilc1000 driver will likely largely work for it and all
>>>you really need to do is modify the existing driver to handle the
>>>quirks of your particular implementation
On Wed, Feb 28, 2018 at 1:34 AM, Arend van Spriel
wrote:
> On 2/27/2018 6:34 PM, Steve deRosier wrote:
>>
>> Hi Harsha,
>>
>> Part 2 - the darn cmd-enter shortcut in gmail got me again. Sorry for
>> the premature send.
>>
>>>
>>> As both Larry and Arend mention,
On 2/27/2018 6:34 PM, Steve deRosier wrote:
Hi Harsha,
Part 2 - the darn cmd-enter shortcut in gmail got me again. Sorry for
the premature send.
As both Larry and Arend mention, while it's possible to have multiple
drivers with the same IDs, for obvious reasons it's not desirable.
In theory
Hi Harsha,
Part 2 - the darn cmd-enter shortcut in gmail got me again. Sorry for
the premature send.
>
> As both Larry and Arend mention, while it's possible to have multiple
> drivers with the same IDs, for obvious reasons it's not desirable.
>
> In theory the vendor IDs shouldn't be duplicated
Hi Harsha,
On Tue, Feb 27, 2018 at 7:29 AM, Harsha Rao wrote:
> On Tue, Feb 27, 2018 at 8:44 PM, Larry Finger
> wrote:
>> On 02/27/2018 07:30 AM, Harsha Rao wrote:
>>>
>>> On Tue, Feb 27, 2018 at 4:45 PM, Arend van Spriel
>>>
On Tue, Feb 27, 2018 at 8:44 PM, Larry Finger wrote:
> On 02/27/2018 07:30 AM, Harsha Rao wrote:
>>
>> On Tue, Feb 27, 2018 at 4:45 PM, Arend van Spriel
>> wrote:
>>>
>>> On 2/27/2018 11:16 AM, Harsha Rao wrote:
Hi folks,
On 02/27/2018 07:30 AM, Harsha Rao wrote:
On Tue, Feb 27, 2018 at 4:45 PM, Arend van Spriel
wrote:
On 2/27/2018 11:16 AM, Harsha Rao wrote:
Hi folks,
I am developing a new wifi driver for our sdio based wifi device.
I see that SDIO_VENDOR_ID and SDIO_DEVICE_ID
On Tue, Feb 27, 2018 at 4:45 PM, Arend van Spriel
wrote:
> On 2/27/2018 11:16 AM, Harsha Rao wrote:
>>
>> Hi folks,
>> I am developing a new wifi driver for our sdio based wifi device.
>>
>> I see that SDIO_VENDOR_ID and SDIO_DEVICE_ID for our device (We had
>>
On 2/27/2018 11:16 AM, Harsha Rao wrote:
Hi folks,
I am developing a new wifi driver for our sdio based wifi device.
I see that SDIO_VENDOR_ID and SDIO_DEVICE_ID for our device (We had
bought the SDIO IP from 3rd party) is already been used by some
other vendor and its already into staging .
11 matches
Mail list logo