Skip to content
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

Kernel 4.15 #2

Open
dspmathguru opened this issue Jan 7, 2019 · 2 comments
Open

Kernel 4.15 #2

dspmathguru opened this issue Jan 7, 2019 · 2 comments

Comments

@dspmathguru
Copy link

Trying to compile with kernel 4.15.0-43-generic under Ubuntu 18.04.

There was a change from setup_timer to timer_setup. So made this simple change in the xhci.c and xhci-mem.c files.

setup_timer(a, b, c) ==> timer_setup(a, b, 0)

Then found out that the type of the call back 'b' is wrong. So not sure how to proceed.

Also, I wonder if xhci is even needed as in the kernel there is already files for xhci.

Please advise.

@sarman1998
Copy link
Contributor

The code here was based of the 3.18 kernel. I agree it isn't ideal to have copies of the xhci* files from the normal kernel source in this repository. I had to make some changes to those files to work with this driver and maintaining a copy of the files is that way i chose to handle that.

As for the compile error, take a look at the diffs of those xhci files in the kernel source from 3.18 -> 4.15,
I can see that they changed the signature of the callback function.
in 3.18: https://elixir.bootlin.com/linux/v3.18/source/drivers/usb/host/xhci-ring.c#L820
in 4.15: https://elixir.bootlin.com/linux/v4.15/source/drivers/usb/host/xhci-ring.c#L938

Best thing to do would be to update all the xhci* files with the changes between 3.18 and 4.15.

What are you planning to use FL6000 for?

@dspmathguru
Copy link
Author

Thank you for the response. I would rather not use a public forum to discuss our future product plans. I believe your CEO knows about what we are doing and it is critical to have Linux support for your products. We do appreciate the support.

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

No branches or pull requests

2 participants