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

Porting Tomato Firmware to other platforms

Discussion in 'Tomato Firmware' started by Victek, May 2, 2014.

  1. Victek

    Victek Network Guru Member

    Well .. the thread is official, thanks to Toxic (linksysinfo.org admin) contacts we received from Belkin sample units to embed Tomato Firmware for WRT AC1900. A new platform, Marvell ARM 1.2GHz and a gorgeous Deja Vu WRT54GL style. The first job has been to discover the serial tag, no information in Internet, so we create an small info for interest about this new model and the Return of Linksys to Open Source. ;)

    Link to Serial Tag for WRT1900AC: http://goo.gl/w17lDh

    Let's begin, thanks to all fellows in linksysinfo.org and Tomato Forum for your support.
     
    MarkDe, Toxic, szpunk and 2 others like this.
  2. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    The first foray of Tomato onto Marvell-based hardware (maybe also kernel 3.x and collaboration with OpenWRT devs). Should I say congratulations, or offer my condolences on the upcoming loss of all your weekends and evenings? ;-)
    Seriously though, kudos to the Tomato community for making it happen!
     
  3. jerrm

    jerrm Network Guru Member

    This is great news, but I hope focus isn't lost on the existing Broadcom ARM platforms.

    I think part of Tomato's success has been the fact it has never tried to support everything out there, but what it does do it does very well.

    Before devoting a lot of time to one unit, I would want to know if the chipsets involved are in the pipeline for many other models. We are in the middle of a platform shift though, and there is no guarantee of longevity with anyone.
     
  4. Victek

    Victek Network Guru Member

    Thanks for the late coffee ;), one small correction, there is no Openwrt code in this product at the moment....

    Regards!
     
  5. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    That's why I said "maybe" ;-)
     
  6. jerrm

    jerrm Network Guru Member

    For the record, I never said it was dead. I said it could be at risk if no one took on the challenge. Always thought you would and am greatful you did.

    Even if it is only Linksys, if they stick with it and populate through several models in their line would still be worthwhile.

    Is there any similarity to Broadcom in the wireless driver interface/wl (or equivalent) syntax, or will anything that touches wireless need to be recoded?
     
  7. BrainSlayer

    BrainSlayer Network Guru Member

    one time the WRT1900AC will be a opensource router. but right now its not opensource since all important part are closed source. this is why openwrt and also my project dd-wrt wont support it right now. we need the sourcecodes for our custom kernels. belkin did not provide these sources yet even if they told us that they will. so whatever they say. up to now, this product is everything else, but not the new cool opensource stuff. its a expensive brick for developers
     
    shibby20 likes this.
  8. Victek

    Victek Network Guru Member

    I started reading code and doing the map two hours ago... there are some nice features like soft-fp, are almost binaries, good code for logic drivers...

    For the interest of the Tomato community and linksysinfo.org we would do our best to support this specific platform with Tomato, hopefully it may help to speed things up with other firmwares too.
     
  9. BrainSlayer

    BrainSlayer Network Guru Member

    it wont. we are depending on the wireless driver sources etc, since we wont use the original kernel. for sure this isnt related to tomato, but we think that belkin is going a wrong way here. its announced at opensource router, but every ralink based router on the market is more opensource than this. the same for atheros socs
     
  10. BrainSlayer

    BrainSlayer Network Guru Member

    its marketing foo and this is what drives me mad. belkin announced full openwrt and dd-wrt support without asking us and later we found out that the provided sdk is a whole blob of binary files without sourcecodes. ah and not to forget, i dont even got any hardware sample
     
    Siff, mstombs, kthaddock and 5 others like this.
  11. mstombs

    mstombs Network Guru Member

    I like the way Victek mis-uses the product name WRT1900AC - deliberate to avoid auto referral link or is the AC1900 a better recommendation?

    At least they seem to have fitted a serial header - the WRT54G just had solder pads, but to market a router for open-source and make it so hard to get to the adaptor! Some other recent Linksys routers had serial available via a LAN port - presumably just for factory test. Is that JTAG header pins I see on the photos too?

    Has anyone checked if Belkin source even complete with respect to basic GPL obligations - even U-Boot bootloader is GPL licensed, and I'm sure they have a custom build? AFAIK proprietary binary kernel modules were deemed OK by Linus, however useless for open-source community (locks kernel) - but the modules themselves cannot contain GPL licensed code.
     
    Last edited: May 3, 2014
  12. Victek

    Victek Network Guru Member

    a) ;) .. yes, will correct now.
    b) no, no external pin-out.
    c) correct, it's not complete GPL compliant. The method for firmware build it's new for me, we can do for future tomato releases, the script check for new versions in some packages from the repositories and then update and build.... it saves a lot of time for new versions.. but also can pull new bugs
     
  13. WRTed

    WRTed Reformed Router Member

    Good luck Vic!

    Have used your awesome tomato releases in the past, and if anyone can figure it out you can.

    I also just received my WRT1900AC, so can't wait!
     
  14. Victek

    Victek Network Guru Member

    Some references to Openwrt are in, my mistake...

    Code:
    openwrt_altnandboot=nand read $default_load_addr $alt_kern_addr $openwrt_fw_size                                                                      ; setenv bootargs $console $default_mtdparts root=/dev/mtdblock7 ro rootfstype=$                                                                      fs_type init=/sbin/init; bootm $default_load_addr;
    openwrt_fw_size=0x4000000
     
  15. RMerlin

    RMerlin Network Guru Member

  16. Chad Burks

    Chad Burks Networkin' Nut Member

  17. RMerlin

    RMerlin Network Guru Member

    Hard to say without the actual context of what he said, but he was probably referring to the initial OpenWRT submission from the first week of April, which included only binary blobs of the drivers. The driver source code was provided a few weeks later.
     
  18. Chad Burks

    Chad Burks Networkin' Nut Member

    Thanks Merlin! I'm not a coder, just trying to follow along. I can manage the stuff all day, but am helpless to do anything currently (Except donations here and there when I can).
     
  19. Netwet

    Netwet Reformed Router Member

    LOL. Then you probably have to wait very long. Even OpenWRT devs said they won't support it unitl Belkins mess is cleaned up.
    Tomato has only support for broadcom wireless units and only support for cfe based models.
    This unit is completely different you can't just grab the kernel and hack it into tomato.

    If OpenWRT does add support for it and DD-WRT has no interest, then this unit is dead.

    I give Tomato devs two weeks until they realize, that they cannot do it.
     
  20. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    Why so pessimistic? My 2 cents: I suspect the approach will be to integrate the Tomato UI and features into the Belkin firmware and make use of Belkin's SDK and binary blob wireless drivers. This is one situation where not being an open source purist is an advantage. The OpenWRT folks want open source and clean code. That's why many Broadcom devices are "supported" only in OpenWRT trunk and still don't work. The Tomato devs are more practical and willing to compromise, essentially perfecting and shoring up the existing offering rather than reinventing the wheel and ending up with nothing to show for it.
     
  21. shibby20

    shibby20 Network Guru Member

    Marcel, because this

    is truth.
     
  22. Netwet

    Netwet Reformed Router Member

    OpenWRT devs want sources in order to be able to maintain a build in order to be able to update the kernel etc.
    Tomato is stuck on an old kernel.

    If there are security issues found someone has to backport them. The question is, do oems backport all issues, I doubt they have the man power for it. But that is not the main problem. OpenWRT devs also mentioned, that the linux wireless tools that are used to configure this radio don't use standard interfaces, but heavily patched/extended tools, which are also difficult to maintain.

    Tomatos UI is relying on a few basic things, like nvram handling , wl tool etc. but these things don't exist on the WRT1900. I could imagine that it would be much easier for DD-WRT to add support for the WRT1900AC, as DD-WRT already supports units that use linux wireless tools , they also have support for uboot units, that don't store configs params in nvram etc.

    This is not like adding a few ifs and defines , you probably have to write a lot of code in order to have the functionality in order to be able to store config stuff etc. OpenWRT has a writeable filesystem, they don't configure the router via nvram commands.
     
  23. jerrm

    jerrm Network Guru Member

    There are ways of dealing with the wl/nvram interface stuff without digging into every line of code that relies on them.

    My main concern is it worth the effort if this turns out to be a one-off unit, or will there be multiple manufacturers with units built around the same basic architecture.

    Also as I said before, Tomato is at least in part successful because it has been focused on one basic platform and does that very well. We don't need to start chasing every new router.
     
  24. blacklotus83

    blacklotus83 Network Newbie Member

    I see a fan for cpu cooling on your pics. This is really a drawback for me... Do you hear the fan?
     
  25. RMerlin

    RMerlin Network Guru Member

    The fan doesn't spin at all under normal use. Tim Higgins was only able to see it spin while he was doing sustained transfer tests with the router, and even then it was near silent.

    Personally, I never heard it spin at all during my own tests.
     
  26. blacklotus83

    blacklotus83 Network Newbie Member

    Ok, thanks!
     
  27. FattysGoneWild

    FattysGoneWild LI Guru Member

    I smell a hardware revision with Broadcom hardware in the near future.......
     
  28. roadkill

    roadkill Super Moderator Staff Member Member

    I doubt it..
     
  29. XVortex

    XVortex Serious Server Member

    EA6900 is based on Broadcom hardware.
     
  30. FattysGoneWild

    FattysGoneWild LI Guru Member

    Speaking of the EA6900. I might have missed it. Any reason why Tomato cannot use it yet?
     
  31. Victek

    Victek Network Guru Member

    Need units to do it, the port for actual models isn't simple as in the past. About WRT1900AC, Openwrt firmware is working very well and you can see in GPL section patches to OpenWRT for the unit.

    The main doubt is, tomato for Marvell Mamba-XP platform could be a wasted effort just for one model ... we hope this platform will be used by other brands, it's simply a cost-price question, not a technical or tomato limitation.

    Another subject is the power consumption on latest models... the smartphone with higher capacities can work with a simple battery 2K7Amp for 24 hours while the router (R7000-WRT1900AC) needs 12V. 3.5Amp - 4.0Amp PSU's or 19V as ASUS. I think ACPI work needs to be done in routers as we see in latest @Eco switches.
     
    Last edited: May 9, 2014
  32. digitalgeek

    digitalgeek Network Guru Member

    Do you have tomato working on a WRT1900AC?
    How difficult is it to upload the firmware?
    I have a spare usb to serial adapter(PL2303), can this be used for the TTL adapter?
    Do all updates need to be performed by TTL?
     
  33. shibby20

    shibby20 Network Guru Member

    There is NO tomato on WRT1900AC.

    Victek maybe we should change thread, because now it makes users confuse
     
  34. digitalgeek

    digitalgeek Network Guru Member

    According to the link(s) it appears as though work has begun, but I couldn't find and actual download that appeared to be usable.

    The OpenWRT guys appear to have something running and stable. how much different is Tomato?
     
  35. lancethepants

    lancethepants Network Guru Member

    Very different, but mostly the router is very different. Porting will be no small feat.
     
  36. Victek

    Victek Network Guru Member

    Correct, just started and no easier work, the main difference... we work in tomato with values stored in nvram instead of configuration files as Mamba or Openwrt, this is one 'small-big' difference.
     
  37. BrainSlayer

    BrainSlayer Network Guru Member

    nope. still just wireless driver binaries, no source
     
  38. lancethepants

    lancethepants Network Guru Member

    Well it's not like tomato has ever played with driver sources anyway. So far it's just stuck with whatever kernel the blobs were built for.
     
  39. Elfew

    Elfew Addicted to LI Member

    Maybe it would be better to focus only on ARM broadcom based devices with Tomato... why? because more platforms=less time to maintain, less builds, less features etc. think about it, everybody should
     
    shibby20 likes this.
  40. jalyst

    jalyst Network Guru Member

    Although that's tempting & completely obvious, the benefits overall & longer-term are far greater if we can have an extra major player in this field. Having only one (broadcom) possibly two (if you include ralink) dominating this field, benefits nobody but the 1-2 SoC OEM's. But certainly Linksys/Marvell must try much harder than they have so far, if they're to garner more support in their corner.
     
  41. jerrm

    jerrm Network Guru Member

    I'm not against the idea of Tomato supporting another platform, just not sure this should be it. I don't know of any other announcements using the same platform as the WRT 1900AC. Admittedly, I have not been staying on top of the issue though - there could be a dozen units in the pipeline using the same chips.

    If I were managing it, I would say full Broadcom ARM support first, then step back and see what the next most popular platform is. I'd have no interest in supporting anything just to develop market diversity or because of marketing buzz. My only interest would be to give Tomato users a wider choice of the hardware that is available and shipping.

    As I said before, Tomato is at least in part successful because it has been focused on one basic platform and does that very well. We don't need to start chasing every new router.

    Ultimately though, it's not my call. We will get whatever appeals to Victek/Shibby/etc. I expect I'll be happy with that.
     
    Monk E. Boy, shibby20 and Elfew like this.
  42. jalyst

    jalyst Network Guru Member

    It depends largely on how much residual support Linksys/Marvell is offering, & what other devices using similar SoCs are coming, remains to be seen.
     
  43. Netwet

    Netwet Reformed Router Member

    Any status update on this? There is no progress on the OpenWRT side. Not a single patch for the WRT has been added to their svn.

    Now that the new Asus AC3200 has been announced people probably wonder if the WRT 1900AC is a dead horse.

    It would be cool if tomato devs could shed some light on their plans. Support, no support, support in 6 months?
     
    jalyst likes this.
  44. roadkill

    roadkill Super Moderator Staff Member Member

    We currently cannot give any estimate about this issue, however what I can tell you is that we are pursuing this platform and we'll have Tomato running on this platform and the recent ASUS development will only hasten things ;)
     
    kthaddock and jalyst like this.
  45. Netwet

    Netwet Reformed Router Member

    No estimation is really bad. 4 weeks passed and you have no clue how long it might take?
    I think a professional dev should be able to give a rough estimation on how long this takes.
    No one asks for a detailed roadmap.

    Saying we will eventually support this unit is bullshit, same bullshit Belkin says about OpenWRT support.

    You see lots of reviews on amazon that claim, soon you will be able to flash an opensource firmware.
    What is soon? 4 weeks, 6 month, 2 years?
    A lot of potential customers might believe it and fall for it. Although they have totally screwed.

    Right now I'm really happy, that I returned the unit after seeing how crippled the Linksys firmware is.
     
  46. roadkill

    roadkill Super Moderator Staff Member Member

    I don't appreciate your attitude.. you understand that all of us are volunteers and none of us owe you anything right??
    people like you are the reason you don't get any reply in forums when you ask questions ;)

    Personally I'd like to run Tomato on my unit as soon as I can.. I'll do everything in my power for other people could do the same.
     
    Siff, jed_99, Victek and 12 others like this.
  47. Elfew

    Elfew Addicted to LI Member

    Have you donated Netwet to devs? Do it and maybe build be there sooner :)
     
    Monk E. Boy, Siff, jed_99 and 2 others like this.
  48. RMerlin

    RMerlin Network Guru Member

    Belkin is the one who screwed up there, not the opensource community. You are venting on the wrong target.

    For starter, nobody can give any ETA at this point because after waiting for nearly two months, Belkin still hasn't delivered the promised source code for the wireless driver. That's one major roadblock there before any dev can provide any ETA on their end.
     
    Monk E. Boy, Siff, TyShawn and 5 others like this.
  49. Netwet

    Netwet Reformed Router Member

    I think you guys don't get it. I'm not demanding support for this unit.

    What I demand though is, that you pull down your pants and tell any one that you can't support it, at least not in the near future.

    Instead you help Belkin screwing users. Just be honest, don't promise anything you can't deliver.
     
  50. jalyst

    jalyst Network Guru Member

    You're pretty clueless/naive, what do you know about the internal machinations of 2 co's & how things are developing, nothing really.

    Belkin/Marvel have handled the whole thing badly*, but clearly you don't know the entire progression of events, else you wouldn't be a whiny bitch. Why? Because it hasn't evolved as simplistically as your understanding of the situation.

    Because you're a bit simple lets keep things simple:
    Some final pieces to the puzzle are still missing, once (if) they're not, everything will be clearer & momentum can accelerate.


    *it's unclear who holds most blame, but based on what we know (& only that), most blame is likely to lay with Belkin
     
    Last edited: Jun 3, 2014
  51. jalyst

    jalyst Network Guru Member

    And before you get attracted like a moth to the flame by this device, you'd be wise to read/understand this, & the 2 main RT-AC3200 threads @SNB.
     
    Last edited: Jun 3, 2014
  52. roadkill

    roadkill Super Moderator Staff Member Member

    This router will run Tomato, We cannot give an ETA so I'll have no more discussions about it.

    as your remarks seems to be counter productive and offensive I'm asking you to shut up because you have no idea what we are willing to do in order to run Tomato on this hardware, so shut up dear and wait patiently :D trust me Tomato will run on this platform in the shortest time possible...
     
  53. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    Play nice guys, or Toxic will send lightning bolts from Mount Olympus and fry you.

    Deep breath @roadkill, 99.9% of Tomato users understand the hard work you guys put into this project. If there were a beer version of PayPal I'd send you one right now! ;-)
     
    Siff likes this.
  54. MarkDe

    MarkDe Connected Client Member

    Netwet, might I suggest a good quality Vitamin B complex supplement, it may assist in keeping your stress levels down and help you be more respectful. As a long time Tomato user, I want to thank the Tomato developers for their hard work. I bought a WRT1900AC the day it went on the shelves, even right out of the box it is the best router I have ever used. My work laptop connects to the 5GHZ at 867mb. I am dying to run Tomato on it so I can tweak it even more, but will respectfully wait.

    To the developers:

    Anyone with a bit of an IQ understands it takes time, the unrefined negative comments of a few, certainly do not represent the views of thousands of appreciative users. Thanks in advance for all your hard work.....AGAIN !
     
    Elfew and Ignas like this.
  55. wit100

    wit100 Networkin' Nut Member

    I am a fan of Tomato. First of all, I want to thank all Tomato developers. I realize you volunteer a lot of your time and expertise to work on it. I appreciate it and am very grateful.

    While as a general rule, I don't like to get into an online forum dispute, I like to say a few words here about what Netwet said.

    Netwet, I don't care what you are demanding. Tomato developers are volunteers. They offer up their time for free and make things better for everyone. "Demanding" anything when they have their day jobs and work on Tomato on a voluntary basis is rude, inconsiderate, and downright offensive.

    Do you realize the Tomato developers can only work on it after they finish their day job, take care of their families, and a ton of other things?

    Asking questions, it seems to me, is very reasonable, but even that, is only reasonable AFTER you have tried hard to look for answers and cannot find them.

    Demanding? Utterly offensive. It is not their duty or job to do anything (even answer a question) for you.

    Finally, I just want to say thank you again to all the people who work on Tomato. Love it!
     
    Last edited: Jun 5, 2014
    Siff, Toastman, Toxic and 5 others like this.
  56. FattysGoneWild

    FattysGoneWild LI Guru Member

    Well this seems appropriate atm. :p

    [​IMG]
     
  57. Victek

    Victek Network Guru Member

    I think it's the wrong place to blame against manufacturers or any router model, simply we like Tomato and we enjoy to see the firmware running in powerfull devices also, WRT1900AC it's one of these powerfull platform and we think Tomato can work, it's a difficult porting but there is no doubt for me that Tomato will run in the unit, ETA? don't know, there is life out of Tomato and this is the reason why all of you saw new models running Tomato in latest months. Let flow ... it will run ;)
     
    MarkDe likes this.
  58. Seal

    Seal Network Guru Member

    keep-calm-and-eat-humble-pie.png
     
    Toxic, MarkDe and Elfew like this.
  59. digitalgeek

    digitalgeek Network Guru Member

    do you have an early beta/alpha build, I am currently running openwrt with luci... It is definitely not tomato.
    I am willing to work with you to test the firmware, but I do not have the setup to compile myself
     
  60. Victek

    Victek Network Guru Member

    No, I don't have anything that can be considered as usable, we still wait some answers from Belkin guys.
     
    Kortez and jalyst like this.
  61. Hardrock

    Hardrock Reformed Router Member

    I've been mucking about with the BB openwrt build but to be honest guys nothing has moved fast with open source firmware development on this product for weeks. Purchased this product thinking it supported tomato or openwrt. Hanging on for your release of tomato Victek or Shibby. Could you guys do a work around for the lack of wireless driver source code?
     
  62. roadkill

    roadkill Super Moderator Staff Member Member

    we plan to use the binary module it would work as it does for the original firmware
     
  63. jalyst

    jalyst Network Guru Member

    Pretty sad how they've now gone fully closed for the entire wifi core, there def. was an opening for a while that they wouldn't (or would at least make some concessions), now it's going to look like they were being deceptive all along, even if they weren't.
     
  64. roadkill

    roadkill Super Moderator Staff Member Member

    we have no problem using the binary modules it's what we do for Broadcom based platforms and it works fine...
     
  65. jalyst

    jalyst Network Guru Member

  66. roadkill

    roadkill Super Moderator Staff Member Member

    as I previously commented on this, we are willing to go into great lengths to support this model.
     
  67. jalyst

    jalyst Network Guru Member

    I meant DD-WRT don't use binary for Broadcom*, & they seem to be (generally) not happy with that approach, don't blame them either.

    Like you they'll have to make significant compromises for the 1900AC, it's left them with lukewarm interest, but apparently they're still going to pursue it, albeit w/a lower priority.

    But as the expression goes; "to each his own"...


    *or so they claim in the thread I ref'd, & that's been my understanding too
     
  68. mstombs

    mstombs Network Guru Member

    To use the binary kernel module blob you have to use the same Linux kernel version, which is a major issue for OpenWRT who like to track the latest. dd-wrt do compile their own wireless drivers for Broadcom, they have the relevant development sdk, probably via Buffalo, which allows them to identify/fix bugs and make kernel changes - it also has the effect of making their drivers no use to anyone else (for example Tomato)! dd-wrt also support Atheros, X86 etc, so you can understand that they have no desire to go back to more restrictive platform.
     
  69. roadkill

    roadkill Super Moderator Staff Member Member

    I'm not questioning any other project methods, just explaining ours ;)
     
  70. jalyst

    jalyst Network Guru Member

    Exactly.

    Yup.

    Well, that depends.

    True.
     
  71. jalyst

    jalyst Network Guru Member

    Cool, looks like I'll unsubscribe from here onwards though.
    For me personally it's getting too hard to justify following 1900AC developments.
    However I do wish you luck!!!
     
  72. MarkDe

    MarkDe Connected Client Member

    .
     
    Last edited: Jul 11, 2014
  73. Hardrock

    Hardrock Reformed Router Member

    Anything new to report guys? This thread as gone awfully quiet :)
     
  74. FattysGoneWild

    FattysGoneWild LI Guru Member

    Not at this point. This router is a complete let down and a mess. Nothing but problems with it if you read over on the Linksys forums. Belkin/Linksys is plain damn stupid. And their PR department should be fired. They could have had a massive hit on their hands. But, nope. They screwed it all up. Idiots. When you look at the stock firmware for this thing. It is completely bare bones minimum. And even then. They still can't get it together with their own firmware.
     
  75. Hardrock

    Hardrock Reformed Router Member

    It is a mess agreed!

    @ Shibby if you read this... What you did with the Tomato E4200 firmware is just magic IMO! Do you think you will be able to re-create this firmware for the WRT1900AC in the near future?
     
  76. MarkDe

    MarkDe Connected Client Member

  77. FattysGoneWild

    FattysGoneWild LI Guru Member

    "We received the official open source wireless driver this week."

    That is BIG news!
     
    MarkDe likes this.
  78. quiron

    quiron Network Newbie Member

    :) this means that there will be a version of tomato for WRT1900AC?
     
  79. Hardrock

    Hardrock Reformed Router Member

    It's all kicking off now over the openwrt forum. Quite a few people questioning how they would go about getting a refund!
    I'm kinda waiting for a tomato release before I decide if refund is the way to go..
    Any realistic view of a release soon guys or should we just give up?
     
  80. mstombs

    mstombs Network Guru Member

    As above OpenWRT compilable wireless drivers not important for Tomato. Finding alternatives to the Broadcom specific functions currently used, such as nvram kernel modules, moving from one specific Broadcom tweaked Linux kernel to a different Marvell one and sorting out equivalents to Broadcom specific wireless and switch configuration likely to be bigger issues.

    It's a big job, it will be done when it is done!
     
  81. MarkDe

    MarkDe Connected Client Member

     
  82. MarkDe

    MarkDe Connected Client Member

    Thank you very much for the update, it is great to know it is being worked on. I can wait, just needed to know it was still on the table. Tx !
     
  83. LucasMoon

    LucasMoon Network Guru Member

    Just bought this unit yesterday. I hope to see Tomato firmware on it. :)
     
  84. roadkill

    roadkill Super Moderator Staff Member Member

    Thread was renamed to avoid confusion
     
  85. MarkDe

    MarkDe Connected Client Member

  86. FattysGoneWild

    FattysGoneWild LI Guru Member

    Its dead in the water. They cant even get OpenWrt running on it. Belkin/Linksys has back tracked. And if you contact them directly complaining about not being able to use 3rd party firmware. They are giving refunds on a case by case bases no matter how long you have owned it.
     
  87. mstombs

    mstombs Network Guru Member

    Anyone know where the returns are being sold off cheap? Every router hacker should have one for nostalgia...
     
  88. LucasMoon

    LucasMoon Network Guru Member

    well hopefully someone will figure out. Right now got to say this router run very well. Yes of course wish there was more options...dont understand why they did not made 2 options basic config for basic users and advanced config for guys like us. MEH....cant have everything :) But i like this router...works very well.
     
  89. roadkill

    roadkill Super Moderator Staff Member Member

    I flashed OpenWRT on it and it was fine.. Wireless worked crappy with the binary modules not all modes are supported but other than that it was ok
     
  90. LucasMoon

    LucasMoon Network Guru Member

    going to take time....just hope they want quit on it. It would be a shame. But I got to admit i really like the interface of linksys. Very well done...but again lacks advanced settings. Some people not happy and returning the product .....i dont plan doing that. Working great and hopefully it wont be a flop on where Linksys stop supporting in firmwares updates.
     
  91. Netwet

    Netwet Reformed Router Member

    Can't you tell, that they already did? Complete silence now. Thread renamed, in order to cover up their failure.
     
  92. Grimson

    Grimson Networkin' Nut Member

    If you think you can do better/faster have a go at it, tomato is open source after all.
     
    JoeDirte and Monk E. Boy like this.
  93. roadkill

    roadkill Super Moderator Staff Member Member

    thread was renamed to avoid user confusion as this is a rather large work to add additional platforms other than Broadcom and requires some additional information which is not currently available, no cover up intended.
     
    Monk E. Boy, LucasMoon and MarkDe like this.
  94. MarkDe

    MarkDe Connected Client Member

    LucasMoon likes this.
  95. RMerlin

    RMerlin Network Guru Member

    Isn't that the proprietary source code that was accidentally leaked back in April? If so, then I would expect lawyers to get involved and start requesting that this code be removed.
     
  96. LucasMoon

    LucasMoon Network Guru Member

    what wrong with that code? bad? or it is the good reliable code that Belkin did not wanted to share to the open source group?
     
  97. MarkDe

    MarkDe Connected Client Member

    this was posted at this link: https://forum.openwrt.org/viewtopic.php?pid=241243#p241243

    2014-07-24 03:06:43

    greymattr wrote:
    I wanted to update everyone about the release of the wireless driver for the WRT1900AC.

    There were potential issues with some of the wording in the source, and we are working to get that corrected so there will not be any legal issues.

    Once these strictly cosmetic changes are made it will allow OpenWrt developers to recompile the wireless driver as updates are made to the kernel.

    Thank you for your patience and support through this process.
    I can not speak officially for Belkin/Linksys, but personally, I have used OpenWrt for many years, and I look forward to working with the OpenWrt community in the future on projects if possible.

    keep up the good work.
     
    LucasMoon likes this.
  98. RMerlin

    RMerlin Network Guru Member

    And what followed that initial announcement was that the driver would be provided in hybrid form, with part of it still closed source, and provided as a precompiled library. Which was the point where the OpenWRT devs pretty much said "screw that".
     
  99. MarkDe

    MarkDe Connected Client Member

    That post was on page 25 of the forum dated July 24, on page 29 dated August 24, it appears they're compiling.

    i'm digging my friend. I am one of those saps who bought this router out of the gate based on the fact it was "supposed" to be open source. I am not a developer, just an enthusiast for trying to get the most out of my home network, kids gaming(ps4's & xbox1's), and my wife's shopping(lol....). At this point, I am just wishing i had stayed with my Asus N66U, and just waited. I am still hanging on to the hope of seeing Tomato on the WRT1900AC.
     
    Last edited: Aug 26, 2014
  100. MarkDe

    MarkDe Connected Client Member

    For anyone who wants to have a custom software, I advise strongly to hit this link and download the latest OpenWrt by Chadster. It flashes from the browser, loads and runs beautifully. My WRT1900AC is no longer a disappointment, but rather in my opinion, a GREAT investment!!

    https://github.com/Chadster766/McWRT/releases
     
    Monk E. Boy and LucasMoon like this.

Share This Page