On Tue, 08 Mar 2016 10:00:37 +0100, Clemens Ladisch wrote:
Takashi Iwai wrote:
Martin Koegler wrote:
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 :)
Acked-by: Clemens Ladisch clemens@ladisch.de
OK, I merged it now.
But the patch had a few minor coding-style issues. I fixed them up. Martin, at the next time, please run scripts/checkpatch.pl before submission.
thanks,
Takashi