Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: sypwex@gmail.com, Clemens Ladisch <cladisch@googlemail.com>
Cc: alsa-user@lists.sourceforge.net, alsa-devel@alsa-project.org,
	daniel@caiaq.de
Subject: Re: [Alsa-user] snd-usb-caiaq (NI Maschine Mikro) device not recognised by alsa
Date: Mon, 21 Sep 2015 19:09:10 +0200	[thread overview]
Message-ID: <560039B6.2000204@zonque.org> (raw)
In-Reply-To: <CAGPstWtnvg=mE54JGaU8y0gTU8BwxkzMqnOFXW-VSVmtQtkJmQ@mail.gmail.com>

On 09/19/2015 11:20 AM, sypwex wrote:
> ow, sorry! I not mentioned that there is no PID of Maschine Mikro
> (0x1110) in caiaq device list
> _https://github.com/torvalds/linux/blob/v4.2/sound/usb/caiaq/device.h_
> 
> yes there is some endless dump from usbhid but I don't know how to deal
> with it
> $sudo usbhid-dump --entity=all --address=1:15
> http://pastebin.com/raw.php?i=KC96ERSV (300KiB)
> 
> ok, I've tried to extend the driver and end up with following doodad
> https://github.com/krasnobaev/linux/commits/feature/caiaq-mmikro-1
> for every commit I've generated dmesg log
> _http://pastebin.com/raw.php?i=pJzdAyf4_

Maschine Mikro is a class compliant USB device which implements a
completely different protocol compared to the old devices. The
snd-usb-caiaq driver is unsuitable of handling and of the details
exposed by device, so this approach is definitely a dead end.

What does 'lsusb -v' show when you plug in the device?


Thanks,
Daniel

  reply	other threads:[~2015-09-21 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGPstWvoprjRHN2+xZe5w+=pPkOqcqQdR4t7bYY_MgXwKbPD4A@mail.gmail.com>
     [not found] ` <55EC7191.8020107@googlemail.com>
2015-09-19  9:20   ` [Alsa-user] snd-usb-caiaq (NI Maschine Mikro) device not recognised by alsa sypwex
2015-09-21 17:09     ` Daniel Mack [this message]
2015-09-21 20:10       ` sypwex
2015-09-22 11:17         ` Daniel Mack
2015-09-22 19:03           ` sypwex
2015-09-23  6:44             ` Daniel Mack
2015-09-24  9:04               ` sypwex

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=560039B6.2000204@zonque.org \
    --to=daniel@zonque.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=cladisch@googlemail.com \
    --cc=daniel@caiaq.de \
    --cc=sypwex@gmail.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