From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <aahringo@redhat.com>
Cc: Stefan Schmidt <stefan@datenfreihafen.org>,
werner@almesberger.net, Alexander Aring <alex.aring@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-wpan@vger.kernel.org
Subject: Re: [PATCH atusb/fw v2 2/3] atusb: fw: Update toolchain instructions
Date: Fri, 21 Oct 2022 15:33:51 +0200 [thread overview]
Message-ID: <20221021153351.1d30f620@xps-13> (raw)
In-Reply-To: <CAK-6q+g6mDWh2xNmMUviqiiDwBs1q835TrOU9wZ-CF7=rOA+Tw@mail.gmail.com>
Hi Alexander,
aahringo@redhat.com wrote on Fri, 21 Oct 2022 08:13:52 -0400:
> Hi,
>
> On Fri, Oct 21, 2022 at 2:53 AM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> ...
> > I read a little bit more about LQI during this test phase and indeed,
> > "weak" seems appropriate :-)
> >
>
> * "weak" defined.
>
> > > I heard successful reports also using aluminium foil around transceivers...
> >
> > Indeed I've heard it could work, I'll keep it in mind!
> >
>
> be careful with shortcutting something there, for atusb I recommend [0].
>
> - Alex
>
> [0] https://www.thingiverse.com/thing:2815832
Excellent!
Thanks,
Miquèl
next prev parent reply other threads:[~2022-10-21 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 8:21 [PATCH atusb/fw v2 1/3] Add .gitignore Miquel Raynal
2022-09-06 8:21 ` [PATCH atusb/fw v2 2/3] atusb: fw: Update toolchain instructions Miquel Raynal
2022-10-12 17:54 ` Stefan Schmidt
2022-10-15 8:58 ` Miquel Raynal
2022-10-16 1:02 ` Alexander Aring
2022-10-19 19:46 ` Miquel Raynal
2022-10-20 14:17 ` Miquel Raynal
2022-10-20 23:32 ` Alexander Aring
2022-10-21 6:53 ` Miquel Raynal
2022-10-21 12:13 ` Alexander Aring
2022-10-21 13:33 ` Miquel Raynal [this message]
2022-09-06 8:21 ` [PATCH atusb/fw v2 3/3] atusb: fw: Provide TRAC status Miquel Raynal
2022-10-12 17:57 ` 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=20221021153351.1d30f620@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=aahringo@redhat.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=werner@almesberger.net \
/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