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

Devices that don't support IBSS shouldn't be marked as BROKEN #1242

Closed
mweinelt opened this issue Oct 20, 2017 · 3 comments
Closed

Devices that don't support IBSS shouldn't be marked as BROKEN #1242

mweinelt opened this issue Oct 20, 2017 · 3 comments
Labels

Comments

@mweinelt
Copy link
Contributor

Currently four targets (ralink/mediatek) are marked as broken with the remark:

BROKEN: No AP+IBSS support

This is not necessarily anything that will ever be resolved.

Since 802.11s is working quite well and seems to be the successor of IBSS those devices are hardly broken, but only useful if the site already uses 802.11s mesh networking. In turn these could be marked conditional with a flag like MESH_11s instead of BROKEN.

@rubo77
Copy link
Contributor

rubo77 commented Oct 21, 2017

You could also add a tag 2.4GHZ_ONLY i.e. for the C25

@neocturne
Copy link
Member

I think a nice solution would be to change the GLUON_ATH10K_MESH variable to a generic GLUON_WLAN_MESH. It would default to 11s, skip building images for models that don't support the chosen mode (unless BROKEN is set), and select ath10k firmwares.

@rotanid
Copy link
Member

rotanid commented Jan 7, 2018

FYI: @2tata created a patch #1298 to fix this issue. maybe take a look at it to check if it works for you, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants