From: Christopher Friedt <chrisfriedt@gmail.com>
To: Koen Zandberg <koen@bergzand.net>
Cc: Stefan Schmidt <stefan@datenfreihafen.org>, linux-wpan@vger.kernel.org
Subject: Re: wpanusb?
Date: Sun, 31 May 2020 12:13:16 -0400 [thread overview]
Message-ID: <CAF4BF-Re1CoR8abM=hvKN=TojDoLL_PRAJTvjWzB-Ak8tKTvRg@mail.gmail.com> (raw)
In-Reply-To: <61ffa93d-f8cf-b059-358c-84a6e04b96ac@bergzand.net>
Hi Koen,
On Sat, May 30, 2020 at 2:10 PM Koen Zandberg <koen@bergzand.net> wrote:
>
> Hello all,
>
> Long term RIOT maintainer here.
>
> 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.
That's great news!
Also, I heard from the original wpanusb author and he said he'll put
submitting a patch any day now.
Cheers,
C
next prev parent reply other threads:[~2020-05-31 16:13 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 ` wpanusb? Koen Zandberg
2020-05-31 16:13 ` Christopher Friedt [this message]
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-Re1CoR8abM=hvKN=TojDoLL_PRAJTvjWzB-Ak8tKTvRg@mail.gmail.com' \
--to=chrisfriedt@gmail.com \
--cc=koen@bergzand.net \
--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.