alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: alsa-devel@alsa-project.org
Subject: Re: alsa jack plugin
Date: Thu, 11 Nov 2010 23:11:57 +0100	[thread overview]
Message-ID: <1289513517.16615.10.camel@mattotaupa> (raw)
In-Reply-To: <20101110101846.GD4238@siel.b>


[-- Attachment #1.1: Type: text/plain, Size: 1728 bytes --]

Am Mittwoch, den 10.11.2010, 11:18 +0100 schrieb torbenh:
> On Mon, Nov 08, 2010 at 10:26:47AM +0100, torbenh wrote:
> > 
> > the alsa jack plugin has quite some problems:
> > a) does not work correctly with mplayers alsa output. (and quite a few
> >    others)
> > b) it includes the pid in its clientname.
> > c) it requires port connections.
> > d) jack client is deactivated when alsa stream is not active.
> > e) no way to set the jack clientname
> > 
> > the master branch on git://hochstrom.endofinternet.org/alsa-plugins
> > carries fixes for a, b and e.
> > 
> > c and d have their own branches.
> > 
> > i have seen a few problems with making the write end of the fd
> > non-blocking. would it be possible to use eventfd(2) for this ?
> 
> did anybody see this mail ?
> do you prefer patches in a different form ?

Please follow `Documentation/SubmittingPatches` [1]. I was told to
always CC the maintainers (item 7). You should also tag your message in
the subject with `[PATCH]` (item 11). Item 16 talks about sending a pull
request.

> looks like you want git send-email

I guess this way people will be able to review your patches more easily
and give feedback.

> or is there another ML for the plugins ?

I do not think so.


Thank you for your contribution. I hope the developers will be able to
take a look. I also believe that Takashi is on vacation right now and is
going to be for another week [2].


Thanks,

Paul


[1] http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=blob;f=Documentation/SubmittingPatches;h=689e2371095cc5dfea9927120009341f369159aa;hb=HEAD
[2] http://mailman.alsa-project.org/pipermail/alsa-devel/2010-November/033366.html

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2010-11-11 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08  9:26 alsa jack plugin torbenh
2010-11-10 10:18 ` torbenh
2010-11-11 22:11   ` Paul Menzel [this message]
2010-11-17  7:16     ` Raymond Yau
2010-11-19 13:15       ` torbenh
2010-11-19 13:37         ` torbenh

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=1289513517.16615.10.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --cc=alsa-devel@alsa-project.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).