search

linux4wilc / driver

DEPRECATED: Updated Linux drivers for the ATWILC1000/ATWILC3000 products are located at https://github.com/linux4microchip/linux/tree/master/drivers/net/wireless/microchip/wilc1000. To simplify development, the legacy Linux4WILC was merged into the Linux4Microchip repo where driver development continues (Please refer latest ATWILC1000/ATWILC 3000 Wi-Fi Link Controller Linux User Guide) Driver code for Microchip ATWILC Wireless Devices (ATWILC1000 & ATWILC3000)
https://www.microchip.com/wwwproducts/en/ATWILC1000
32 stars 19 forks source link

Upstream roadmap #104

Open jan-kiszka opened 4 years ago

jan-kiszka commented 4 years ago

What's the relationship of this activity and the upstream wilc1000 driver? Are the plans to enhance the upstream version with wilc3000 support? Is there maybe a staging queue for upstream?

HDC67 commented 4 years ago

Probably worth reading the response here: https://github.com/linux4wilc/driver/issues/30

We're told this is the official version, but yes there seems to be semi parallel efforts. So in the two years, no progress seems to have been made wrt to the mainline kernel.

jan-kiszka commented 4 years ago

wilc1000 came out of staging by now (5.9). Apparently similar people involved for that. So it seems logical to me to ask for the next steps. Would be beneficial for everyone if this driver here can be retired.

tsifb commented 4 years ago

Interesting. Have you had a chance to diff that version with the the code here? There was quite some divergence a while ago.

jan-kiszka commented 4 years ago

They are still fairly different, though not completely. It will likely take some effort extract features and fixes from here, that's also why I'm asking for a potentially existing upstream queue with pending changes. The sooner everyone can and does focus on upstream, the better.

tsifb commented 4 years ago

It would certainly be nice to have 100% of resources going towards fixing issues, providing customer support and improving functionality.

Does upstream use the same firmware as is current in the firmware repo here? This is probably the most critical, being a closed-source binary blob.