Why is it so hard to get openwrt image for broadcom soc devices?
- User
Why is it so hard to get openwrt image for broadcom soc devices?
- Assistant
Obtaining OpenWRT images for Broadcom SoC devices is challenging due to several key factors:
1. Limited Open-Source Driver Support
Broadcom has a reputation for not releasing Free and Open Source Software (FOSS) drivers for their hardware. This lack of support means that OpenWRT developers must rely on reverse-engineered drivers or proprietary firmware blobs, which are often incomplete or incompatible with OpenWRT's open-source philosophy[2][4][5][10].
2. Proprietary Firmware Blobs
Many Broadcom devices require proprietary firmware blobs to function, particularly for WiFi. These blobs are not freely available or redistributable, which conflicts with OpenWRT's principles. As a result, OpenWRT often does not include support for Broadcom's WiFi capabilities, leaving only partial functionality, such as Ethernet support[2][4][9].
3. Driver Quality and Performance Issues
Even when third-party or proprietary drivers are used, their performance is often subpar. Users report issues such as weak signal strength, limited functionality (e.g., lack of 5 GHz support), and instability when running OpenWRT on Broadcom-based devices[5][10][17].
4. Complexity of Reverse Engineering
Reverse engineering Broadcom's hardware to create open-source drivers is a time-consuming and resource-intensive process. This effort is further complicated by Broadcom's lack of documentation and active discouragement of open-source development[5][9][14].
5. Alternative Firmware Options
Due to these challenges, other firmware projects like DD-WRT and Tomato have focused more on Broadcom devices. These projects often include proprietary Broadcom drivers, which allows for better functionality but deviates from the open-source ethos of OpenWRT[2][5][17].
6. Hardware-Specific Limitations
Broadcom devices often have unique hardware configurations or locked-down bootloaders, making it difficult to flash OpenWRT images. This adds another layer of complexity for developers and users attempting to use OpenWRT on these devices[3][13].
Conclusion
The difficulty in obtaining and using OpenWRT images for Broadcom SoC devices stems from Broadcom's lack of open-source support, reliance on proprietary firmware, and the technical challenges of reverse engineering. For users seeking robust OpenWRT support, it is recommended to choose devices with chipsets from manufacturers like MediaTek, Qualcomm, or Intel, which have better open-source compatibility[4][18].
- User
Popular nic such as intel also relies on firmware blobs but is still widely used and recomended across linux distributions. Can it be considered just as broadcom because of such blobs or are they more suitable for openwrt systems? I have router cudy be3600 and i want more features that stock software can prowide but it has broadcom chip, what are my options?
- Assistant
Intel Firmware Blobs vs. Broadcom Firmware Blobs
While both Intel and Broadcom rely on proprietary firmware blobs, Intel devices are generally more suitable for OpenWRT and Linux systems due to the following reasons:
-
Community Collaboration: Intel actively works with the Linux community to ensure their drivers (e.g.,
iwlwifi) are included in the mainline Linux kernel. Their firmware blobs are also distributed under licenses that allow redistribution, making them easier to integrate into Linux distributions and OpenWRT[3][9]. -
Driver Quality: Intel's open-source drivers are well-maintained and provide robust performance. While firmware blobs are required, the drivers themselves are open-source, ensuring better compatibility and fewer limitations compared to Broadcom's proprietary drivers[3][9].
-
Broadcom's Limited Support: Broadcom, on the other hand, has a history of poor open-source support. Their WiFi drivers are often proprietary, and the lack of open-source alternatives means OpenWRT support is limited or non-existent for many Broadcom devices[11][14][17].
Options for Your Cudy BE3600 Router
The Cudy BE3600 router uses a Broadcom BCM6764 chipset, which poses significant challenges for running OpenWRT due to Broadcom's limited open-source support[8][15]. Here are your options:
-
Stick with Stock Firmware:
- Cudy's stock firmware provides basic functionality and some advanced features like VPN support and mesh networking. However, it may not offer the full customization and package management capabilities of OpenWRT[8][10].
-
Explore Other Firmware Options:
- Broadcom-based routers are better supported by alternative firmware like DD-WRT or FreshTomato. These projects often include proprietary Broadcom drivers, enabling better functionality than OpenWRT for such devices[17].
-
Use the Router as a Dumb Access Point:
- If you need advanced features, consider using the BE3600 as a simple access point while offloading routing and other tasks to a more OpenWRT-compatible device, such as one with a MediaTek or Qualcomm chipset[6][16].
-
Replace the Router:
- If OpenWRT's flexibility is essential, consider replacing the BE3600 with a router that has better OpenWRT support. Devices with MediaTek or Qualcomm chipsets are highly recommended due to their strong open-source driver support[4][16].
Conclusion
While Intel's reliance on firmware blobs is a compromise, their active collaboration with the Linux community and robust driver support make their devices far more suitable for OpenWRT and Linux systems than Broadcom's. For your Cudy BE3600, the best course of action depends on your priorities. If OpenWRT is non-negotiable, replacing the router with a more compatible model is the most practical solution.
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.