On Sat, Aug 22, 2020 at 11:33 AM Alper Nebi Yasak <alpernebiyasak@xxxxxxxxx> wrote: > > On 22/08/2020 20:07, Curtis Malainey wrote: > > Typically we use JackDev over JackControl, and this would add similar > > support to what you added but within the context of using an input > > device instead of an ALSA jack. > > Oh, I forgot JackDev was actually an upstream thing and thought it was > ChromeOS-specific. In that case I can't really object to JackSwitch > either. > > Still, problems with jack detection are common for people who want to > use ordinary Linux distributions on ChromeOS devices and from my point > of view it's "Google makes their things run on JackControl" vs "Someone > makes PulseAudio etc. support JackDev+JackSwitch" to get things working > out of the box in the future. I was trying to propose the former, but I > don't know the merits of either approach, so can't say much other than > that. I understand that, which is why I am trying to pull our configs into alignment. Currently we support JackControl or JackDev (I believe as of january.) And I am gradually pulling the rest of the configs into alignment. I think given the fact that JackDev is an upstream construct we should make it match feature parity with JackControl. > > Regardless, I appreciate your work on reconciling ChromeOS configs with > upstream configs. Thanks :)
