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
ramips-mt76x8: remove broken flag #1608
Conversation
This commit removes the broken flag from all devices in the mt76x8 subtarget. The stability of the mt76 driver for the mt7628 and mt7612 has greatly improved in the last half-year. It might be still behind ath9k and ath10k but it is suitable for daily use. This affects the following devices: - GL.iNet MT300N v2 - TP-Link Archer C50 v3 - TP-Link TL-WR841 v13
I thought it only runs fine if you do MoL? |
please read also comments after the one you linked. |
@rubo77 The thing is - yes the driver is not that stable as ath9k or ath10k. But with ath9k options slowly disappearing and being replaced with chips we don't know yet if they can be supported (QCN5502), having the option of less stable MediaTek devices is something we can only be happy about. mt76 has improved greatly stability wise even for mesh applications (which are not in the focus of the development afaik) so i think we are heading in the right direction there. As we might come to the point of people HAVING to replace their TL-WR841N, low cost options will be very appreciated. |
This commit removes the broken flag from all devices in the mt76x8 subtarget. The stability of the mt76 driver for the mt7628 and mt7612 has greatly improved in the last half-year. It might be still behind ath9k and ath10k but it is suitable for daily use. This affects the following devices: - GL.iNet MT300N v2 - TP-Link Archer C50 v3 - TP-Link TL-WR841 v13
This commit removes the broken flag from all devices in the mt76x8 subtarget. The stability of the mt76 driver for the mt7628 and mt7612 has greatly improved in the last half-year. It might be still behind ath9k and ath10k but it is suitable for daily use. This affects the following devices: - GL.iNet MT300N v2 - TP-Link Archer C50 v3 - TP-Link TL-WR841 v13
* update timezone-data 3d46f2593 timezone data: update to 2018c ee319993e Merge pull request freifunk-gluon#1613 from user7887/lede-17.01 9eee806f9 i18n-ru: fixed and updated russian translation 43ab9c0a8 Merge pull request freifunk-gluon#1608 from user7887/lede-17.01 e58ce740d luci-app-travelmate fixed f4d02b698 Merge pull request freifunk-gluon#1604 from user7887/lede-17.01 a016dbcee i18n-ru: fixed and updated russian translation 73abb7db5 Merge pull request freifunk-gluon#1590 from user7887/lede-17.01 b16253ed8 i18n-ru: fixed and updated russian translation f8682164c Fix bad argument #1 to 'tonumber'
Do you actually have no desire to at least take over version 14 (4/32) in principle? The cheapest alternative is currently the 801n (d) v5 from TPlink. |
@kueken this place (and old PR only vaguely related to your request) is not here to discuss new device support - please open a new pull request (PR) which provides the code for the device support you want and/or let's discuss it via IRC or mailing list. |
This commit removes the broken flag from all devices in the mt76x8
subtarget.
The stability of the mt76 driver for the mt7628 and mt7612 has greatly
improved in the last half-year. It might be still behind ath9k and
ath10k but it is suitable for daily use.
This affects the following devices: