From: Cyril Hrubis Subject: Re: TASCAM US-122mkII Date: Fri, 19 Aug 2011 15:11:04 +0200 Message-ID: <20110819131104.GA1913@yumi.suse.cz> References: <20110819100156.GA31665@yumi> <20110819113727.GA9522@yumi> <1313759213.3673.40.camel@mattotaupa> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-fx0-f51.google.com (mail-fx0-f51.google.com [209.85.161.51]) by alsa0.perex.cz (Postfix) with ESMTP id 27D57246A0 for ; Fri, 19 Aug 2011 15:11:03 +0200 (CEST) Received: by fxh10 with SMTP id 10so2102001fxh.38 for ; Fri, 19 Aug 2011 06:11:03 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1313759213.3673.40.camel@mattotaupa> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Paul Menzel Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Hi! > > > As far as I understand it, there are two endpoints for audio and two for > > > MIDI. The MIDI part seems to be initalized fine although I don't have > > > any MIDI device to test it. > > > > > > And in the log from windows machine the audio part does some > > > intialization and then only buch of isochronous transfers. > > > > Hmm, so it seems that our only option is really to look at these > > Windows dumps and reverse-engineer the protocol. > > Is there a chance to talk to the manufacturer or are they known to not > cooperate? Cyril, did you contact their support? Hmm, haven't though of this, but that may be worth of try. -- Cyril Hrubis