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

libusbdrivers: Add LWIP library #12

Merged
merged 1 commit into from
Jan 25, 2022
Merged

libusbdrivers: Add LWIP library #12

merged 1 commit into from
Jan 25, 2022

Conversation

szhuang
Copy link
Contributor

@szhuang szhuang commented Jan 24, 2022

LAN9730 utilizes LWIP when LWIP exists.

Signed-off-by: Siwei Zhuang [email protected]

LAN9730 utilizes LWIP when LWIP exists.

Signed-off-by: Siwei Zhuang <[email protected]>
@axel-h
Copy link
Member

axel-h commented Jan 24, 2022

So did this never compile before at all? I wonder, what is the actual dependency there, that the driver need to know about the higher layer protocols?

@szhuang
Copy link
Contributor Author

szhuang commented Jan 24, 2022

It never compiled with lwip turned on. We're reviving some legacy code which happens to use both lwip and usb.
The usb library combines host controller driver, usb 2.0 stack and the driver for individual devices, only the individual device drivers need to know high level protocol. Like libethdrivers, it needs to know how to work with lwip.

@axel-h
Copy link
Member

axel-h commented Jan 24, 2022

Change seem ok to me if this make it build again. Looks like this is another thing around improving GitHub CI coverage, see seL4/util_libs#112 (comment) and seL4/camkes#13

@szhuang szhuang merged commit 5dea49d into seL4:master Jan 25, 2022
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.

2 participants