Skip to content

Fix two building errors when we build the kernel in the non-src folder #3215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 9, 2019
Merged

Fix two building errors when we build the kernel in the non-src folder #3215

merged 2 commits into from
Sep 9, 2019

Conversation

jason77-wang
Copy link
Contributor

It is because the building process can't find the needed header files. And this already introduced building errors on the branches of 5.2.y and 5.3.y for RPi4, and I guess all branches need these two fixes, it is safe to merge these two patches to base branch then it will apply to all branches automatically?

If we build the kernel with "-O=$non-src-folder", this driver will
introdcue a building error because of the header's location.

Signed-off-by: Hui Wang <[email protected]>
If we build the kernel with "-O=$non-src-folder", this driver will
introdcue a building error because of the header's location.

Signed-off-by: Hui Wang <[email protected]>
@pelwell
Copy link
Contributor

pelwell commented Sep 9, 2019

@kbingham This reverses your commit - any comments?

@kbingham
Copy link
Contributor

kbingham commented Sep 9, 2019

@pelwell Ack on this.
Tested-by: Kieran Bingham [email protected]

It looks like my earlier fix was squashed in, so perhaps it got squashed or merged with some other change that affected things here.

Anyway, I can confirm Jason's patch compiles VC_SM where as without Jason's patch - there is a failure to build the VC_SM code.

I have not tested the rtl8192cu.

@pelwell
Copy link
Contributor

pelwell commented Sep 9, 2019

Thanks. I'll take the 8192 change on trust.

@pelwell pelwell merged commit c506530 into raspberrypi:rpi-5.3.y Sep 9, 2019
@kbingham
Copy link
Contributor

kbingham commented Sep 9, 2019

Well, to put your mind at ease, as I had the build environment all set up I've added CONFIG_RTL8192CU=y and it built successfully.
(Although there is a lot of clean-up required in that driver!!!)

Out of interest, why is this driver included in the RPi kernel?
https://github.com/pvaret/rtl8192cu-fixes declares that it is deprecated and that rtl8xxxu available from linux-4.4 should be used first. As this tree is now 5.3....

Is there a specific use case needed to support this driver? If not - I'd perhaps recommend dropping it!

@pelwell
Copy link
Contributor

pelwell commented Sep 9, 2019

Is there a specific use case needed to support this driver?

@popcornmix?

@popcornmix
Copy link
Collaborator

When using 4.9 kernel we switched to mainline driver and got a lot of complaints about unreliable wireless. We currently build both and blacklist one so users can switch.
See: #1866

It is possible the driver has improved in the meantime, but I'm not too optimistic.

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.

4 participants