Skip to content

Patch for compiling with kernel 4.11.9 - #47

Closed
zebulon2 wants to merge 17 commits into
astsam:v5.1.5from
zebulon2:v5.1.5
Closed

Patch for compiling with kernel 4.11.9#47
zebulon2 wants to merge 17 commits into
astsam:v5.1.5from
zebulon2:v5.1.5

Conversation

@zebulon2

@zebulon2 zebulon2 commented Jul 6, 2017

Copy link
Copy Markdown

Patch for compiling with kernel 4.11.9 and 4.12+. This patch was taken from kernel developer Stephen Rothwell. See LKML post https://patchwork.kernel.org/patch/9773573/ for details.

kimocoder and others added 14 commits May 16, 2017 18:45
* Added support for "Alfa - AWUS036AC"
* Added support for "TP-Link - Archer T4U AC1300"
* Added support for "TP-Link - T4UHP"
* Added support for "GMYLE - AC450"
* Added support for "Tenda - U12"
* Added support for "Amped Wireless ACA1"
* Added support for "Netis WF2190"
* Added support for "I-O DATA - WN-AC433UA"
* Added support for "Comcast - CF-915AC"
* Added Kernel v4.12 support
* Reverted back to originally added devices, left UPPERCASE & kernel v4.12 support intact
Fixes TX_Power to Max to that RegDoms allowed maximum, resolves issues with TLP and other powersaving affecting signal stability.
@CGarces

CGarces commented Jul 11, 2017

Copy link
Copy Markdown

@zebulon2 Note that you are sending a lot of commits, all the ones form @paspro fork.
For 4.12 only 3f0b82e is needed and for 4.11.9, check #50 that contains the correct fix.
Consider close this one.

@MilhouseVH

Copy link
Copy Markdown

@gordboy yes, the 4.12 commit 3f0b82e is incomplete and doesn't build - this is the fix I've just submitted to the paspro repo: https://github.com/paspro/rtl8812au/pull/4

If anyone wants to cherry-pick it they're more than welcome.

@ghost

ghost commented Jul 14, 2017

Copy link
Copy Markdown

@MilhouseVH yes I committed something very similar myself, about 3 hours ago, to my 5.2.9 as part of my AIO 4.12 commit gordboy/rtl8812au@2217dd0 Try to keep up squire... :)

@MilhouseVH

MilhouseVH commented Jul 14, 2017

Copy link
Copy Markdown

Yes, sorry - it's annoying seeing these same build issues crop up with a new/different repository when you think you'd already fixed it 2 months ago... :)

@ghost

ghost commented Jul 14, 2017

Copy link
Copy Markdown

@MilhouseVH I'm beginning to think you and I are the only actual humans here, and the rest are auto-commit bots as part of some arcane Google conspiracy to obfuscate ... anyways 5.2.9 is going very swimmingly. And I shall search your stuff first in future, instead of working things out for myself. Take care, squire.

@kimocoder

kimocoder commented Jul 14, 2017

Copy link
Copy Markdown

I said the commit was dirty and needed review & testing.

And with 2 months away without my computer it's kinda hard to keep up or even fix it, but you guys seem to got it going, so.. Im out :)

@MilhouseVH

MilhouseVH commented Jul 15, 2017

Copy link
Copy Markdown

@zebulon2 you've pulled a lot of other commits I'm now pretty sure you did not intend to include in this PR. You need to rebase this pull request without the other commits.

@MilhouseVH

Copy link
Copy Markdown

@zebulon2: Please close this as it can't possibly be merged in this state, and #50 is now available which does the job.

@zebulon2

Copy link
Copy Markdown
Author

Apologies for the issue. Glad this is now resolved.

@zebulon2 zebulon2 closed this Jul 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants