yes, got it. Thanks. I replaced it by "main" so that the release to a local GIT tree becomes simpler (different project location than the one's which come from Google)
Also, has this been published in the Googe's GIT ? regards, Pavan On Tue, Nov 10, 2009 at 3:39 PM, Chih-Wei <cwhu...@linux.org.tw> wrote: > Yes, you can use it. The code is Apache License 2.0. > > It is a utility of the toolbox, you don't need to change hotplug_main. > Just make the android tree and it will be compiled as a part of > toolbox, > and the symlinks /system/bin/hotplug and /sbin/hotplug will be > created. > > On 11月9日, 下午5時18分, pavan savoy <pavan.sa...@gmail.com> wrote: >> Hi Chih-Wei, >> Would it be ok, for me to make use of the same code, and release it to >> my internal GIT. >> What should I be licensing it as ? GPL ? >> >> regards, >> Pavan >> >> >> >> On Tue, Nov 3, 2009 at 3:20 PM, pavan savoy <pavan.sa...@gmail.com> wrote: >> > Hi, >> >> > Thanks for the tool. But how do I use it ? >> > I am working on a normal android FS and don't have a toolbox/ >> > directory and no method to call hotplug_main. >> >> > I did build the hotplug executable and change the hotplug_main to >> > main, but somehow running "hotplug firmware" doesn't seem to be >> > working out. >> > So my doubt is the env variables like ACTION, FIRMWARE being set or >> > not, and didn't see them in the hotplug.log (created by you either). >> >> > Note: >> > Hard-coding what is required, i.e from the cmd line if I perform a >> > $ echo 1 > /sys/.../loading >> > $ echo ..firmware_file. > /sys/.../data >> > $ echo 0 > /sys/.../loading >> > does seem to be working !! > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting -- --Pavan Savoy -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
