Navigation Menu

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

ramips-mt76x8: remove broken flag #1608

Merged
merged 1 commit into from Dec 29, 2018

Conversation

blocktrron
Copy link
Member

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
@rotanid rotanid added the 3. topic: hardware Topic: Hardware Support label Dec 29, 2018
@rotanid rotanid merged commit 55d2acd into freifunk-gluon:master Dec 29, 2018
@rubo77
Copy link
Contributor

rubo77 commented Dec 30, 2018

@rotanid
Copy link
Member

rotanid commented Dec 30, 2018

please read also comments after the one you linked.
blocktrron and myself were observing mt76x8 devices over a long period and came to the conclusion already written in this PR here, see above.

@blocktrron
Copy link
Member Author

@rubo77
It might be a bit confusing but just to clarify: If i would have the choice i would pick a recent ath9k based device over every mt76x8 based one.

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.

@blocktrron blocktrron deleted the pr-mt76x8 branch January 17, 2019 07:23
mweinelt pushed a commit that referenced this pull request Feb 26, 2019
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
christf pushed a commit to christf/gluon that referenced this pull request May 23, 2019
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
SvenRoederer added a commit to SvenRoederer/freifunk-gluon_core that referenced this pull request Sep 29, 2019
* 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'
@kueken
Copy link

kueken commented Oct 15, 2020

Do you actually have no desire to at least take over version 14 (4/32) in principle?
In principle it is still completely sufficient for Freifunk and would be helpful to the community as a 15 € router.
Probably many have bought the device 'accidentally' and it is now lying around unused.

The cheapest alternative is currently the 801n (d) v5 from TPlink.
Also the same chipset.
Then there would be Netgear 6120.
Just a question.
Openwrt is built and runs for the 841n V14.
I also get Sysupgrade built for Freifunk, but the router cannot be flashed via sysupgrade?

@rotanid
Copy link
Member

rotanid commented Oct 15, 2020

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. topic: hardware Topic: Hardware Support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants