-
Notifications
You must be signed in to change notification settings - Fork 7
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
NetBSD seems to have a driver #2
Comments
closed xmm7360/xmm7360-pci#64 for being duplicate and misplaced |
Which driver came first? It looks like the same driver. If they have sleep/resume, maybe we can too? 👀 |
Indeed, it's a descendant of the driver here. There's no particular hardware obstacle to sleep/resume - it just needs someone with a little patience and thought to get all the kernel side interfaces brought up and down in the right order, perhaps some of the BSD patience and thought can be reused! |
The core issue is the complete lack of support from Intel & Fibocom. Whereas Fibocom just stayed radio-silent and neither responds to requests for neither on Twitter nor via eMail - despite advertising the 850GL as compactible with Linux, Intel went out of their way to find excuse after excuse why they don't want to release anything. And I'm not saying that it's about legitimate [legal] concerns like IP [Patents & Licensing] preventing them to do so, but sheer lazyness, blaming OEMs instead. Which is hillarious considering that Intel's WiFi & Ethernet drivers work regardless of who's branding the chips have. Intel going full nVidia in that regard is just bad, and if Lenovo would not do bs like MAC-Whitelisting for WWAN NICs, I would've brought myself a Huawei Me906s long ago, because that one just works. |
According to
https://bsd-hardware.info/?id=pci:8086-7360-8086-0020
there is a functioning driver for NetBSD that does support the iXMM7360:
https://github.com/NetBSD/src/blob/trunk/sys/dev/pci/xmm7360.c
Maybe that'll hint an option to get the driver more stable and actually work fine.
The text was updated successfully, but these errors were encountered: