[alsa-devel] [PATCH] Provide card number / PID via sequencer client info

Martin Koegler martin.koegler at chello.at
Mon Feb 15 22:44:54 CET 2016


On Mon, Feb 15, 2016 at 08:08:12PM +0100, Takashi Iwai wrote:
> On Mon, 15 Feb 2016 19:32:43 +0100,
> Martin Koegler wrote:
> > 
> > On Mon, Feb 15, 2016 at 11:30:15AM +0100, Takashi Iwai wrote:
> > > The idea looks good.  One remaining question is whether only providing
> > > the card number or pid is sufficient for all cases.
> > 
> > I only care about the kernel client. 
> 
> Well, the question is whether only card number is enough.  What if
> cards provide multiple rawmidi devices?

Aren't they currently ports?
seq_midi.c creates just one sequencer device per card number.

Regards,
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Show-sequencer-sound-card-numer-PID-via-aconnect.patch
Type: text/x-diff
Size: 1688 bytes
Desc: not available
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20160215/434e009a/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Provide-sequencer-sound-card-number-PID-via-alsa-lib.patch
Type: text/x-diff
Size: 5120 bytes
Desc: not available
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20160215/434e009a/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Provide-card-number-PID-via-sequencer-client-info.patch
Type: text/x-diff
Size: 3916 bytes
Desc: not available
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20160215/434e009a/attachment-0002.bin>


More information about the Alsa-devel mailing list