On Thu, Mar 03, 2016 at 10:43:32AM +0100, Takashi Iwai wrote:
From: Martin Koegler martin.koegler@chello.at
rawmidi devices expose the card number via IOCTLs, which allows to find the corresponding device in sysfs.
The sequencer provides no identifing data. Chromium works around this issue by scanning rawmidi as well as sequencer devices and matching them by using assumtions, how the kernel register sequencer devices.
This changes adds support for exposing the card number for kernel clients as well as the PID for user client.
The minor of the API version is changed to distinguish between the zero initialised reserved field and card number 0.
Signed-off-by: Martin Koegler martin.koegler@chello.at
This ABI change itself looks simple enough, so I have no big problem to merge if you can convince other people with it :)
Clemens?
The current solution has been proposed by him: http://mailman.alsa-project.org/pipermail/alsa-devel/2016-February/104175.ht...
Regards, Martin