From: Takashi Iwai <tiwai@suse.de>
To: R Chan <rspchan@starhub.net.sg>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Heaps of firewire audio: bridgeco, IEC61883 - any work being done?
Date: Wed, 11 Feb 2004 15:27:15 +0100 [thread overview]
Message-ID: <s5hfzdhbsjg.wl@alsa2.suse.de> (raw)
In-Reply-To: <4020ED64.6000207@starhub.net.sg>
At Wed, 04 Feb 2004 21:02:28 +0800,
R Chan wrote:
>
> Suddenly there seems to be a heap of Firewire (non-mLAN) semi-pro
> audio interfaces launched or to be launched. Some of the usual culprits are
> Tascam, M-Audio, Edirol, Presonus (Firepod not Firestation), Hercules,
> Mackie (firewire
> option card for Onyx mixers), Echo Audio. Now it would seem that most of
> them are using bridgeco chips (are there any others?). Is anyone working
> on supporting
> these 'cards' or 'fbbs' (firewire breakout boxes) or are specs even
> available?
no, at least both of Jaroslav and I don't work on firewire yet.
> Incidentally, any news on the mLAN front, i.e., Yamaha kindly releasing
> specs to the
> Alsa team (I wish)?
no... IIRC, Bob Ham worked on jack implementation?
Takashi
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
prev parent reply other threads:[~2004-02-11 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 13:02 Heaps of firewire audio: bridgeco, IEC61883 - any work being done? R Chan
2004-02-11 14:27 ` Takashi Iwai [this message]
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=s5hfzdhbsjg.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rspchan@starhub.net.sg \
/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