[alsa-devel] emi62 (may be slightly off-topic)
xiphmont at gmail.com
Thu Dec 12 08:32:13 CET 2013
> Monty, would you submit the emi driver patch to upstream?
It's been a few years since I've submitted a patch. Last I tried,
upstream seriously frowned on any sort of 'I wrote a whole new driver'
type patches. But I'm happy to try if you think it would go through.
> We can keep
> the old EMI26 and EMI62 at first but make them conflicting with EMI
> driver via Kconfig. The external firmware files are maintained in
> linux-firmware tree nowadays. Once all things get merged, the old
> emi26/62 can be faded away.
Sure, that sounds perfectly sensible.
> Looking through the tarball and codes, my only concern is the license
> of the new firmware files...
Yes, that's what has always been problematic in the past. I see
there's at least a patch now to restore it to the state it was in in
early 2.6 when it worked but was just outdated.
That said, I don't want to go through this yet again where one problem
gets fixed, everyone gets bogged down in arguing over the rest, and
that's the state things stay in. That's where eMagic support has been
since roughly 2008. If we're not going to fix it all, and fix it for
real, I'd honestly rather not bother. No more partial solutions when
the complete solution is already right here.
So before submitting a patch, I'd like to secure agreement over the
firmware update from whomever needs to commit. Who would that be? If
we can agree on that, I'm in for the rest.
I mean, it's not like we have explicit permission to distribute the
firmware we're shipping now. :-P
More information about the Alsa-devel