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: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: hardware recommendation
Date: Mon, 23 Mar 2015 08:58:21 +0100	[thread overview]
Message-ID: <20150323075818.GA4069@omega> (raw)
In-Reply-To: <8575BDE3-5617-49A9-AF9C-D0C9359E074E@cisco.com>

Hi Ralph,

welcome back.

On Sun, Mar 22, 2015 at 03:28:36PM +0000, Ralph Droms (rdroms) wrote:
> What hardware - radio board, interface, Linux platform - are recommended for the 802.15.4 stack in the bluetooth-next kernel?
> 

See [0].

Radio board:

  - I would advice a 2.4 Ghz at86rf231 or at86rf233 [1].
     Supports async xmit handling and has the most supported hardware
     flags. Driver is at86rf230.

Interface:
  - What you mean with interface? Bus Interface? -> SPI. Or netlink
    interface? -> nl802154 with wpan-tools. Don't understand the
    question.

Linux platform:
  - I think you mean some architecture -> ARM. Then the platform, some
    board: The transceiver at [1] was made for RPi which works well on
    my side. But the RPi has a lack of mainline support. You have no
    USB, this means you have also no ethernet. If you don't need
    ethernet, then I would use a simple RPi. If you need ethernet I
    would advice to make some adapter board to add the [1] on a
    beaglebone [2], which have a good mainline support. This require
    some hardware hacking skills.

    Note: for RPi I also support you have no other support e.g. HDMI
    output or something else. SPI with RPi works mainline perfectly.

> - Ralph
> 
> BTW, is this list archived?  Where?
>

Over google I detected that spinics archive this mailinglist [3] (but
doesn't include the early days).

- Alex

[0] http://wpan.cakelab.org/
[1] http://openlabs.co/store/Raspberry-Pi-802.15.4-radio
[2] http://beagleboard.org/
[3] http://www.spinics.net/lists/linux-wpan/


  reply	other threads:[~2015-03-23  7:58 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 [this message]
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
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=20150323075818.GA4069@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=rdroms@cisco.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