Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Carlo Vallati <carlo.vallati@iet.unipi.it>
Cc: Henning Rogge <hrogge@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-wpan@vger.kernel.org
Subject: Re: 6lowpan with external radio
Date: Thu, 6 Nov 2014 20:34:46 +0100	[thread overview]
Message-ID: <20141106193445.GD2321@omega> (raw)
In-Reply-To: <20141106182403.GA2321@omega>

Hi Carlo,

On Thu, Nov 06, 2014 at 07:24:03PM +0100, Alexander Aring wrote:
> On Thu, Nov 06, 2014 at 06:55:11PM +0100, Carlo Vallati wrote:
> > Hi,
> > you can also take a look at this work in progress of mine [0] in which I'm
> > implementing a driver for the Xbee s1 cards.
> > The implementation is still a work in progress, so it has only the basic TX
> > and RX operations and it includes the latest subsystem changes (at least
> > the version included in the 3.16 kernel).
> > The driver communicates with the Xbee s1 card using a serial protocol to
> > receive/send raw data, while most of the 802.15.4 are implemented in
> > hardware (for this reason its structure follows the fakehard.c driver).
> > 
> 
> well, I removed now any HardMAC functionality because it never had any
> functionality. For example [0].
> 
> This was used by the fakehard driver but there was no real netlink
> interface which used these calls. HardMAC driver is another topic for
> the future.
> 

this will not mean that I don't accept HardMAC drivers. I do now a
rework of this branch which looks very similar like wireless/mac80211
afterwards.

The HardMAC functionality should be look like wireless. This
means a cfg802154 implementation inside driver layer. Also netdev
allocation/registration etc.. is inside driver layer. cfg802154 is just
a callback structure for the netlink 802.15.4 calls.

Really the current mainline HardMAC functionality was in some broken
state which never had any functionality.


I hope you are not too frustrated now. :-)

- Alex

  reply	other threads:[~2014-11-06 19:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 11:14 6lowpan with external radio Henning Rogge
2014-11-06 15:36 ` Marcel Holtmann
2014-11-06 16:33   ` Henning Rogge
2014-11-06 16:54     ` Alexander Aring
2014-11-06 17:00       ` Henning Rogge
2014-11-06 17:08         ` Alexander Aring
2014-11-06 18:09           ` Carlo Vallati
     [not found]           ` <CAP0sMCzn-cRSDi7GoeLPFKH868vdW+DJsC_ak-eZwT+GEbwwiA@mail.gmail.com>
2014-11-06 18:01             ` Henning Rogge
2014-11-06 18:13               ` Carlo Vallati
2014-11-06 18:28                 ` Alexander Aring
2014-11-06 18:24             ` Alexander Aring
2014-11-06 19:34               ` Alexander Aring [this message]
2014-11-07 13:22                 ` Carlo Vallati

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=20141106193445.GD2321@omega \
    --to=alex.aring@gmail.com \
    --cc=carlo.vallati@iet.unipi.it \
    --cc=hrogge@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=marcel@holtmann.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