Posted: Tue Sep 03, 2019 18:10 Post subject: Atheros vs Broadcom
Atheros is mostly open-source. Broadcom isn't. They use large sections of binary blobs. Ex: Atheros's version of software NAT acceleration (Shortcut Forwarding Engine) is open-source, Broadcom's (Cut-Through Forwarding) is not. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Sep 03, 2019 21:12 Post subject:
Let me clarify: All of the Atheros source code and drivers are in the kernel source trees on the public repository. Firmware files, I am not 100% sure on, but the source code is there for the drivers and SoC boards.
Let me clarify: All of the Atheros source code and drivers are in the kernel source trees on the public repository. Firmware files, I am not 100% sure on, but the source code is there for the drivers and SoC boards.
This is not true. In Makefile.pb42 and others, make -f Makefile.pb42 ath9k is called. Under rules/all.mk ath9k points to a private directory include $(TOP)/private/ath9k-rules/ath9k.mk, see
Just placing public available ath9 code there is not working.
Also there is no code in the public repository for wireless tools such as iw etc. thus most likely not only ath9k code is contained in this private directory.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Sep 06, 2019 16:37 Post subject:
ATHDude wrote:
kernel-panic69 wrote:
Let me clarify: All of the Atheros source code and drivers are in the kernel source trees on the public repository. Firmware files, I am not 100% sure on, but the source code is there for the drivers and SoC boards.
This is not true. In Makefile.pb42 and others, make -f Makefile.pb42 ath9k is called. Under rules/all.mk ath9k points to a private directory include $(TOP)/private/ath9k-rules/ath9k.mk, see
Just placing public available ath9 code there is not working.
Also there is no code in the public repository for wireless tools such as iw etc. thus most likely not only ath9k code is contained in this private directory.
yes its tricky. basicly you can integrate your own mac80211/ath9k etc variant based on compat wireless. but it requires some work. i now added my mac80211 tree to the svn repository (you may need to change the path to get it working) with all local modifications i did. ath9k and ath10k is still excluded but you can integrate it from the official repository. i excluded it for a good reason since it contains code to unlock somewhat "curious" channels which are violating the fcc and etsi rules which should not be missused. i added also my building rules to the svn which helps with external builders _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Sep 06, 2019 18:36 Post subject:
^ This was a given and something I already knew before I destroyed my local code repo. It is very tedious to figure out what is and isn't in the public repo for whatever reason, but what was there before those commits could be made to work if you looked hard enough. One could even implement their own packages, kernels, etc. outside of the DD-WRT base code if one were so inclined. They could even completely build a source tree that is organized differently, if they wanted and make it work -- but that would make pulling updates from the public repository a bit difficult
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sat Sep 07, 2019 9:59 Post subject:
kernel-panic69 wrote:
^ This was a given and something I already knew before I destroyed my local code repo. It is very tedious to figure out what is and isn't in the public repo for whatever reason, but what was there before those commits could be made to work if you looked hard enough. One could even implement their own packages, kernels, etc. outside of the DD-WRT base code if one were so inclined. They could even completely build a source tree that is organized differently, if they wanted and make it work -- but that would make pulling updates from the public repository a bit difficult
its not as hard at least like in the early days of development. sometimes you have troubles with bad libraries in the local operating system. personally i only work with opensuse (latest leap right now). but i also managed todo with with ubuntu. all in utf8 localisation and english os language. if you have a difference character set than utf8 or compatible you may have problems _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Sat Sep 07, 2019 14:31 Post subject:
I haven't used SuSE in years -- 16 or so years, to be exact. That machine was running Ubuntu 18.04 LTS, but is now running Debian 10. Not 'hard', just time-consuming -- tedious. Most factory GPL source code organization is different, so following the bouncing ball is a little different, but not impossible.
