[wdmaudiodev] Re: Raspberry Pi OTG Audio
- From: "Matthew van Eerde" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "Matthew.van.Eerde" for DMARC)
- To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Sat, 10 Feb 2018 00:28:48 +0000
Can you send more of setupapi.dev.log, e.g. from the !!! line all the way up to
the closest blank line? I want to see what the compatible ID is (in particular
whether it’s USB\Class_01&…&Prot_00 or USB\Class_01&…&Prot_20, which is to say
USB Audio 1.0 or USB Audio 2.0 respectively)
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Robert Bielik <Robert.Bielik@xxxxxxxxx>
Sent: Friday, February 9, 2018 6:41:39 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Raspberry Pi OTG Audio
I'll try patch this myself also see if it works out.
Ok, patched the linux kernel so that wTotalLength is calculated correctly,
still the audio gadget device does not load entirely.
Excerpt from setupapi.dev.log:
sto: {Configure Driver Package: exit(0x00000000)}
dvi: Install Device: Configuring device class.
15:36:08.031
dvi: Install Device: Configuring device class
completed. 15:36:08.038
dvi: Device Status: 0x01806400, Problem: 0x1
(0xc0000493)
dvi: Install Device: Starting device
'USB\VID_1D6B&PID_0104\DEADBEEF00115599'. 15:36:08.045
dvi: Install Device: Starting device completed.
15:36:08.070
!!! dvi: Device not started: Device has problem: 0x0a
(CM_PROB_FAILED_START), problem status: 0xc0440025.
☹
Any ideas welcomed.
Regards
/Robert
X3
Other related posts: