Re: [OpenWrt-Devel] Image command line hack question
password is 123, sorry On Fri, Sep 2, 2011 at 7:06 PM, jason duhamell ps2chi...@gmail.com wrote: As promised, here is the official realtek bsp with documentation. http://d01.megashares.com/dl/abc0f5c/rtl819x-sdk-v2%5B1%5D.2.tar.gz Jason On Sat, Aug 27, 2011 at 9:51 PM, Florian Fainelli flor...@openwrt.orgwrote: Hello, On Saturday 27 August 2011 15:14:51 Andrew wrote: Hello again, I looked through the patches, and think of rebasing my current work on top of them. Still, one question persists: Is your work on RT856X abandoned? Why wasn't it included in the OpenWRT trunk. At the time it was written, it was not tested on enough hardware to be included. I'll try to forward-port your RT856X work, some things look similar. But since I do not have any RT865X board, it might be buggy. I have some RTL865x boards that I can test on. And what conserns those realtek's imgtools (cvimg and mgbin), will it be OK if I make a script that either downloads the official GPL sources from, say TRENDnet's site and rips the reuired stuff from it (or asks the user to do that manually). (I have a strange feeling it isn't worth the effort asking realtek for license clarification) Since the sourcecode was published, let's just say that we can use the version as-is, but a rewrite by someone else and with proper license would be better. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Image command line hack question
As promised, here is the official realtek bsp with documentation. http://d01.megashares.com/dl/abc0f5c/rtl819x-sdk-v2%5B1%5D.2.tar.gz Jason On Sat, Aug 27, 2011 at 9:51 PM, Florian Fainelli flor...@openwrt.orgwrote: Hello, On Saturday 27 August 2011 15:14:51 Andrew wrote: Hello again, I looked through the patches, and think of rebasing my current work on top of them. Still, one question persists: Is your work on RT856X abandoned? Why wasn't it included in the OpenWRT trunk. At the time it was written, it was not tested on enough hardware to be included. I'll try to forward-port your RT856X work, some things look similar. But since I do not have any RT865X board, it might be buggy. I have some RTL865x boards that I can test on. And what conserns those realtek's imgtools (cvimg and mgbin), will it be OK if I make a script that either downloads the official GPL sources from, say TRENDnet's site and rips the reuired stuff from it (or asks the user to do that manually). (I have a strange feeling it isn't worth the effort asking realtek for license clarification) Since the sourcecode was published, let's just say that we can use the version as-is, but a rewrite by someone else and with proper license would be better. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Image command line hack question
Hello all, I'm currently working on rtl8196 port, and those weird guys from realtek implemented there a different architecture rlx in kernel. Basically, much is borrowed from mips, but small differences here and there are present. I applied openwrt command hack to rlx, however, that didn't work out of the box. To get patch-cmdline actually patch rlx's vmlinux I had to widen the SEARCH_SPACE ( http://invyl.ath.cx/cgit/cgit.cgi/openwrt/commit/?id=38a13e566f179a12803a391ca941cad1f806db08 ). The next thing was, that despite the image gets patched, and I see the correct text hexdump'ing the image, the kernel command line stays the same. Looks like some other place needs to get patched, but I just can't firure where to look. Any ideas? Thanks in advance. I have now fixed the image packing for initial support for different boards, and, hopefully I'll get spi flash uprunning next week. What should the state of the port be, before it's ok to send in the patches to the trunk? :) Regards, Andrew ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Image command line hack question
Hello again, I looked through the patches, and think of rebasing my current work on top of them. Still, one question persists: Is your work on RT856X abandoned? Why wasn't it included in the OpenWRT trunk. I'll try to forward-port your RT856X work, some things look similar. But since I do not have any RT865X board, it might be buggy. And what conserns those realtek's imgtools (cvimg and mgbin), will it be OK if I make a script that either downloads the official GPL sources from, say TRENDnet's site and rips the reuired stuff from it (or asks the user to do that manually). (I have a strange feeling it isn't worth the effort asking realtek for license clarification) Regards, Andrew ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Image command line hack question
Hello, On Saturday 27 August 2011 15:14:51 Andrew wrote: Hello again, I looked through the patches, and think of rebasing my current work on top of them. Still, one question persists: Is your work on RT856X abandoned? Why wasn't it included in the OpenWRT trunk. At the time it was written, it was not tested on enough hardware to be included. I'll try to forward-port your RT856X work, some things look similar. But since I do not have any RT865X board, it might be buggy. I have some RTL865x boards that I can test on. And what conserns those realtek's imgtools (cvimg and mgbin), will it be OK if I make a script that either downloads the official GPL sources from, say TRENDnet's site and rips the reuired stuff from it (or asks the user to do that manually). (I have a strange feeling it isn't worth the effort asking realtek for license clarification) Since the sourcecode was published, let's just say that we can use the version as-is, but a rewrite by someone else and with proper license would be better. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel