Return-path: Received: from mail-it0-f53.google.com ([209.85.214.53]:54761 "EHLO mail-it0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967488AbeCAKKD (ORCPT ); Thu, 1 Mar 2018 05:10:03 -0500 Received: by mail-it0-f53.google.com with SMTP id c11so7043674ith.4 for ; Thu, 01 Mar 2018 02:10:03 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <5A967894.9090900@broadcom.com> References: <5A953DBE.9070805@broadcom.com> <68f5549d-b8ad-85fb-4e80-50c53cac8108@lwfinger.net> <5A95B9B2.4040403@broadcom.com> <5A967894.9090900@broadcom.com> From: Harsha Rao Date: Thu, 1 Mar 2018 15:40:02 +0530 Message-ID: (sfid-20180301_111051_577659_68A2DA15) Subject: Re: Support on vendor id and device id To: Arend van Spriel Cc: Steve deRosier , Larry Finger , linux-wireless Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: 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 >>>>> >>>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 Thank you folks for your comments. The SDIO IP is VHDL IP core integrated on our SoC. And we figured out a way to update vendor ID at run-time during boot. We would get our own vendor ID from SD association and proceed . - Harsha