On 10/05/20 at 14:22 +0200, Bjørn Mork wrote:
> Bjørn Mork writes:
>
> > Note that I found that I had to remove the cma=xx option raspi-firmware
> > wants to put into the cmdline.txt. This messed up mailbox access to the
> > firmware, and took several drivers/devices with it in the fall. Don't
Bjørn Mork writes:
> Note that I found that I had to remove the cma=xx option raspi-firmware
> wants to put into the cmdline.txt. This messed up mailbox access to the
> firmware, and took several drivers/devices with it in the fall. Don't
> think the SD card was one one them. But still worth
Lucas Nussbaum writes:
> I am trying to boot a RPI4 with the 5.6 kernel from unstable, but it
> fails to boot (while it worked with 5.5 from unstable).
>
> What I'm seeing with 5.5, but not with 5.6, is:
> [4.500333] mmc1: SDHCI controller on fe34.emmc2 [fe34.emmc2]
> using ADMA
> [
Lucas Nussbaum writes:
> On 09/05/20 at 20:44 +0200, Bjørn Mork wrote:
>> Please enable CONFIG_PCIE_BRCMSTB on arm64.
>>
>> The Raspberry Pi 4 has a VL805 xhci controller connected to the
>> PCIe bus on the SoC. All USB ports are connected to this controller.
>> CONFIG_PCIE_BRCMSTB is therefore
Hi Bjørn,
On 09/05/20 at 20:44 +0200, Bjørn Mork wrote:
> Please enable CONFIG_PCIE_BRCMSTB on arm64.
>
> The Raspberry Pi 4 has a VL805 xhci controller connected to the
> PCIe bus on the SoC. All USB ports are connected to this controller.
> CONFIG_PCIE_BRCMSTB is therefore necessary for USB
Package: src:linux
Version: 5.6.7-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Maintainer,
Please enable CONFIG_PCIE_BRCMSTB on arm64.
The Raspberry Pi 4 has a VL805 xhci controller connected to the
PCIe bus on the SoC. All USB ports are connected to this
6 matches
Mail list logo
