From: Pavel Polischouk <pavelvp@inbox.ru>
To: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/2] M-Audio USB Documentation
Date: Mon, 27 Nov 2006 10:20:24 -0500 [thread overview]
Message-ID: <456B0238.80103@inbox.ru> (raw)
In-Reply-To: <017e01c71219$d04a2170$161ce4a0@supelec.fr>
Thibault Le Meur wrote:
>> At Fri, 24 Nov 2006 15:26:46 -0500,
>> Pavel Polischouk wrote:
>>
>>> +3.2 - Patching alsa to use direct pcm device
>>> +--------------------------------------------
>>> +A patch for Jack by Andreas Steinmetz adds support for Big Endian
>>> +devices.
>>> +However it has not been included in the CVS tree.
>>>
>> Is this true? If so, you should submit the patch to upstream...
>>
>
> Oups, my mistake:
> * It is "Patching Jackd to use direct pcm device" and NOT "Patching alsa to
> use direct pcm device"
> * Moreover, this patch has now been adapted and integrated into the Jackd
> main code (I can't remember which version had this patch, but the latest one
> has it for sure)
>
This part of the documentation came from the original
Audiophile-Usb.txt, I didn't modify this part. Looks like it's outdated,
jack 0.102 already has big endian support integrated (sort of - it has
certain problems, like not supporting different endians for playback and
capture, I'm gonna submit the patch for this to Jack team). I can update
this part of documentation too.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-11-27 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 20:26 [PATCH 2/2] M-Audio USB Documentation Pavel Polischouk
2006-11-27 11:17 ` Takashi Iwai
2006-11-27 11:47 ` RE : " Thibault Le Meur
2006-11-27 15:20 ` Pavel Polischouk [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=456B0238.80103@inbox.ru \
--to=pavelvp@inbox.ru \
--cc=alsa-devel@lists.sourceforge.net \
/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