All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Friedt <chrisfriedt@gmail.com>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: Koen Zandberg <koen@bergzand.net>,
	linux-wpan@vger.kernel.org,
	Andrei Emeltchenko <andrei.emeltchenko@intel.com>,
	erik@statropy.com
Subject: Re: wpanusb?
Date: Sat, 26 Sep 2020 08:47:09 -0400	[thread overview]
Message-ID: <CAF4BF-TG4wpX8TdEXY=EeTz4HV0b-nceFwKb=VkFBkMjfSLPew@mail.gmail.com> (raw)
In-Reply-To: <71f4ce0f-5614-6410-9c8b-72a87ab7473d@datenfreihafen.org>

On Sat, Sep 26, 2020 at 8:28 AM Stefan Schmidt
<stefan@datenfreihafen.org> wrote:
> On 24.07.20 15:41, Stefan Schmidt wrote:
> > [Added Erik here to be part of the discussion]
> >
> > This mostly goes to Koen and Erik. Please coordinate how you are wanting
> > to work on this. And be pro-active. Waiting for the other one to start
> > will just lead to starving :-)
>
> With silence from both of you on this I would assume neither had time to
> look over this. Correct?

On the contrary, Erik & I are working on it right now (although mostly
from the Zephyr side) ;-)

We expect to have something demonstrable with the cc1352r within a
week or 2, at which point I would very much like to work on
upstreaming wpanusb with the additional features.

In Zephyr, I recently got Sub GHz IEEE 802.15.4g running on the
cc1352r1_launchxl. Did a fairly big overhaul of the 2.4 GHz driver as
well. SubG should be able to run simultaneously to 2.4 GHz, and beyond
that, the driver is written so that BLE will work concurrently at 2.4
GHz (with arbitration).

I might need to send you one more dev board though for testing
purposes, because the cc1352r requires a second chip for USB.
BeagleBoard.org is currently preparing for manufacturing of the
BeagleConnect which includes the cc1352 and the USB chip The official
release date is not announced yet.

I have not touched MLME yet unfortunately due to contractual obligations.

Also, somewhat annoying, but a shoddy USB hub damaged my ATUSB :( I
ordered 2 more, so hopefully they get to me shortly!

C

  reply	other threads:[~2020-09-26 12:47 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                       ` wpanusb? Stefan Schmidt
2020-07-24 13:41                 ` wpanusb? Stefan Schmidt
2020-09-26 12:28                   ` wpanusb? Stefan Schmidt
2020-09-26 12:47                     ` Christopher Friedt [this message]
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-TG4wpX8TdEXY=EeTz4HV0b-nceFwKb=VkFBkMjfSLPew@mail.gmail.com' \
    --to=chrisfriedt@gmail.com \
    --cc=andrei.emeltchenko@intel.com \
    --cc=erik@statropy.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.