alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: errordeveloper@gmail.com
To: Eliot Blennerhassett <linux@audioscience.com>,
	alsa-devel@alsa-project.org
Subject: Re: Kirkwood SoC - AVB support questions ..?
Date: Sat, 10 Jul 2010 12:01:05 +0100	[thread overview]
Message-ID: <20100710110105.GM7638@00110101.home> (raw)
In-Reply-To: <4C382C37.7090904@audioscience.com>

Ok, so it's really no wonder about these,
those proprietary are hendeled transparently by an ASIC or an FPGA.

so this won't be the case with AVB,
i suppose at low sampling (48k or 44k1) it will work over a regular
network, provided the host is doing only AVB streaming and there is
no other trafic on the network.
I'm not intery sure how stream reservation would work, but may be
you can fake it in software somehow.

there is PTP driver patch here:
http://kerneltrap.org/mailarchive/linux-netdev/2010/4/29/6276033

it seems to be ptpv1 ..hm
this ptpd list thread is about patents:
http://lists.infradead.org/pipermail/ptpd/2010-January/000023.html

could these patents be such a problem?
will AVB support have to be distributed trough patches because of this?


well ..i haven't used Netjack or anything, so cannot tell.

On Sat, Jul 10, 2010 at 08:15:51PM +1200, Eliot Blennerhassett wrote:
> On 10/07/10 08:01, errordeveloper@gmail.com wrote:
> 
> > How are the CobraNet and EtherSound drivers designed, has anyone used
> > those cards ?? (one was from DigiGram and another from Audio Science IIRC)
> 
> AudioScience ASI6416 and AS6316 cards use cobranet processor from
> Cirrus, and appear to the host as a standard soundcard.
> 
> Similarly, ASI6585 uses hardware implementation of Axia livewire protocol.
> 
> So, none of the network audio protocol is handled by the host PC.
> 
> 
> -- 
> Eliot Blennerhassett
> AudioScience Inc.

      reply	other threads:[~2010-07-10 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 20:01 Kirkwood SoC - AVB support questions ..? errordeveloper
2010-07-10  8:15 ` Eliot Blennerhassett
2010-07-10 11:01   ` errordeveloper [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=20100710110105.GM7638@00110101.home \
    --to=errordeveloper@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux@audioscience.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).