From: Zac Dydek <zac.dydek@alum.mit.edu>
To: linux-wireless@vger.kernel.org
Subject: Looking for a wireless contractor/consultant
Date: Thu, 30 Jul 2020 10:31:12 -0400 [thread overview]
Message-ID: <CALUoyiA=c_wEFUPbXW=PT4EVnE6SH2vT=a2nkmL2hFa0RUJegA@mail.gmail.com> (raw)
Hi all--
My company builds autonomous mobile robots (AMRs) that run Linux and
connect wirelessly to a facility network using an Atheros wireless
card and the atk9k driver. We've also used an Intel card and iwlwifi
in the past. We are looking to improve the performance of our
wireless connectivity and want to bring in someone with deep
experience in this area to review our approach and provide guidance on
where improvements might be made
Ideally, this contractor would have not only deep understanding of
Linux wireless firmware setup and configuration, but also hardware
design (antenna selection and placement, etc.). Experience with
mobile device wireless, especially roaming across access points would
be useful as well.
If there's anyone on this mailing list or in your networks that might
fit this description, please reach out as soon as possible.
Best,
-Zac
reply other threads:[~2020-07-30 14:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CALUoyiA=c_wEFUPbXW=PT4EVnE6SH2vT=a2nkmL2hFa0RUJegA@mail.gmail.com' \
--to=zac.dydek@alum.mit.edu \
--cc=linux-wireless@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).