All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Zandberg <koen@bergzand.net>
To: Christopher Friedt <chrisfriedt@gmail.com>,
	Stefan Schmidt <stefan@datenfreihafen.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: wpanusb?
Date: Sat, 30 May 2020 20:10:26 +0200	[thread overview]
Message-ID: <61ffa93d-f8cf-b059-358c-84a6e04b96ac@bergzand.net> (raw)
In-Reply-To: <CAF4BF-SipApoY=7CY8fWs8cSi8rKZaYMxOZHAqoKv=poAgVm=Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2075 bytes --]

Hello all,

Long term RIOT maintainer here.

On 30-05-2020 17:08, Christopher Friedt wrote:
> On Sat, May 30, 2020 at 7:33 AM Stefan Schmidt
> <stefan@datenfreihafen.org> wrote:
>> On 29.05.20 21:33, Christopher Friedt wrote:
>>> 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.
Most of our developers have of-the-shelve development boards such as the
nrf52840dk and the samr21-xplained pro. For us a generic firmware +
Linux kernel driver would be a very welcome addition to the tool set.
>>>> 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'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.

I'm willing to work on this for a RIOT implementation, assuming there is
some documentation available on the USB protocol side :)
I think I should be able to get a relative generic firmware application
able to run on any of our hardware boards as long as they have a radio
and a USB interface.

Koen



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-05-30 18:18 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   ` wpanusb? Christopher Friedt
2020-05-30 11:33     ` wpanusb? Stefan Schmidt
2020-05-30 15:08       ` wpanusb? Christopher Friedt
2020-05-30 18:10         ` Koen Zandberg [this message]
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=61ffa93d-f8cf-b059-358c-84a6e04b96ac@bergzand.net \
    --to=koen@bergzand.net \
    --cc=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.