From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Christopher Friedt <chrisfriedt@gmail.com>
Cc: Koen Zandberg <koen@bergzand.net>,
linux-wpan@vger.kernel.org,
Andrei Emeltchenko <andrei.emeltchenko@intel.com>,
erik@statropy.com
Subject: Re: wpanusb?
Date: Fri, 24 Jul 2020 15:26:59 +0200 [thread overview]
Message-ID: <58d03eed-00e3-7c96-3464-4b30719ca90c@datenfreihafen.org> (raw)
In-Reply-To: <CAF4BF-TdLpg6hCc8iiR40tGmV9C5EPDF6c6Qr5m5CfDWOVJUMA@mail.gmail.com>
Hello
On 21.07.20 19:11, Christopher Friedt wrote:
>
> Does Linux already support the 900 MHz phy and IEEE bits?
>
> If possible, we're hoping to be able to use it for the 2.4 GHz band and
> the 900 MHz band.
As follow up from what I wrote on the 900 MHz stuff before here is a
link where we are adding sub GHz support to the atusb driver
https://git.kernel.org/pub/scm/linux/kernel/git/sschmidt/wpan-next.git/commit/?id=d5dd29e4dafef4baad7bf529ad73cafeb13e1aa8
regards
Stefan Schmidt
next prev parent reply other threads:[~2020-07-24 13:27 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 ` 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 ` Stefan Schmidt [this message]
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=58d03eed-00e3-7c96-3464-4b30719ca90c@datenfreihafen.org \
--to=stefan@datenfreihafen.org \
--cc=andrei.emeltchenko@intel.com \
--cc=chrisfriedt@gmail.com \
--cc=erik@statropy.com \
--cc=koen@bergzand.net \
--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;
as well as URLs for NNTP newsgroup(s).