You missed the point again, the challenge for dd-wrt is for the Devs to decide not me.
BTW Thanks for the pointer to "Open"wrt I'll "check it out" LOL [from GIT]!
I notice they use the word "users" rather than "developers" in the last sentence, now that sounds more like freedom to me:
"Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned."
Actually, it's you who doesn't get it.
You are a novice coming to a 10+years project and showing a "My way or the highway" atitude.
Main build and enivroment is by Brainslayer, he is in charge (maybe "benevolant dictator") of dd-wrt.
Eko, Fractal and Kong are all external builders who started publishing builds of dd-wrt to fill in the gap between Brainslayers builds.
Each of them figured out how to make a build.
You couldn't, so you showed your arrogance!
You don't have the knowledge, expertise or experience for what you want to do.
Goodybye to you, go bother somebody else.
I will be ignoring all posts related to this matter.
It's not worth my time or anyone elses to support or discuss with such arrogant fools. _________________ http://www.speedtest.net/result/3915993898.png
DO NOT 30-30-30 or erase nvram newer routers! It can brick them.
EA6700: Build 27745 (nvram below 32K, ipv6 - HE 6in4)
E4200: Build 26587
WRT54GL: Retired - waiting in the closet for an emergency.
colinsnj, once you're done discussing GPL politics here and are able to get to work on DD-WRT, you'd ideally go ahead and take a look at the recent reboot problems with the new ARM drivers.
You'll find the necessary driver debug info in another thread here.
Best thing is, you will not need to provide us with any builds of your own.
Given your vast knowledge of the GPL, I trust once you have fixed the driver issue, you will have commited the patches to a public repository, well documented the exact build environment and provided us with everything we need to compile on our own in no time.
I vote for an Ubuntu 14.04 LTS howto, but any other Unix will be fine, too.
Many thanks in advance.
colinsnj, once you're done discussing GPL politics here and are able to get to work on DD-WRT, you'd ideally go ahead and take a look at the recent reboot problems with the new ARM drivers.
You'll find the necessary driver debug info in another thread here.
The problem with the broadcom driver is, that it's closed source and without access to the source code you can just pray and hope that broadcom finds the bug, fixes it, and releases a new binary. If the driver would be open source, then everybody could search for the bug, and fix it, once the bug is found.
Posted: Sat Oct 11, 2014 16:05 Post subject: Good by to an incredible reference...
Wow, I can't believe that...
Probably are the worst news that read in long time.
Kong you have my full respect and I want to type here a big thanks for all your work here. Has been a good time testing your builds and playing with it as well.
In any case at some point you are comming to Barcelona let me know by a private message to grab a coffe or a dinner at least to give you the thanks face to face.
Grettings.
PS: Message to your company management: I'm happy to pay for "activation-licenses" in fact I did to two units WRT160NL in the past, so raise this comment at least to get some revenue and reconsider the public-developement. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
The problem with the broadcom driver is, that it's closed source and without access to the source code you can just pray and hope that broadcom finds the bug, fixes it, and releases a new binary. If the driver would be open source, then everybody could search for the bug, and fix it, once the bug is found.
Dream on..
The wl driver is a huge chunk of code which only a specialist is able to understand, you would need assistance from Broadcom hardware and software engineers in order to find and fix bugs in it. _________________ Kernel panic: Aiee, killing interrupt handler!
Posted: Sat Oct 11, 2014 17:03 Post subject: Re: Ceasing Development
Thanks so much Kong...you have put so much time and effort into these projects that we are all in your debt. Your builds were brilliant work and advanced in particular for me the NetGear appliances, R6300 and R7000 into devices truly useable. I appreciate it much....Bob
The problem with the broadcom driver is, that it's closed source and without access to the source code you can just pray and hope that broadcom finds the bug, fixes it, and releases a new binary. If the driver would be open source, then everybody could search for the bug, and fix it, once the bug is found.
Dream on..
The wl driver is a huge chunk of code which only a specialist is able to understand, you would need assistance from Broadcom hardware and software engineers in order to find and fix bugs in it.
Does it sound like I'm dreaming when I say, that it's not possible to fix the bug without sourcecode? I would say it's the opposite of dreaming.
The problem with the broadcom driver is, that it's closed source and without access to the source code you can just pray and hope that broadcom finds the bug, fixes it, and releases a new binary. If the driver would be open source, then everybody could search for the bug, and fix it, once the bug is found.
Dream on..
The wl driver is a huge chunk of code which only a specialist is able to understand, you would need assistance from Broadcom hardware and software engineers in order to find and fix bugs in it.
Does it sound like I'm dreaming when I say, that it's not possible to fix the bug without sourcecode? I would say it's the opposite of dreaming.
It is not possible to fix bugs in the wl driver without exceptional good knowledge about how the hardware works.
The hardware internal working is not documented anywhere so you will only see a lot of code and you will have no idea what the code does.
Believe me, I am quite familiar with Broadcoms SDK and I can easily follow the code in all of their other platform data and glue code for the SOC's.
I have a 3 year old wl source and almost all of it is swahili for me, I can only imagine what it is today after AC and beamforming has been added. _________________ Kernel panic: Aiee, killing interrupt handler!
The problem with the broadcom driver is, that it's closed source and without access to the source code you can just pray and hope that broadcom finds the bug, fixes it, and releases a new binary. If the driver would be open source, then everybody could search for the bug, and fix it, once the bug is found.
Dream on..
The wl driver is a huge chunk of code which only a specialist is able to understand, you would need assistance from Broadcom hardware and software engineers in order to find and fix bugs in it.
Does it sound like I'm dreaming when I say, that it's not possible to fix the bug without sourcecode? I would say it's the opposite of dreaming.
It is not possible to fix bugs in the wl driver without exceptional good knowledge about how the hardware works.
The hardware internal working is not documented anywhere so you will only see a lot of code and you will have no idea what the code does.
Believe me, I am quite familiar with Broadcoms SDK and I can easily follow the code in all of their other platform data and glue code for the SOC's.
I have a 3 year old wl source and almost all of it is swahili for me, I can only imagine what it is today after AC and beamforming has been added.
I never said that it would be easy to find bugs, but it would not be impossible if the source would be available.
PS: Message to your company management: I'm happy to pay for "activation-licenses" in fact I did to two units WRT160NL in the past, so raise this comment at least to get some revenue and reconsider the public-developement.
I suspect the issue with <kong>'s workplace is not this directly connected to DD-WRT per se. Maybe his company has some HR policy that they cannot hire or continue to employ software engineers who are involved in an intellectual property lawsuit of any kind, and if the asshole on this forum got one started against <kong>, that he might lose his job. This could be an inflexible rule from the HR department of his company that could not be waived even if he does outstanding work. Perhaps he might participate in other GPL based open source development as part of his employment and that he would not be able to continue that, if he is accused of violating GPL terms on any unrelated GPL code in his spare time. But this is just my pure speculation and I have no way to verify that.
Anyway, this is a case of one asshole ruining things for everyone with his threats.
PS: Message to your company management: I'm happy to pay for "activation-licenses" in fact I did to two units WRT160NL in the past, so raise this comment at least to get some revenue and reconsider the public-developement.
I suspect the issue with <kong>'s workplace is not this directly connected to DD-WRT per se. Maybe his company has some HR policy that they cannot hire or continue to employ software engineers who are involved in an intellectual property lawsuit of any kind, and if the asshole on this forum got one started against <kong>, that he might lose his job. This could be an inflexible rule from the HR department of his company that could not be waived even if he does outstanding work. Perhaps he might participate in other GPL based open source development as part of his employment and that he would not be able to continue that, if he is accused of violating GPL terms on any unrelated GPL code in his spare time. But this is just my pure speculation and I have no way to verify that.
Anyway, this is a case of one asshole ruining things for everyone with his threats.
I PMed Kong about paying for a US-based IP consult with my friend, but haven't heard back yet.
