Skip to content
The Chat Archive
sonar-reasoning LMArena Search Arena 24K

Why is it so hard to get openwrt image for broadcom soc devices?

  1. User

    Why is it so hard to get openwrt image for broadcom soc devices?

  2. Assistant

    The challenges in obtaining OpenWrt images for Broadcom SOC devices stem from Broadcom's limited open-source support and philosophical differences with OpenWrt's development model. Here's a breakdown of the key factors:


    1. Broadcom's Proprietary Driver Policy

    Broadcom historically restricts access to open-source drivers for their wireless and network hardware, requiring reliance on binary blobs (proprietary firmware) for full functionality[2][4][7]. This conflicts with OpenWrt's preference for Free/Libre and Open Source Software (FLOSS), which avoids non-free components[2][4].


    2. Limited Community Support

    • Reverse-Engineered Drivers: OpenWrt often depends on community-developed drivers (e.g., brcmfmac for Broadcom WiFi), which may lack stability or full feature support[7]. These drivers are frequently incomplete or buggy compared to proprietary alternatives[7].
    • Case-by-Case Support: OpenWrt support for Broadcom devices is inconsistent. For example:
      • Netgear R7000: Only Ethernet is supported in OpenWrt, while WiFi requires proprietary drivers[2].
      • Linksys EA9500: Users report weak signals and connectivity issues due to suboptimal driver support[7].

    3. Philosophical and Technical Barriers

    • OpenWrt's Open-Source Philosophy: The project prioritizes FLOSS components, excluding proprietary blobs. This limits functionality on Broadcom devices that require non-free drivers[2][4].
    • Hardware Complexity: Broadcom SOCs often integrate specialized hardware (e.g., WiFi, switch controllers) that lacks proper documentation, complicating driver development[3][7].

    4. Alternatives and Workarounds

    Some users opt for DD-WRT or Tomato, which include proprietary Broadcom drivers, but these projects face their own challenges (e.g., outdated support, stability issues)[2][7]. For example:

    • Netgear R7000: Advanced Tomato is recommended over OpenWrt for WiFi functionality[2].
    • Linksys EA9500: DD-WRT support remains a "work in progress" with unresolved issues[7].

    5. Impact on Device Selection

    OpenWrt's hardware compatibility table explicitly warns against Broadcom WiFi chipsets due to limited FLOSS driver availability[4]. This discourages users from choosing Broadcom-based devices for OpenWrt installations, pushing them toward alternatives like Mediatek or Qualcomm SOCs[5][6].


    Conclusion

    The difficulty in obtaining reliable OpenWrt images for Broadcom SOC devices is rooted in Broadcom's closed-source practices and OpenWrt's commitment to open-source principles. While community efforts exist, they often result in unstable or incomplete implementations, making Broadcom devices less viable for OpenWrt compared to other SOCs[2][4][7].

  3. 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?

  4. Assistant

    The distinction between Intel and Broadcom in OpenWrt compatibility lies in collaboration with open-source communities and licensing practices, not just the presence of firmware blobs. Here's a breakdown:


    1. Intel vs. Broadcom: Key Differences

    AspectIntelBroadcom
    Firmware LicensingFirmware included in linux-firmware[3][7]Proprietary blobs excluded from mainline[2][4]
    Driver DevelopmentFOSS drivers (e.g., iwlwifi) in mainline[3]Relies on reverse-engineered drivers (e.g., brcmfmac)[7]
    Community SupportStable, widely adopted in Linux distros[3][7]Limited, inconsistent functionality[2][4]
    OpenWrt ViabilityRecommended for routers (e.g., Intel-based devices)Discouraged due to WiFi/switch limitations[4][8]

    2. Cudy BE3600 Options

    For your Cudy BE3600 (Broadcom-based), options are constrained but not impossible:

    A. OpenWrt Installation

    1. Cudy-Signed OpenWrt Image:

      • Use Cudy’s pre-signed OpenWrt firmware to bypass bootloader restrictions[4].
      • Steps:
        1. Download Cudy’s OpenWrt image from their site (if available).
        2. Flash via the OEM firmware’s GUI (System → Firmware)[4].
        3. Post-installation: Enable WiFi via Ethernet (wireless disabled by default)[4].
    2. Post-Installation Limitations:

      • WiFi: May require proprietary drivers (e.g., brcmfmac), leading to weak signals or instability[7].
      • Switch/Port Control: Broadcom’s switch drivers are often incomplete[4].

    B. Alternatives to OpenWrt

    • DD-WRT/Tomato: Include proprietary Broadcom drivers but face stability issues[2][7].
    • Stock Firmware: Cudy’s firmware may support VPN/WireGuard (as seen in BE3600 China models)[8], but lacks advanced features.

    C. Hardware Recommendations

    If OpenWrt is critical, consider routers with Mediatek/Qualcomm SOCs (e.g., TP-Link Archer C7, Xiaomi Mi Router 4A Gigabit), which have better FLOSS driver support[4][5].


    3. Why Intel Is More OpenWrt-Friendly

    Intel’s firmware is redistributable and integrated into linux-firmware, making it compatible with OpenWrt’s FLOSS philosophy[3][7]. Broadcom, by contrast, restricts firmware distribution, forcing reliance on community workarounds[2][4].


    Conclusion

    While both Intel and Broadcom use firmware blobs, Intel’s collaboration with Linux communities makes its devices viable for OpenWrt. Broadcom’s closed practices render its hardware less suitable. For the Cudy BE3600, proceed with Cudy’s signed OpenWrt image but expect WiFi/switch limitations. Long-term, prioritize non-Broadcom routers for OpenWrt[4][8].

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.