From: Dale Amon <amon@vnl.com>
To: Russell Coker <russell@coker.com.au>
Cc: Dale Amon <amon@vnl.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: file_contexts/types.fc
Date: Fri, 27 Aug 2004 18:10:45 +0100 [thread overview]
Message-ID: <20040827171045.GA18446@vnl.com> (raw)
In-Reply-To: <200408280305.02429.russell@coker.com.au>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
On Sat, Aug 28, 2004 at 03:05:02AM +1000, Russell Coker wrote:
> > It usually means Digital Signal Processor.
>
> Yes, the issue however is what a DSP board is. Is it a software modem/sound
> card device (like the MWave cards in older Thinkpads)? Is it a numeric
> co-processor for offloading some computations from the main CPU (useful for
> sound/video processing)?
The only ones I'm familiar with were boards that
had one or more DSP chips on them for massive
offboard general purpose signal processing. There
was a dandy one for NeXT's from IRCAM many years
back...
--
------------------------------------------------------
Dale Amon amon@islandone.org +44-7802-188325
International linux systems consultancy
Hardware & software system design, security
and networking, systems programming and Admin
"Have Laptop, Will Travel"
------------------------------------------------------
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-27 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 11:41 file_contexts/types.fc Russell Coker
2004-08-27 15:25 ` file_contexts/types.fc Dale Amon
2004-08-27 17:05 ` file_contexts/types.fc Russell Coker
2004-08-27 17:10 ` Dale Amon [this message]
2004-08-27 17:21 ` file_contexts/types.fc Russell Coker
2004-08-27 21:08 ` file_contexts/types.fc James Carter
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=20040827171045.GA18446@vnl.com \
--to=amon@vnl.com \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/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.