Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

Hi Stefan > So after fixing the polarity of the wifi-reset everything works as > expected. > > - reset-gpios = < 1 GPIO_ACTIVE_HIGH>; > + reset-gpios = < 1 GPIO_ACTIVE_LOW>; > > I think this should be acceptable as a stable fix for 4.19 LTS. > Great! I applied the same change to

Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

Hi Stefan > i want to play safe. Could you please check the Rev of your 3 B board? > You can find it on the upside of the PCB below the GPIO pin header (e.g. i have Rev 1.2). Mine is also a "Raspberry Pi 3 Model B V1.2". > Could you please provide a complete dmesg in case wlan0 is absent? Here

Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

Hi Stefan > Which RPi 3 variant do you use (B or B+)? Today I have tested on the Raspberry Pi 3 B with arm64. I was able to reproduce it also with kernel 4.19.5. wlan0 remains absent with this newer kernel version. Based on 4.19.5 I reverted commit b1b8f45b3130dbd8704e5ea0d82b49b1d929498e and

Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

Hi Gunnar I must say, I have not been able to find WiFi (not even a "firmware > required" message). Could you help me find it, so it makes its way into > raspi3-image-spec ? Thanks - > I'm closing this MR. > I have also struggled with WiFi. Could the

Bug#884601: "console=ttyAMA0,115200" --> "console=tty0"

Hi Michael > I just uploaded a new raspi3-firmware package which uses ttyS1 on Linux > ≥ 4.14, which is the new device name for the UART on the pin header: > https://anonscm.debian.org/cgit/pkg-raspi/raspi3-firmware.git/commit/?id= > 4da2e6b1576f0a7513bffe7f95882693fdadd7ae Many thanks - this

Bug#884601: "console=ttyAMA0,115200" --> "console=tty0"

Hi I just faced a similar issue with the arm64 kernel (linux-image-4.14.0-0.bpo.2-arm64). It booted fine with the 4.13 based kernel but it failed after the upgrade to the above mentioned kernel. Since I wanted to debug the stuff I took a closer look at the cmdline.txt file: There I found the

Bug#882053: Additional investigations

Dear maintainers I have just taken a look at https://anonscm.debian.org/cgit/kernel/linux.git/: CONFIG_CMA will be switched to yes as soon as commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 gets released on the respective branches. For armhf CONFIG_CMA=y is anyway set since a longer time ago.

Bug#882053: linux-image-4.13.0-0.bpo.1-arm64: feature request: enable contiguous memory allocator (CMA) for arm64 (CONFIG_CMA=y)

Package: src:linux Version: 4.13.4-2~bpo9+1 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? My goal is to generate a pure Debian arm64 image for the Raspberry Pi 3. * What