1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tomato architecture question

Discussion in 'Tomato Firmware' started by gfunkdave, Jan 18, 2013.

  1. gfunkdave

    gfunkdave LI Guru Member

    Why does Tomato only support Broadcom routers? DD-WRT supports Broadcom, Atheros, and I think Ralink, so it can be done. Is there something inherent in Tomato that precludes it from working with non-Broadcom routers? Seems like it would be really helpful in getting wider adoption for Tomato for it to support non-Broadcom routers.

    Thanks
     
  2. gogubeb

    gogubeb Addicted to LI Member

    Something interesting here
     
  3. Mangix

    Mangix Networkin' Nut Member

    too much code would need to be written. better off doing openwrt if you want atheros.

    as for dd-wrt, they use a non-public ath9k driver.

    edit: forgot to mention: tomato started out as a fork of HyperWRT which was a fork of the linksys firmware for the WRT54GL. Broadcom from birth and probably until the day it dies.
     
  4. RMerlin

    RMerlin Network Guru Member

    Also, DD-WRT has at least one full time developer (Brainslayer) and a few other active ones (Ash and Eko). Tomato on the other hand has to rely on very few maintainers who are doing this out of their spare time. Adding support for a new platform requires a LOT of work. It's possible - that's what Asus did with Asuswrt, which was originally based on Tomato and now supports both Broadcom and Ralink - but it requires a lot of work and expertise.
     

Share This Page