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: <CAGRyCJFxe4sg_GhimQjTG+jSb8CYJRP3wGcJDEJSq6Uek0Y_iQ@mail.gmail.com>
Date:	Wed, 30 Jan 2013 08:13:28 +0100
From:	Daniele Palmas <dnlplm@...il.com>
To:	Bjørn Mork <bjorn@...k.no>
Cc:	Dan Williams <dcbw@...hat.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Matthias Urlichs <smurf@...rf.noris.de>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] USB: option: add support for Telit LE920

Hello,

2013/1/29 Bjørn Mork <bjorn@...k.no>:
> Dan Williams <dcbw@...hat.com> writes:
>> On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
>>> From: danielepa <danielepa@...11.(none)>
>>>
>>> Add PID and special handling for Telit LE920
>>
>> Any idea what interfaces 1 and 5 are?  Is one perhaps a pseudo-ethernet
>> interface that could be used instead of PPP?  What's the lsusb -v output
>> for the device?
>
> Daniele has already posted a patch adding intf #5 to qmi_wwan, so I
> assume that is verified to be a QMI/rmnet interface.
>
> But I was wondering about #1 too, if that indeed is a vendor specific
> interface providing a non-serial, non-rmnet function.  What could that
> be?
>
>
> Bjørn

The output of lsusb for interface #1 is the following:

Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass     66
      bInterfaceProtocol      1
      iInterface              0

It should be an adb device, so probably it is not needed to blacklist
it. Should I resend a new patch with only interface #5 reserved?

Thanks,
Daniele
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ