Return-Path: MIME-Version: 1.0 In-Reply-To: References: <00A3687E-050A-469F-98B0-C42F872EFE1C@holtmann.org> <115EE599-9710-437B-9AA8-C4CD8360EF3F@holtmann.org> <9C9C1616-C9CA-4542-AC9C-0DBC3107BA61@holtmann.org> From: Peter Robinson Date: Fri, 22 Sep 2017 12:32:52 +0100 Message-ID: Subject: Re: Fedora 27 kernel and RPi3 Bluetooth oops To: Loic Poulain Cc: Marcel Holtmann , "bluez mailin list (linux-bluetooth@vger.kernel.org)" Content-Type: text/plain; charset="UTF-8" List-ID: On Fri, Sep 22, 2017 at 10:09 AM, Loic Poulain wrote: > Hi Marcel, Peter, > >> > Hans added a script to automatically btattch some bcm controllers for >> > atom devices, maybe we need to add more IDs for udev, not sure if >> > there's a means of making that generic and upstreamable. Also some of >> > the other distro patches I've seen had a different BT firmware, not >> > sure if Loic needed that or not. >> >> The whole point behind serdev is that you no longer need btattach. The >> UART can be enumerated by the kernel. So that should not be needed and we >> also want to get rid of it for ACPI based systems as well. >> > > Since it works with raspbian I had a try with Fedora 26. > > To make this 'simpler', I bypassed u-boot and just loaded my kernel + my > dtb: > > - added bcm2837-rpi-3-b.dtb and kernel zImage (Linux 4.13 32-bit) (FAT PART) Where did the kernel come from? Is that the Fedora kernel? > - modified config.txt (FAT part): > # Raspberry Pi 3 > [pi3] > kernel=zImage > device_tree=bcm2837-rpi-3-b.dtb > > - added cmdline.txt (FAT part): > dwc_otg.lpm_enable=0 root=/dev/mmcblk0p4 rootfstype=ext4 elevator=deadline > fsck.repair=yes rootwait splash plymouth.ignore-serial-consoles > > - added modules (rootfs ext4 part) > > That works as expected, my hci device is correctly configured and > operational. > Maybe u-boot adds some unexpected overlay or applies incorrect config. It certainly doesn't add overlays by default, it uses the vanilla linux kernel DT