From: Alexander Aring <alex.aring@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Varka Bhadram <varkabhadram@gmail.com>,
linux-wpan@vger.kernel.org,
unstrung-hackers <unstrung-hackers@lists.sandelman.ca>
Subject: Re: testing and building for RPI
Date: Mon, 27 Jul 2015 09:39:29 +0200 [thread overview]
Message-ID: <20150727073925.GA1187@omega> (raw)
In-Reply-To: <6138.1437963289@sandelman.ca>
Hi Michael,
On Sun, Jul 26, 2015 at 10:14:49PM -0400, Michael Richardson wrote:
>
> Michael Richardson <mcr@sandelman.ca> wrote:
> >> Please see the blog: https://honk.sigxcpu.org/piki/hw/rpi6lowpan/
>
> > I have some edits for this; mostly unfortunate typos or copy/pastes.
> > I did get it working; my major stumbling block had to do with u-boot
> > apparently not really sending out multiple DHCPs messages.
>
> > The first goes out, and if the network is truly ready, it works.
> > Why wouldn't it be ready? Cisco switches with STP enabled... plugging in a
> > trusty 8-port 100Mb/s stupid switch solved the problem, but cross-over cable to my
> > laptop showed me that it was really only sending out a single DHCP request,
> > not 8. Once I put the "boot.scr" in place, it seems to boot very reliably,
> > but I haven't removed the 100Mb/s switch yet.
>
> > The suggested "agx" tree's defconfig didn't seem to enable the correct set of
> > kernel CONFIG options for the AT86*, etc. I'll post my whole recipe when I'm
> > back from the cottage. You need to enable the IEEE802154, to then see
> > MAC802154 (and enable it) options before you'll see the AT86 drivers
> > available if you are using menuconfig.
>
> After doing:
> make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcm2835_defconfig
>
> I had to enable:
> CONFIG_6LOWPAN=y
> CONFIG_6LOWPAN_NHC=y
> CONFIG_6LOWPAN_NHC_DEST=y
> CONFIG_6LOWPAN_NHC_FRAGMENT=y
> CONFIG_6LOWPAN_NHC_HOP=y
> CONFIG_6LOWPAN_NHC_IPV6=y
> CONFIG_6LOWPAN_NHC_MOBILITY=y
> CONFIG_6LOWPAN_NHC_ROUTING=y
> CONFIG_6LOWPAN_NHC_UDP=y
> CONFIG_IEEE802154=y
> CONFIG_IEEE802154_SOCKET=y
> CONFIG_IEEE802154_6LOWPAN=y
> CONFIG_MAC802154=y
>
> CONFIG_IEEE802154_FAKELB=y
> CONFIG_IEEE802154_AT86RF230=y
> CONFIG_IEEE802154_MRF24J40=y
> CONFIG_IEEE802154_CC2520=y
>
> and then I had a kernel that saw my at86 device. (I'm sure that the CC2520
> and MRF24J40 enable was gratuitous).
>
congratulation. :-)
> I haven't yet interoperated with contiki; just ran out of time.
>
Okay, I see also you use a builtin CONFIG_IEEE802154_FAKELB, this module
generates two virtual phys which can "transmit <-> receive" some data
between them - if the page/channel setting are the same. This module
will register two phys by default.
It's just a note, that you might have 3 phys registered.
- Alex
next prev parent reply other threads:[~2015-07-27 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 19:41 testing and building for RPI Michael Richardson
2015-05-12 3:52 ` Varka Bhadram
2015-05-12 8:28 ` Christoffer Holmstedt
2015-07-21 16:37 ` Michael Richardson
2015-07-30 14:37 ` Stefan Schmidt
2015-07-25 18:27 ` Michael Richardson
2015-07-27 2:14 ` Michael Richardson
2015-07-27 7:39 ` Alexander Aring [this message]
2015-07-30 17:39 ` Guido Günther
2015-07-31 13:33 ` Michael Richardson
2016-03-12 21:38 ` Guido Günther
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=20150727073925.GA1187@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=mcr@sandelman.ca \
--cc=unstrung-hackers@lists.sandelman.ca \
--cc=varkabhadram@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