About transplant the ipk to Gargoyle

[fox85]

Hi all.
I'm kinder new of linux. And here is my story , I just got a tl-wr720n Chinese version , and here is the wiki details link for you guys http://wiki.openwrt.org/toh/tp-link/tl-wr720n

And here is the product introduction link from tplink
http://translate.google.com.hk/translat ... ntro%23tag

Yes, the product has a usb 2.0 port , this port can be used to file sharing or charging phones ,pads etc , and the port can provide power supply up to 5V/2A .

The hardware specification is same as tl-wr703n , so I just modified
some source codes that can support this model.

I have flashed openwrt or Gargoyle to this product , main function works fine, except the usb port. If I plug ipad to usb port for charing , the ipad shows "Not Charging". Actually the usb port just provides power supply 5V/500ma .

With the stock firmware, if I plug ipad to usb port for charging, the port can provide 5V/2A, and then ipad shows "Charing" . I have tested both.

I found another model TL-WR710N ,
here is the link
http://www.tp-link.com/en/products/deta ... R710N#over
It's a product from tplink too ,the hardware specification is very similar with tl-wr720n Chinese version , and the webpage mentions the usb port power supply up to 5V/1A.
So I downloaded the GPL code of TL-WR710N to find out how they implement this funtion, I saw they use ipad_charge.

ipad_charge is a USB charging control utility used to enable/disable charging of an Apple device connected to USB port. And here is the link
https://github.com/mkorenkov/ipad_charge

So I'm pretty sure tplink uses same trick with TL-WR720N Chinese Version.

Now I'm wondering if I could transplant this program to Gargoyle.
I heard Gargoyle has a custom kernel different from Openwrt , so do I need the SDK of Gargoyle to transplant the program ?

Thanks all!

[BashfulBladder]

I've moved this topic because the scope is larger than a simple ipad charging question.

1st, Gargoyle has a modified kernel, not an entirely different one. I haven't gotten into the details, but it could just be some modules that are different - for bandwidth monitoring & such. Gargoyle follows OpenWrt AA codebase very closely.

2nd, Gargoyle does not have an SDK, you must compile. Compile soup-to-nuts: compiler, buildroot, kernel, every tool on the router.

3rd, for both OpenWrt & Gargoyle to be able to compile your program, you need a makefile wrapper around the ipad_charge program. You can use the dsiktype or dosfstools as examples.

4th, you would need to somehow integrate the ipad_charge into either the Gargoyle scripts or create a new webpage or add a section to a page.

5th, you build Gargoyle using its build scripts. See http://www.gargoyle-router.com/wiki/dok ... umentation