linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Harsha Rao <harshrao464@gmail.com>
Cc: Steve deRosier <derosier@gmail.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Support on vendor id and device id
Date: Wed, 28 Feb 2018 10:38:28 +0100	[thread overview]
Message-ID: <5A967894.9090900@broadcom.com> (raw)
In-Reply-To: <CAPcv9S2gwDL6Jikxot2yS4daYaFQN6mEMx3vuY5w+ma_6wHCew@mail.gmail.com>

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 of the wilc1000 chip. And,
>>>> >>>often WiFi chips will let you change the VID/PID somewhere within
>>>> >>>whatever non-volatile storage it has (like where it stores the MAC
>>>> >>>address).
>> >
>> >
>> >So it seems the wilc1000 devices from Microchip/Atmel are also using a
>> >vendor id they did not buy. Could be that the mentioned 3rd party providing
>> >the SDIO IP actually owns that vendor id, but if you are building your wifi
>> >chip on that you should better buy you own vendor id from the SD
>> >Association. Now if Harsha is actually working for Microchip (unclear to me)
>> >there is basically one party that should go shopping.
>> >
> I would like to clarify that I am not building anything on top of
> microchip wifi device.
> We have a different HW . Its been just that 3rd party vendor providing
> SDIO IP has given
> same ID to different customers.

So it is as I said, ie. you are using the 3rd party SDIO IP as is and 
add your own wifi IP to it? So what does the term "SDIO IP" mean here. 
Is it a piece of hardware that you hook up to your wifi hardware or is 
it VHDL/verilog in which the vendor id is defined. If it is VHDL you 
should really get your own vendor id from the SD Association and fix it. 
Otherwise, the 3rd party hardware should have means to change it. If 
not, you better find another party.

Regards,
Arend

  reply	other threads:[~2018-02-28  9:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 10:16 Support on vendor id and device id Harsha Rao
2018-02-27 11:15 ` Arend van Spriel
2018-02-27 13:30   ` Harsha Rao
2018-02-27 15:14     ` Larry Finger
2018-02-27 15:29       ` Harsha Rao
2018-02-27 17:15         ` Steve deRosier
2018-02-27 17:34           ` Steve deRosier
2018-02-27 20:04             ` Arend van Spriel
2018-02-27 23:14               ` Harsha Rao
2018-02-28  9:38                 ` Arend van Spriel [this message]
2018-03-01 10:10                   ` Harsha Rao
2018-03-13 19:23                     ` Arend van Spriel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5A967894.9090900@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=derosier@gmail.com \
    --cc=harshrao464@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).