From: Takashi Iwai <tiwai@suse.de>
To: Cyrus Harmon <cyrus@bobobeach.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] add Steinberg UR44 USB Audio Interface support to quirks-table
Date: Thu, 06 Nov 2014 00:14:16 +0100 [thread overview]
Message-ID: <s5hvbmt8cl3.wl-tiwai@suse.de> (raw)
In-Reply-To: <5458946F.5060100@bobobeach.com>
At Tue, 04 Nov 2014 00:55:11 -0800,
Cyrus Harmon wrote:
>
>
> I have used a number of 3.1x kernels. At the moment, I'm writing this
> from a 3.17.0 kernel that doesn't recognize the UR44 without my patch.
OK, could you repost the patch (and put me to Cc) so that I can apply
to for-next branch?
thanks,
Takashi
>
> thanks,
>
> Cyrus
>
> On 11/03/2014 10:28 PM, Takashi Iwai wrote:
> > At Mon, 03 Nov 2014 16:36:58 -0800,
> > Cyrus Harmon wrote:
> >>
> >> Well, it's 7 months on and I'm still using a patched kernel to access my
> >> UR44. Any chance of either seeing my original patch committed, or some
> >> suggestions on a more proper fix, if there's something with my original
> >> patch?
> > Which kernel version are you testing?
> >
> >
> > Takashi
> >
> >> thanks,
> >>
> >> Cyrus
> >>
> >> On 03/17/2014 09:29 AM, Cyrus Harmon wrote:
> >>> On Mar 11, 2014, at 1:31 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> >>>
> >>>> Cyrus Harmon wrote:
> >>>>> On Mar 10, 2014, at 8:40 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> >>>>>> In theory, kernel 3.11 and later should support this device without
> >>>>>> a quirk entry. I guess it actually does not?
> >>>>> no, the stock kernel doesn’t support this device.
> >>>> Strange; in theory, the driver should be able to pick up these
> >>>> descriptors.
> >>>>
> >>>> Are there any error messages in the system log when you plug it in or
> >>>> reload the unpatch snd-usb-audio driver?
> >>> Following up on this from last week, here’s the error message I see with an unpatched kernel:
> >>>
> >>> Mar 11 02:25:11 cbox kernel: [ 82.426640] usb 2-1.6: new high-speed USB device number 4 using ehci-pci
> >>> Mar 11 02:25:12 cbox kernel: [ 82.515364] usb 2-1.6: New USB device found, idVendor=0499, idProduct=150e
> >>> Mar 11 02:25:12 cbox kernel: [ 82.515368] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> >>> Mar 11 02:25:12 cbox kernel: [ 82.515370] usb 2-1.6: Product: Steinberg UR44
> >>> Mar 11 02:25:12 cbox kernel: [ 82.515372] usb 2-1.6: Manufacturer: Yamaha Corporation
> >>> Mar 11 02:25:12 cbox kernel: [ 82.518134] snd-usb-audio: probe of 2-1.6:1.0 failed with error -5
> >>> Mar 11 02:25:12 cbox kernel: [ 82.523317] snd-usb-audio: probe of 2-1.6:1.1 failed with error -5
> >>> Mar 11 02:25:12 cbox mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6"
> >>> Mar 11 02:25:12 cbox mtp-probe: bus: 2, device: 4 was not an MTP device
> >>>
> >>> Any suggestions for further debugging this?
> >>>
> >>> Also, from an earlier message,
> >>>
> >>> On Mar 10, 2014, at 8:40 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> >>>
> >>>> This sounds as if the playback stream needs to be synchronized to the
> >>>> recording stream
> >>> Any pointers on where I might look to figure out how to do this?
> >>>
> >>> thanks again,
> >>>
> >>> Cyrus
> >>>
> >>> _______________________________________________
> >>> Alsa-devel mailing list
> >>> Alsa-devel@alsa-project.org
> >>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >> _______________________________________________
> >> Alsa-devel mailing list
> >> Alsa-devel@alsa-project.org
> >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >>
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2014-11-05 23:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 18:12 [PATCH] add Steinberg UR44 USB Audio Interface support to quirks-table Cyrus Harmon
2014-03-10 9:42 ` Takashi Iwai
2014-03-10 12:07 ` Clemens Ladisch
2014-03-10 15:26 ` Cyrus Harmon
2014-03-10 15:30 ` Takashi Iwai
2014-03-10 15:40 ` Clemens Ladisch
2014-03-11 6:33 ` Cyrus Harmon
2014-03-11 8:31 ` Clemens Ladisch
2014-03-11 9:30 ` Cyrus Harmon
2014-03-17 16:29 ` Cyrus Harmon
2014-11-04 0:36 ` Cyrus Harmon
2014-11-04 6:28 ` Takashi Iwai
2014-11-04 8:55 ` Cyrus Harmon
2014-11-05 23:14 ` Takashi Iwai [this message]
2014-11-06 4:39 ` Cyrus Harmon
2014-11-06 5:28 ` Vlad Catoi
2014-11-06 5:32 ` Cyrus Harmon
2014-11-06 13:46 ` Vlad Catoi
2014-11-04 8:59 ` Clemens Ladisch
2014-11-04 9:00 ` Clemens Ladisch
2014-11-05 18:16 ` Cyrus Harmon
2014-11-05 21:17 ` Clemens Ladisch
2014-11-06 5:47 ` Cyrus Harmon
2014-11-15 13:00 ` Clemens Ladisch
2015-02-03 7:14 ` Cyrus Harmon
2014-11-06 16:05 ` Cyrus Harmon
2014-11-06 16:49 ` Takashi Iwai
2014-11-06 16:54 ` Cyrus Harmon
2014-11-08 4:24 ` Vlad Catoi
2014-11-08 4:25 ` Vlad Catoi
2015-02-03 6:56 ` Cyrus Harmon
2015-02-03 9:02 ` Takashi Iwai
2014-11-06 17:32 ` Clemens Ladisch
-- strict thread matches above, loose matches on Subject: below --
2014-03-10 15:37 Cyrus Harmon
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=s5hvbmt8cl3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=cyrus@bobobeach.com \
/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