From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Giuliano Pochini <pochini@shiny.it>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: MIDI and PCMCIA
Date: Wed, 18 Jun 2003 14:34:51 +0200 [thread overview]
Message-ID: <s5hvfv34l90.wl@alsa2.suse.de> (raw)
In-Reply-To: <E19Sb7s-0002yL-00@sc8-sf-list1.sourceforge.net>
At Wed, 18 Jun 2003 07:34:42 -0400,
Paul Davis wrote:
>
> >struct. (although it has a xilinx firmware loading routine).
>
> just to make sure there is no misinformation going around: the
> "firmware" loaded by the hdsp driver has nothing to do with the xilinx
> fpga. its not even really "firmware" in the conventional sense. its
> actually configuration data for the i/o box attached to the pci/pcmcia
> card, and is written to the already running fpga, which passes it
> through/writes it to the i/o box. you can have a "running" hdsp card
> with no i/o box, but that's hardly what you'd call useful :)
thanks for the clarification.
for more notes about xilinx chip: in the case of vx-pocket drivers,
the xilinx chip works as a kind of boot-strapping. so, in this case,
the firmware to start up the xilinx chip is necessary to make the main
dsp chip accessible through it.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
prev parent reply other threads:[~2003-06-18 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-14 23:41 MIDI and PCMCIA Giuliano Pochini
2003-06-14 22:06 ` Paul Davis
2003-06-17 22:59 ` Giuliano Pochini
2003-06-18 10:59 ` Takashi Iwai
2003-06-18 11:34 ` Paul Davis
2003-06-18 12:34 ` Takashi Iwai [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=s5hvfv34l90.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.com \
--cc=pochini@shiny.it \
/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.