lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <278bcd0d.7189.17b4e479a3a.Coremail.slark_xiao@163.com>
Date:   Mon, 16 Aug 2021 17:25:20 +0800 (CST)
From:   "Slark Xiao" <slark_xiao@....com>
To:     "Greg KH" <gregkh@...uxfoundation.org>
Cc:     "Reinhard Speyerer" <rspmn@...or.de>, johan@...nel.org,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re:Re: Re: [PATCH] [V2,1/1]USB: serial: option: add Foxconn T77W175
 composition 0x901d

















At 2021-08-16 17:20:59, "Greg KH" <gregkh@...uxfoundation.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.
 
Thanks

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ