From: Lee Revell <rlrevell@joe-job.com>
To: Fruhwirth Clemens <clemens@endorphin.org>
Cc: Clemens Ladisch <clemens@ladisch.de>, alsa-devel@lists.sourceforge.net
Subject: Re: [ALSA - driver 0000955]: CN-126 - USB 5.1 Audio adapter
Date: Fri, 04 Mar 2005 13:32:46 -0500 [thread overview]
Message-ID: <1109961167.6442.11.camel@mindpipe> (raw)
In-Reply-To: <1109863466.13335.6.camel@ghanima>
On Thu, 2005-03-03 at 16:24 +0100, Fruhwirth Clemens wrote:
> I wonder what's the cause. Has Creative delivered a non-standard
> compliant device one more time? The original EMU10K1 was also FUBAR wrt
> to the PCI standard.
I guess you are referring to only being able to DMA into a 29 bit
address space?
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-04 18:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 9:34 [ALSA - driver 0000955]: CN-126 - USB 5.1 Audio adapter Fruhwirth Clemens
2005-03-03 10:35 ` Jaroslav Kysela
2005-03-03 11:35 ` Clemens Ladisch
2005-03-03 15:24 ` Fruhwirth Clemens
2005-03-04 8:31 ` SB Live 24 Ext (was: [ALSA - driver 0000955]: CN-126 - USB 5.1 Audio adapter) Clemens Ladisch
2005-03-04 9:57 ` Fruhwirth Clemens
2005-03-04 11:09 ` Clemens Ladisch
2005-03-04 11:55 ` Fruhwirth Clemens
2005-03-04 18:32 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-22 2:28 [ALSA - driver 0000955]: CN-126 - USB 5.1 Audio adapter bugtrack
2005-09-22 12:56 bugtrack
2005-03-02 14:07 bugtrack
2005-03-02 13:19 bugtrack
2005-03-02 11:58 bugtrack
2005-03-02 11:48 bugtrack
2005-03-02 11:46 bugtrack
2005-03-02 11:44 bugtrack
2005-03-02 11:34 bugtrack
2005-03-02 8:28 bugtrack
2005-03-01 23:13 bugtrack
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=1109961167.6442.11.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@endorphin.org \
--cc=clemens@ladisch.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 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.