From: Alexander Aring <alex.aring@gmail.com>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH wpan-misc] website: add opentask section in developing
Date: Sun, 12 Apr 2015 12:35:14 +0200 [thread overview]
Message-ID: <20150412103513.GC984@omega> (raw)
In-Reply-To: <20150412103006.GB984@omega>
On Sun, Apr 12, 2015 at 12:30:06PM +0200, Alexander Aring wrote:
> Hi,
>
> On Sat, Apr 11, 2015 at 06:42:15PM +0200, Guido Günther wrote:
> > On Wed, Apr 08, 2015 at 10:31:34AM +0200, Alexander Aring wrote:
> > > This patch adds an open task section in developing. So maybe if somebody
> > > has too much time he/she can pick tasks from it and send patches.
> > >
> > > Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> > > ---
> > > website/index.txt | 23 +++++++++++++++++++++++
> > > 1 file changed, 23 insertions(+)
> > >
> > > diff --git a/website/index.txt b/website/index.txt
> > > index 2f007d5..9cf2ca3 100644
> > > --- a/website/index.txt
> > > +++ b/website/index.txt
> > > @@ -122,6 +122,29 @@ All patches should be send to <linux-wpan@vger.kernel.org> and based on bluetoot
> > > For wpan-tools checkout the https://github.com/linux-wpan/wpan-tools[wpan-tools] repository. Also send patches to <linux-wpan@vger.kernel.org> for it with a "wpan-tools" tag.
> > > The same for https://github.com/linux-wpan/wpan-misc[wpan-misc].
> > >
> > > +Open Tasks
> > > +~~~~~~~~~~
> > > +
> > > +* There is a lot of missing features for enum definition to some string definition in iwpan which can be lookup in 802.1.54 standard. Words say more than numbers...
> > > +** channel/page to frequency
> > > +** cca modes/opts
> > > +** no aret mode for max_frame_retires -1
> > > +** etc
> > > +* Missing features which wireless has and wpan not. Since we based our implementation on wireless we should sync "good patches" from wireless branch.
> > > +** Something like http://www.spinics.net/lists/netdev/msg321088.html[net: nl80211 - pass name_assign_type to rdev_add_virtual_intf()]
> > > +** trace functionality for rdev/driver_ops http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/tree/net/wireless/rdev-ops.h[rdev-ops.h] and
> > > +http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/tree/net/mac80211/driver-ops.h[driver-ops.h]
> >
> > I've started to add some tracing at:
> >
> > https://github.com/agx/linux-wpan-next/commits/features/trace
> >
> > will post the patch here once I've finished the rdev part.
>
> cool! I really like that, thanks.
>
> One thing which I see now: You need to care about the byteorder. Don't
> know if there is some magic in the background which do when you say
> it's a __leFOO type. Otherwise you need to call __leFOO_to_cpu(xxx) before,
> for printouts or equals checks. For equal checks with a static value it's
printouts with hex values should also have some filled zero's before.
Example panid format string should be "0x%04x".
- Alex
prev parent reply other threads:[~2015-04-12 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 8:31 [PATCH wpan-misc] website: add opentask section in developing Alexander Aring
2015-04-09 9:16 ` Guido Günther
2015-04-12 10:21 ` Alexander Aring
2015-04-12 17:33 ` Guido Günther
2015-04-12 21:51 ` Alexander Aring
2015-04-11 16:42 ` Guido Günther
2015-04-12 10:30 ` Alexander Aring
2015-04-12 10:35 ` Alexander Aring [this message]
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=20150412103513.GC984@omega \
--to=alex.aring@gmail.com \
--cc=agx@sigxcpu.org \
--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