Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Baptiste Clenet <bapclenet@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: error: nl802154 not found
Date: Wed, 3 Jun 2015 16:46:59 +0200	[thread overview]
Message-ID: <20150603144657.GB744@omega> (raw)
In-Reply-To: <CAPpUg6Oj5TbS9qwdor-uymsU5bzhUMxJXk=RBd+1UmPXwHVK=Q@mail.gmail.com>

On Wed, Jun 03, 2015 at 03:08:44PM +0200, Baptiste Clenet wrote:
> Hi,
> 
> I finally managed to set up the at86rf212B with some edits in spi
> driver and pinctrl driver.
> 
> Anyway, I've got an at86rf212B set up now and I wanted to use iwpan tools.
> As soon as I use "iwpan list", I get an error: "nl802154 not found"
> 
> 
> The at86rf230 driver seems to register an ieee802154 device without
> errors: ieee802154_register_device(lp->dev);
> 
> What could be the problem?
> 

which kernel version do you use?

- Alex

  reply	other threads:[~2015-06-03 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 13:08 error: nl802154 not found Baptiste Clenet
2015-06-03 14:46 ` Alexander Aring [this message]
2015-06-03 15:08   ` Baptiste Clenet
2015-06-03 15:32     ` 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=20150603144657.GB744@omega \
    --to=alex.aring@gmail.com \
    --cc=bapclenet@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    /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