All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@vis.ethz.ch>
To: alsa-devel@alsa-project.org
Subject: Driver(s) for IEEE 1394 based break out boxes
Date: Mon, 12 Jul 2004 21:19:30 +0200	[thread overview]
Message-ID: <20040712191930.GA20382@vis.ethz.ch> (raw)

Hi,

There're several IEEE 1394 based break out boxes on the market for
which no drivers exist for Linux [1] (The web site has a translation
to english, but the content seems to disappear, at least for the IEEE
1394 boxes.) .  The interesting fact about those boxes is that all
but one are using the same chip (dm1000).  Furthermore, the
communication protocol(s) between break out box and computer is
documented and "public" available.  Yes, you have to be member of those
groups to read the documents but in the general idea it's available.

Relevant standards are:
  IEC 61883
  1394ta AVC
  1394ta Audio and Music Data Transmission Protocol

I'm still trying to figure out what's the best way to write a driver.

On the on hand, there exists already the IEEE 1394 stack with IEC
61883 support in user-land.  I don't know if the libiec61883 is already
ready to use but still it exists.  As I understand the general idea
behind libraw1394 and libiec61883 is to do as much as possible in
users-pace.  Any application which wants to take advantage of IEEE 1394
based sound cards has to use those libraries.  I guess it means for
jack to have a new backend in order to use those cards.  But most
application wont be aware of this interface, I suppose.

On the other hand ALSA provides a well known interface which most
sound based application are using.  To write a new driver for a sound
card, you end up writing an ALSA kernel driver because libasound is
not designed to use other interfaces than the ALSA kernel interface
(this is an assumption).  So it is not possible to use libraw1394 and
libiec61883.  A new kernel driver has to be written with implements
those parts.  Of course it needs some more things but I'm just writing
my lousy ordered thoughts down.

The question is which way to go?  Get the break out boxes working with
the existing libraries or write an ALSA driver which implements those
parts again?  Personaly, I think ALSA might be the better idea but it
does not make use of the already written code.  Maybe there exists a
better way...

thanks,
daniel

[1]  http://www.soundkartenkatalog.de/deu2/pi-1117011340.htm?categoryId=28



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

             reply	other threads:[~2004-07-12 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 19:19 Daniel Wagner [this message]
2004-07-13 16:41 ` Driver(s) for IEEE 1394 based break out boxes Takashi Iwai
2004-07-13 17:26   ` Jack O'Quin
2004-07-13 21:38     ` Daniel Wagner
2004-07-13 21:34   ` Daniel Wagner
2004-07-13 21:44     ` Steve Harris

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=20040712191930.GA20382@vis.ethz.ch \
    --to=wagi@vis.ethz.ch \
    --cc=alsa-devel@alsa-project.org \
    /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.