lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 26 Jul 2016 10:06:41 +0200 From: Clemens Ladisch <clemens@...isch.de> To: Ruslan Bilovol <ruslan.bilovol@...il.com> Cc: Felipe Balbi <balbi@...nel.org>, Daniel Mack <zonque@...il.com>, Jassi Brar <jassisinghbrar@...il.com>, "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [RFC PATCH 0/5] USB Audio Gadget refactoring Ruslan Bilovol wrote: > On Fri, Jul 15, 2016 at 10:43 AM, Clemens Ladisch <clemens@...isch.de> wrote: >>>> On Tue, May 24, 2016 at 2:50 AM, Ruslan Bilovol >>>> <ruslan.bilovol@...il.com> wrote: >>>>> it may break current usecase for some people >> >> And what are the benefits that justify breaking the kernel API? > > Main limitation with current f_uac1 design is - it can be used only on systems > with real ALSA card present and can have only exact number of > channels / sampling rate as sink card has. [...] > A real cases when it's required to have UAC1 gadget represented as virtual > sound card on gadget side: [...] Thanks. > Of course disadvantage of new approach for UAC1 gadget is you need to > use some userspace application for routing audio from virtual to real > sound card, like in case of UAC2 gadget. But thanks to existing > applications like alsaloop it's not difficult nowadays. I don't know what the maintainer will say, but you would increase the chances of this change being accepted when you show a concrete example of how to change the userspace configuration from the old to the new driver. (And add it to the documentation.) Regards, Clemens
Powered by blists - more mailing lists