From: Wade Berrier <wberrier@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Sean Young <sean@mess.org>,
linux-media@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: mceusb xhci issue?
Date: Thu, 15 Sep 2016 16:48:04 -0600 [thread overview]
Message-ID: <20160915224804.GA14827@miniwade.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1609151447410.1396-100000@iolanthe.rowland.org>
On Thu Sep 15 15:13, Alan Stern wrote:
> On Sat, 10 Sep 2016, Wade Berrier wrote:
>
> > On Thu Aug 11 16:18, Alan Stern wrote:
> > > I never received any replies to this message. Should the patch I
> > > suggested be merged?
> > >
> >
> > Hello,
> >
> > I applied this updated patch to the fedora23 4.7.2 kernel and the mceusb
> > transceiver works as expected.
>
> Thank you for testing. Can you provide the "lsusb -v" output for the
> troublesome IR transceiver?
>
Here's the output:
Bus 001 Device 006: ID 1784:0006 TopSeed Technology Corp. eHome Infrared Transceiver
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x1784 TopSeed Technology Corp.
idProduct 0x0006 eHome Infrared Transceiver
bcdDevice 1.02
iManufacturer 1 TopSeed Technology Corp.
iProduct 2 eHome Infrared Transceiver
iSerial 3 TS004RrP
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 0
Device Status: 0x0001
Self Powered
Wade
next prev parent reply other threads:[~2016-09-15 22:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 4:06 mceusb xhci issue? Wade Berrier
2016-04-25 17:15 ` Sean Young
2016-04-26 3:16 ` Wade Berrier
2016-04-27 20:07 ` Sean Young
2016-05-15 2:29 ` Wade Berrier
2016-05-18 14:52 ` Wade Berrier
2016-07-09 14:59 ` Mauro Carvalho Chehab
2016-07-12 15:52 ` Alan Stern
2016-08-11 20:18 ` Alan Stern
2016-09-10 19:58 ` Wade Berrier
2016-09-15 19:13 ` Alan Stern
2016-09-15 22:48 ` Wade Berrier [this message]
2016-09-16 14:24 ` [PATCH] USB: change bInterval default to 10 ms Alan Stern
2016-09-16 15:02 ` Mauro Carvalho Chehab
2016-09-16 14:25 ` mceusb xhci issue? Alan Stern
2016-09-16 15:03 ` Mauro Carvalho Chehab
2016-09-15 19:37 ` Alan Stern
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=20160915224804.GA14827@miniwade.localdomain \
--to=wberrier@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=sean@mess.org \
--cc=stern@rowland.harvard.edu \
/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).