From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Louie Lu <me@louie.lu>, Make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] How to efficient test ath10k driver changed on LEDE platform?
Date: Tue, 12 Dec 2017 14:03:42 +0100 [thread overview]
Message-ID: <87d13kxfm9.fsf@toke.dk> (raw)
In-Reply-To: <CADMDV=zQy1_TATH2XhrkB6FsruKbO+w9ueAdtbDLvKbfwyqeaQ@mail.gmail.com>
Louie Lu <me@louie.lu> writes:
> Hi all,
>
> I'm using TP-Link C2600 with LEDE to test ath10k driver,
> not sure if there have a better way to make the procedure more efficient.
>
> This is my current workflow:
>
> 1. Using ath.git to make the changed I want (apply make-wifi-fast path
> for example)
> 2. git-patch to get the patch file
> 3. Put the patch file into LEDE ./package/kernel/mac80211/patches/
> 4. Build up LEDE
> 5. scp ath10k kernel module into C2600 and reboot C2600
> 6. Check and test with the modified driver
>
> I'm wondering if step 5 can reduce the reboot step, just rmmod and insmod
> ath10k driver when it is running to save the reboot time.
Yup, reinstalling the kmod-ath10k package (or just copying over the new
.ko) and rmmod/insmod is fine. Just make sure you get all the modules
(including all the ath* and mac80211*).
> Also, sometimes apply patch into LEDE may cause error when compiling
> ath10k driver,
> is there any way to specify which version of ath10k that LEDE to
> build?
LEDE backports the entire WiFi stack. So it's way newer than the rest of
the kernel; think you can see the date it was backported in the version
number in the Makefile.
-Toke
next prev parent reply other threads:[~2017-12-12 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 12:28 Louie Lu
2017-12-12 13:03 ` Toke Høiland-Jørgensen [this message]
2017-12-14 13:45 ` Louie Lu
2017-12-14 14:28 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d13kxfm9.fsf@toke.dk \
--to=toke@toke.dk \
--cc=Make-wifi-fast@lists.bufferbloat.net \
--cc=me@louie.lu \
/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