All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Patrick Shirkey <pshirkey@boosthardware.com>,
	Peter Enderborg <pme@ufh.se>,
	alsa-devel@lists.sourceforge.net
Subject: Re: soundcard matrix (more)(
Date: Mon, 01 Dec 2003 15:14:21 +0100	[thread overview]
Message-ID: <s5hr7zoaama.wl@alsa2.suse.de> (raw)
In-Reply-To: <200312011359.hB1Dxraf013635@oud.linuxaudiosystems.com>

At Mon, 01 Dec 2003 08:59:53 -0500,
Paul Davis wrote:
> 
> >has anyone contact with yamaha, btw?
> 
> i've spoken in person with guys inside the mLAN development group (at
> NAMM, last februrary), and they put me in touch with a professor in
> south africa who has been acting as a consultant for them on a number
> of aspects of mLAN. i talked with him a few times too, he's quite a
> fan of linux.
 
it's a good news, at least :)

> my understanding of the end result of this conversation was that:
> 
>    * the core part of mLAN is already part of an IEEE standard

ok, that's what i understood, too.
as long as the m-audio device doesn't depend too much on the mlan
connection stuff below, we'll be able to use it in a certain level.
IIRC, linux ieee1394 stuff has already the audio iso transfer
support.  the question is how tightly they are bound.

m-audio people are so far very helpful for the development on linux,
and they want that their products are well supported, too.
maybe we can contact with them about the detailed technical info of
410.


>    * the part that Yamaha is retaining right now is the connection
>        management stuff. they are not unwilling to release this,
>        but they are also not particularly enthusiastic about it
>        and nobody knows who has authority to do so. they have
>        licensing schemes for this part, but eventually hope to
>        see it merged into either the existing IEEE standard
>        or a new one.

hmm, it sounds like they are in fact not refusing to get the mlan
spec open but even try to standarlize?

> note: without connection management, mLAN looks like the ALSA
> sequencer but without any way to know which ports exist. its not
> useless, but its very hard to use.

as always, another abstraction layer on that layer... :)

thanks for the info!


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

      reply	other threads:[~2003-12-01 14:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 21:42 soundcard matrix Martin Langer
2003-11-26 23:04 ` Apostolos
2003-11-26 23:05 ` Apostolos Dimitromanolakis
2003-11-28 14:10 ` Takashi Iwai
2003-11-29 13:14   ` Peter Enderborg
2003-11-29 13:34     ` soundcard matrix (more)( Peter Enderborg
2003-12-01 12:48       ` Patrick Shirkey
2003-12-01 13:02         ` Takashi Iwai
2003-12-01 13:59           ` Paul Davis
2003-12-01 14:14             ` 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=s5hr7zoaama.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=paul@linuxaudiosystems.com \
    --cc=pme@ufh.se \
    --cc=pshirkey@boosthardware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.