From: "Slark Xiao" <slark_xiao@163.com>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: "Reinhard Speyerer" <rspmn@arcor.de>,
johan@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re:Re: Re: Re: Re: [PATCH] [V2,1/1]USB: serial: option: add Foxconn T77W175 composition 0x901d
Date: Tue, 17 Aug 2021 14:51:34 +0800 (CST) [thread overview]
Message-ID: <31fcfd4a.2432.17b52e12d52.Coremail.slark_xiao@163.com> (raw)
In-Reply-To: <YRtYTFFCNn/xp2Hr@kroah.com>
At 2021-08-17 14:33:48, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>On Tue, Aug 17, 2021 at 10:27:05AM +0800, Slark Xiao wrote:
>>
>>
>
><blank lines snipped, please fix your email client...>
>
>>> At 2021-08-16 19:17:11, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>> >On Mon, Aug 16, 2021 at 05:25:20PM +0800, Slark Xiao wrote:
>> >> At 2021-08-16 17:20:59, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>> >> >On Mon, Aug 16, 2021 at 05:17:00PM +0800, Slark Xiao wrote:
>> >> >> So should I use USB_DEVICE_INTERFACE_NUMBER(QUALCOMM_VENDOR_ID, 0x901d, 0x00) to bind Diag port only?
>> >> >
>> >> >Why is this device using the QUALCOMM vendor id anyway? Is this allowed
>> >> >by Qualcomm?
>> >> >
>> >> >thanks,
>> >> >
>> >> >greg k-h
>> >>
>> >> Hi Greg,
>> >> Our product are designed based on Qualcomm SDX55 platform. So it still support Qualcomm vendor ID.
>> >> I think there is no infringement about this ID combo.
>> >
>> >Do you have permission from Qualcomm to use their vendor id? I know
>> >some vendors get very upset about this...
>> >
>> >Why not use your own vendor id?
>> >
>> >thanks,
>> >
>> >greg k-h
>>
>> Hi Greg,
>> As Qualcomm mainly provide service to their customer, like Samsung, Apple, Huawei, Quectel, Foxconn, Sierra and so on, so I believe all available VID/PIDs are allowed to use.
>
>That is not how USB VIDs work, sorry. Please get approval from the
>company whose VID you wish to use, otherwise they will be using it
>themselves for their own devices, and you will have a collision.
>
>thanks,
>
>greg k-h
Hi Greg,
I am checking this with Qualcomm side now. I will update the result once I get it.
Thank you for your advice.
next prev parent reply other threads:[~2021-08-17 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 3:54 [PATCH] [V2,1/1]USB: serial: option: add Foxconn T77W175 composition 0x901d Slark Xiao
2021-08-16 9:04 ` Reinhard Speyerer
2021-08-16 9:17 ` Slark Xiao
2021-08-16 9:20 ` Greg KH
2021-08-16 9:25 ` Slark Xiao
2021-08-16 11:17 ` Greg KH
2021-08-17 2:27 ` Slark Xiao
2021-08-17 6:33 ` Greg KH
2021-08-17 6:51 ` Slark Xiao [this message]
2021-08-16 15:47 ` Reinhard Speyerer
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=31fcfd4a.2432.17b52e12d52.Coremail.slark_xiao@163.com \
--to=slark_xiao@163.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rspmn@arcor.de \
/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).