Control: tags -1 + moreinfo On Mon, Dec 31, 2018 at 12:15:35AM +0100, Santiago Garcia Mantinan wrote: > > > >> And could we have the patch I sent on #856505 to enable sound on this > > > >> machines applied as well? > > > > > > i assume you are talking about: > > > > > > arm: bcm2835-audio: Document the device tree node to enable > > > bcm2835-audio driver > > > > > > This patch will not be accepted. For a explanation please refer to: > > > > > > https://lkml.org/lkml/2018/10/16/1615 > > > > > > The proper solution is called: > > > > > > staging: bcm2835-audio: Drop DT dependency > > > > > > and is in linux-next since a week. > > I've been playing with those patches for a while on 4.19, but those patches > won't work on their own, they depend on some other stuff that has been > commited as well. All that would mean a lot of changes. > > So, it seems that 4.21 will have a solution for this through a lot of > changes and updates on the drivers, ... > > But, if we are going to go with 4.19 I believe that the simple change I was > proposing which works as expected is going to give us audio on the pi and > only affects the pi, is a clean solution that would solve the problem. > > I don't see the problem on applying this patch on Debian while upstream > evolves the drivers even more on 4.21 and next versions, all we do is enable > what is available on 4.19 like it was coded. > > Any chance for this to happen?
What is the status of this bug? has the issue been fixed upstream? Does it happen still with a recent kernel from unstable or buster-backports? Regards, Salvatore
