From: Sam Ravnborg <sam@ravnborg.org>
To: Dan Malek <dan@embeddededge.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Efficient handling of RTP frames?
Date: Mon, 10 May 2004 23:33:36 +0200 [thread overview]
Message-ID: <20040510213336.GA4496@mars.ravnborg.org> (raw)
In-Reply-To: <548E72DE-A2C7-11D8-95B9-003065F9B7DC@embeddededge.com>
On Mon, May 10, 2004 at 05:16:40PM -0400, Dan Malek wrote:
>
> >Can anyone point in a direction where to find more information
> >about how to realise this in the most efficiet way?
>
> Without any more knowledge of your protocol details, you'll
> probably want to design the software to reduce the amount of
> interrupts. There are buffer management concerns, such as
> alignment and location, but all of this depends on all of your
> system requirements outside of this processing. Where is
> the RTP processing being done, on the 8xxx or the external device?
All (or most) procesing will be done outside the 82xx. The main
purpose of the 82xx will be to do a simple conversion to/from
RTP - since the external DSP will not use this format.
The alignment concerns you mention I expect can be addressed
we anyway have to develop a driver for the DSP connected to the FCC.
The buffer management needs a second thought.
But I still do not see how the two drivers can 'communicate',
or what other requirements is put on the driver that communicate
with the DSP.
Sam
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-10 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 20:58 Efficient handling of RTP frames? Sam Ravnborg
2004-05-10 21:16 ` Dan Malek
2004-05-10 21:33 ` Sam Ravnborg [this message]
2004-05-11 1:55 ` Dan Malek
2004-05-10 22:22 ` Eugene Surovegin
2004-05-11 8:28 ` Matevz Langus
-- strict thread matches above, loose matches on Subject: below --
2004-05-11 21:42 sam
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=20040510213336.GA4496@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@lists.linuxppc.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 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).