From: Martijn Sipkema <msipkema@sipkema-digital.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: MTP-AV problems (Re: intel8x0 sequencer & MTP-AV)
Date: Thu, 13 Feb 2003 16:21:17 +0100 [thread overview]
Message-ID: <000c01c2d373$8e27ada0$161b14ac@boromir> (raw)
In-Reply-To: s5hel6cky69.wl@alsa2.suse.de
[...]
> > I suppose this doesn't mention AMT? Can I have this information. It
> > might contain more than what I already have.
>
> the info appeared in another thread (running-status bug on mtpav):
> http://www.math.tu-berlin.de/~sbartels/unitor/unitor8_doc.txt
> the project itself seems dead now...
That's the info I already had... :(
I don't see why Emagic won't give the AMT protocol specs...
--ms
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-02-13 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1044258789.30428.61.camel@littlewolf2.littlewolf>
[not found] ` <s5h3cn5ino4.wl@alsa2.suse.de>
2003-02-03 11:59 ` intel8x0 sequencer & MTP-AV Allan Klinbail
2003-02-13 14:34 ` MTP-AV problems (Re: intel8x0 sequencer & MTP-AV) Takashi Iwai
2003-02-13 15:05 ` Martijn Sipkema
2003-02-13 15:17 ` Takashi Iwai
2003-02-13 15:21 ` Martijn Sipkema [this message]
2003-02-14 3:26 ` Allan Klinbail
2003-02-14 11:38 ` Takashi Iwai
2003-02-16 9:58 ` MTP-AV problems (Re: intel8x0 sequencer & MTP-AV) - success Allan Klinbail
2003-02-16 21:06 ` Ryan Pavlik
2003-02-17 5:00 ` Allan Klinbail
2003-02-17 5:30 ` Ryan Pavlik
2003-02-17 10:56 ` Takashi Iwai
2003-02-17 11:36 ` Allan Klinbail
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='000c01c2d373$8e27ada0$161b14ac@boromir' \
--to=msipkema@sipkema-digital.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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