Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>
Cc: Maciej Wasilak <wasilak@gmail.com>,
	"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: hardware recommendation
Date: Tue, 7 Apr 2015 20:59:20 +0200	[thread overview]
Message-ID: <20150407185917.GF16415@omega> (raw)
In-Reply-To: <978F3708-BC58-46E5-AED3-3C4CE1C4BBD3@cisco.com>

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@gmail.com> 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.



Or do you mean mainline networking support? This doesn't work on my side, too.

- Alex

[0] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/tree/arch/arm/configs/bcm2835_defconfig
[1] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/tree/arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
[2] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/tree/arch/arm/boot/dts/bcm2835-rpi-b.dts

  reply	other threads:[~2015-04-07 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 15:28 hardware recommendation Ralph Droms (rdroms)
2015-03-23  7:58 ` Alexander Aring
2015-03-26  4:41   ` Ralph Droms (rdroms)
     [not found]     ` <CAFUtXGzGeMmbSNtbP2xdjr6uitzFwPZCb3Yo-GV2+2gV3uz6+w@mail.gmail.com>
2015-03-26  9:06       ` Alexander Aring
2015-04-07 18:12       ` Ralph Droms (rdroms)
2015-04-07 18:59         ` Alexander Aring [this message]
2015-04-07 19:17           ` Guido Günther
     [not found]         ` <CAFUtXGzHpvDcCErKfyGTvGYri-PsmToNUE7rvoniLmqmdZ8q6w@mail.gmail.com>
2015-04-07 20:12           ` Alexander Aring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150407185917.GF16415@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=rdroms@cisco.com \
    --cc=wasilak@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox