Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
Hi! I no longer have a working pi3 around, but last time I checked, all the way through the 5.X series... it was ok, and this was at least until 5.8.X or 5.9.X. So, I'd say this is solved, at least for the Pi 3 b, which was the one I used to have around and which was presenting this on 4.19. I believe you can close this. Regards. El dom, 2 may 2021 a las 9:32, Salvatore Bonaccorso () escribió: > > 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 > -- Manty/BestiaTester -> http://manty.net
Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
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
Processed: Re: Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
Processing control commands: > tags -1 + moreinfo Bug #856505 [src:linux] No driver for BCM2835 audio output Added tag(s) moreinfo. -- 856505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
> > >> 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? Regards. -- Manty/BestiaTester -> http://manty.net
Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
On Wed, Dec 19, 2018 at 12:05:27PM +0100, Stefan Wahren wrote: > Am 19.12.18 um 09:15 schrieb Uwe Kleine-König: > > Hello, > > > > On Tue, Dec 18, 2018 at 11:49:33PM +0100, Santiago Garcia Mantinan wrote: > >>> I just added the commit from v4.20-rc7 that fixes this problem to the > >>> Linux package git repository. It will be part of the next upload of > >>> v4.19.x to unstable. > >> And could we have the patch I sent on #856505 to enable sound on this > >> machines applied as well? > >> > >> I sent this to the lkml as you sugested but with little luck, it looks like > >> nobody cares. > > 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 didn't suggest to send to lkml, did I? You seem to have skipped > > reading section 5 of the link I provided. You should address the mail to > > the broadcom maintainers (see MAINTAINER file) and carbon copy > > linux-arm-ker...@lists.infradead.org (which for reasons unknown to me > > isn't listed in the broadcom entry). > > scripts/get_maintainers.pl will be your friend It doesn't list lakml for the dt file under discussion though[1]. That's why I added here explicitly. Best regards Uwe [1] scripts/get_maintainer.pl -f arch/arm/boot/dts/bcm283x.dtsi -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ |
Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
Hi Santiago, Am 19.12.18 um 09:15 schrieb Uwe Kleine-König: > Hello, > > On Tue, Dec 18, 2018 at 11:49:33PM +0100, Santiago Garcia Mantinan wrote: >>> I just added the commit from v4.20-rc7 that fixes this problem to the >>> Linux package git repository. It will be part of the next upload of >>> v4.19.x to unstable. >> And could we have the patch I sent on #856505 to enable sound on this >> machines applied as well? >> >> I sent this to the lkml as you sugested but with little luck, it looks like >> nobody cares. 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 didn't suggest to send to lkml, did I? You seem to have skipped > reading section 5 of the link I provided. You should address the mail to > the broadcom maintainers (see MAINTAINER file) and carbon copy > linux-arm-ker...@lists.infradead.org (which for reasons unknown to me > isn't listed in the broadcom entry). scripts/get_maintainers.pl will be your friend Regards Stefan > > Best regards > Uwe >
Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
Hello, On Tue, Dec 18, 2018 at 11:49:33PM +0100, Santiago Garcia Mantinan wrote: > > I just added the commit from v4.20-rc7 that fixes this problem to the > > Linux package git repository. It will be part of the next upload of > > v4.19.x to unstable. > > And could we have the patch I sent on #856505 to enable sound on this > machines applied as well? > > I sent this to the lkml as you sugested but with little luck, it looks like > nobody cares. I didn't suggest to send to lkml, did I? You seem to have skipped reading section 5 of the link I provided. You should address the mail to the broadcom maintainers (see MAINTAINER file) and carbon copy linux-arm-ker...@lists.infradead.org (which for reasons unknown to me isn't listed in the broadcom entry). Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ |
Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
> I just added the commit from v4.20-rc7 that fixes this problem to the > Linux package git repository. It will be part of the next upload of > v4.19.x to unstable. And could we have the patch I sent on #856505 to enable sound on this machines applied as well? I sent this to the lkml as you sugested but with little luck, it looks like nobody cares. For me it would be good to recover not only the wifi but also the audio. Regards... -- Manty/BestiaTester -> http://manty.net
