From: torbenh <torbenh@gmx.de>
To: Christian Riesch <christian.riesch@omicron.at>
Cc: Richard Cochran <richardcochran@gmail.com>,
john stultz <johnstul@us.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Richard Cochran <richard.cochran@omicron.at>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [PATCH 2/3] ptp: add a software clock based on clock_monotonic_raw
Date: Fri, 11 Mar 2011 14:38:52 +0100 [thread overview]
Message-ID: <20110311133852.GB5553@siel.b> (raw)
In-Reply-To: <95DC1AA8EC908B48939B72CF375AA5E3011C9E20A4@alice.at.omicron.at>
On Fri, Mar 11, 2011 at 12:37:57PM +0100, Christian Riesch wrote:
> Torben,
>
> On Friday, March 11, 2011 12:13, torbenh wrote:
> >On the audio lists, we have a guy now claiming that software ptp would
> >confuse the whole h/w ptp infrastructure. His main agenda seems to be to
> >prevent a software only ptp/avb implementatation.
>
> could you please post a link to that discussion?
duncan started somewhat like this:
http://article.gmane.org/gmane.comp.audio.jackit/23606
http://article.gmane.org/gmane.comp.audio.jackit/23612
then it seems that he somehow turned his head:
http://www.mail-archive.com/linux-audio-dev@lists.linuxaudio.org/msg11765.html
maybe we have a communication problem, with the definition of "play"
i only want to be able to generate an RTP stream on my computer.
the actual conversion from packets to analog signal would be happening on a
networked soundcard. the goal is to achieve low latency in the range of
2-3ms ...
maybe he interprets playing the rtp stream, as converting the rtp
packets to analog audio.
this obviously wouldnt work with software ptp, because we would need
nanoseconds accuracy of the clock.
but to just create an rtp stream, where a 2ms buffer doesnt underflow,
just requires a clock accuracy of 500us.
all in all this discussion might be a bit confusing.
> Thanks,
> Christian
--
torben Hohn
next prev parent reply other threads:[~2011-03-11 13:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 17:26 some patches for the ptp framework Torben Hohn
2011-03-03 17:26 ` [PATCH 1/3] remove __cpuinit from mwait_usable() Torben Hohn
2011-03-03 17:26 ` [PATCH 2/3] ptp: add a software clock based on clock_monotonic_raw Torben Hohn
2011-03-03 19:34 ` john stultz
2011-03-04 6:46 ` Richard Cochran
2011-03-04 11:06 ` torbenh
2011-03-05 20:08 ` john stultz
2011-03-06 13:28 ` Richard Cochran
2011-03-11 11:13 ` torbenh
2011-03-11 11:37 ` Christian Riesch
2011-03-11 13:38 ` torbenh [this message]
2011-03-11 11:56 ` Christian Riesch
2011-03-04 6:42 ` Richard Cochran
2011-03-04 11:30 ` torbenh
2011-03-04 16:10 ` Richard Cochran
2011-03-03 17:26 ` [PATCH 3/3] Check for write permission on FD based posix-clocks Torben Hohn
2011-03-04 7:22 ` Richard Cochran
2011-03-04 9:55 ` Arnd Bergmann
2011-03-04 10:13 ` torbenh
2011-03-11 19:46 ` Thomas Gleixner
2011-03-12 17:23 ` Richard Cochran
2011-03-12 17:35 ` Thomas Gleixner
2011-03-12 20:30 ` [tip:timers/core] posix-clocks: Check write permissions in posix syscalls tip-bot for Torben Hohn
2011-03-04 6:21 ` some patches for the ptp framework Richard Cochran
2011-03-10 7:02 ` Richard Cochran
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=20110311133852.GB5553@siel.b \
--to=torbenh@gmx.de \
--cc=christian.riesch@omicron.at \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.cochran@omicron.at \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.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