Hi, On Tue, Apr 07, 2015 at 08:59:20PM +0200, Alexander Aring wrote: > Hi Ralph, > > On Tue, Apr 07, 2015 at 06:12:49PM +0000, Ralph Droms (rdroms) wrote: > > > > > On Mar 26, 2015, at 2:44 AM 3/26/15, Maciej Wasilak <wasilak@xxxxxxxxx> wrote: > > > > > > Dear Ralph, > > > > > > I confirm it's possible to use USB and Ethernet on RaspberryPi with bluetooth-next. You have to enable kernel options: > > > > > > CONFIG_USB_DWC2_HOST > > > CONFIG_USB_DWC2_PLATFORM > > > > Are there any other changes to a clone of bluetooth-next I need to make to build a Raspberry Pi kernel? I tried naively building bluetooth-next with an updated, known good .config but the resulting kernel doesn't seem to be operational. > > > > A lastest "known to work config" can be found at [0]. > > But you need to boot with device tree, then it depends on plus model or > not, see [1] or [2]. You need to tell your bootloader where the device > tree file is found. Also the device tree file is usually a binary > format, you need to convert the dts file with dtc to some dtb file. I recently went through this using device tree. Had to minimally patch device tree due to using "Raspberry Pi 802.15.4 radio" from Openlabs and it worked fine after tweaking defconfig a tiny bit to enable 6LoWPAN. Notes are here: https://honk.sigxcpu.org/piki/hw/rpi6lowpan/ The current tree I'm using is at: https://github.com/agx/linux-wpan-next/tree/rpi-6lowpan It's basically bluetooth-next as of baf880a96859cca79208122e555e7efeabd16e4d + the device tree and defconfig changes. Ethernet works fine here too. Cheers, -- Guido -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html