From: Alex Dewar <alex.dewar90@gmail.com>
To: davem@davemloft.net, Jakub@medion, Kicinski@medion,
kuba@kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: How to port rtl8xxxu to new device...?
Date: Sun, 17 Jan 2021 17:55:33 +0000 [thread overview]
Message-ID: <20210117175533.ya3wcb6yyqfgwiln@medion> (raw)
Hi all,
I'm currently trying to port the rtl8xxxu driver to RTL8822u chips (one
of which I own), but I'm finding it hard to figure out where to start
and I figured that some wiser minds could maybe help steer me in the
right direction.
I've managed to get as far as reading and writing to various registers
as part of the device setup, but the dongle appears to crash at the
downloading firmware stage. At the moment it just feels like I'm
changing random bits and pieces to see what happens. I'm using this
downstream driver for reference: https://github.com/RinCat/RTL88x2BU-Linux-Driver
Does anyone know of any documentation or anything that could be useful
for working on this?
Best,
Alex
reply other threads:[~2021-01-17 17:58 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=20210117175533.ya3wcb6yyqfgwiln@medion \
--to=alex.dewar90@gmail.com \
--cc=Jakub@medion \
--cc=Kicinski@medion \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).