All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Friedt <chrisfriedt@gmail.com>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: wpanusb?
Date: Fri, 29 May 2020 15:33:53 -0400	[thread overview]
Message-ID: <CAF4BF-SNRyXQzUBqx5k014nZou4q7=Gd8=dbUyK7JiDkaEEvFA@mail.gmail.com> (raw)
In-Reply-To: <b009a2a8-64a5-fe66-a53e-5a93135cf1f8@datenfreihafen.org>

Hi Stefan!

On Tue, May 26, 2020 at 3:38 PM Stefan Schmidt
<stefan@datenfreihafen.org> wrote:
> On 25.05.20 14:39, Christopher Friedt wrote:
> > Hi all,
> >
> > Bouncing around a bit, but in Zephyr, there is reference to a
> > "wpanusb" Linux kernel driver here:
> >
> > https://docs.zephyrproject.org/latest/samples/net/wpanusb/README.html
> >
> > This *might* be the driver in question:
> >
> > https://github.com/finikorg/wpanusb
> >
> > Just wondering if anyone has made any attempts to submit that, or
> > would that go directly upstream these days?
>
> I had a chance to talk to the author a while back. Not much activity
> from his side.

I was chatting with him as well on Zephyr Slack and let him know that
there was significant interest in it going upstream. I worry though
that it might not be a high priority for his employer.

Is there a linux-wpan IRC? Would be nice to chat in real-time at some point.

> For me this needs to be designed in a way where we could have bare
> metal, Zephyr, RIOT or Contiki based firmware implementing the interface
> and the driver would just work. The code available is a good start but
> needs more work.

I agree mostly. Of course each RTOS has their own headers, way of
declaring things, etc, but for the most part it could be platform
independent.

> I was, and somehow still am, planning on working on this. But with the
> world turned upside down there was always something else to look at
> before. Its on my list, just not very high. If anyone wants to have a
> stab at this feel free and let me know.

I'll bring it up in the Zephyr Slack. They want to incorporate it into
their "tools" repository, but it really should go into Linux at some
point.

We'll probably end up working on this for BB.O - even just having a
single driver that works for all boards in Zephyr is a pretty large
step.

Lastly, I feel like this is a recurring question, but a number of us
will likely need a bunch of 802.15.4 USB dongle to speak to our 15.4
nodes. I have a couple of ATUSB on my desk, but are there others in
our group that don't have any idea where to get parts, and likely
building one from scratch would be more time than they want to take.

Do you know of an off-the-shelf product that works with existing
drivers upstream?

M.f.G.

Chris

  reply	other threads:[~2020-05-29 19:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 12:39 wpanusb? Christopher Friedt
2020-05-26 19:38 ` wpanusb? Stefan Schmidt
2020-05-29 19:33   ` Christopher Friedt [this message]
2020-05-30 11:33     ` wpanusb? Stefan Schmidt
2020-05-30 15:08       ` wpanusb? Christopher Friedt
2020-05-30 18:10         ` wpanusb? Koen Zandberg
2020-05-31 16:13           ` wpanusb? Christopher Friedt
2020-06-03 18:18             ` wpanusb? Stefan Schmidt
2020-06-05 11:07               ` wpanusb? Koen Zandberg
2020-06-07 12:17                 ` wpanusb? Stefan Schmidt
2020-07-06 14:42                   ` wpanusb? Stefan Schmidt
     [not found]                     ` <CAF4BF-TdLpg6hCc8iiR40tGmV9C5EPDF6c6Qr5m5CfDWOVJUMA@mail.gmail.com>
2020-07-23  8:15                       ` wpanusb? Stefan Schmidt
2020-07-24 13:26                       ` wpanusb? Stefan Schmidt
2020-07-24 13:41                 ` wpanusb? Stefan Schmidt
2020-09-26 12:28                   ` wpanusb? Stefan Schmidt
2020-09-26 12:47                     ` wpanusb? Christopher Friedt
2020-09-27  8:59                       ` wpanusb? Stefan Schmidt
2020-10-15 20:16                         ` wpanusb? Christopher Friedt
2020-11-03 16:47                           ` wpanusb? Stefan Schmidt

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='CAF4BF-SNRyXQzUBqx5k014nZou4q7=Gd8=dbUyK7JiDkaEEvFA@mail.gmail.com' \
    --to=chrisfriedt@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=stefan@datenfreihafen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.