Browsing through the NAND using enexfi on the GP2X, I found many things which will interest any developer. A lot of devs are saying that the F-200 is not developer friendly as it lacks the networking tools, wrong!
Sure, the F-200 does not "graphically" display the networking functions, as normal users do not need this in their settings, but rather a nice clean settings page. Why confuse a new GP2X user with tons of garbage they would never use in the settings.
The F-200 firmware contains everything that the F-100 has in it's Linux root file system, even all the networking kernel modules are left for people to work with. The samba server, the web server, and even the telnet server are all left in tact on the F-200's root file system. I have yet to test it out, however I will see if I can generate some nice scripts for people interested on using these functions on their new F-200 device. I'd sure like to get the telnet working again.
Does anyone know what parameters the ethernet usb gadget requires? As all I need to do on my Palm TX Linux, is load g_ether and use ifconfig to set-up the interface, I would imagine it is the same on the GP2X. However, due to hardware configurations, it may need some extra parameters.
I am going to see if I am able to directly copy gp2xmenu from a v3.0.0 firmware onto my SD card of my F-200 and run it, I want to see if it will let me run it, and even configure the interface and daemons from there. If it does, then we are in business for easy development on the F-200. I sure of h*ll want to copy over mplayer from an v3.0.0 firmware to my F-200. Has anyone tried copying mplayer from a v3.0.0 firmware onto their F-200 yet?
Does firmware v3.0.0 use Linux kernel 2.4.25 as firmware v4.0.0 on the F-200 uses? If so, then we can move over kernel modules easily, in case we are missing some additional networking modules.
Stay tuned to this thread for more finding and some shell scripts.
Sure, the F-200 does not "graphically" display the networking functions, as normal users do not need this in their settings, but rather a nice clean settings page. Why confuse a new GP2X user with tons of garbage they would never use in the settings.
The F-200 firmware contains everything that the F-100 has in it's Linux root file system, even all the networking kernel modules are left for people to work with. The samba server, the web server, and even the telnet server are all left in tact on the F-200's root file system. I have yet to test it out, however I will see if I can generate some nice scripts for people interested on using these functions on their new F-200 device. I'd sure like to get the telnet working again.
Does anyone know what parameters the ethernet usb gadget requires? As all I need to do on my Palm TX Linux, is load g_ether and use ifconfig to set-up the interface, I would imagine it is the same on the GP2X. However, due to hardware configurations, it may need some extra parameters.
I am going to see if I am able to directly copy gp2xmenu from a v3.0.0 firmware onto my SD card of my F-200 and run it, I want to see if it will let me run it, and even configure the interface and daemons from there. If it does, then we are in business for easy development on the F-200. I sure of h*ll want to copy over mplayer from an v3.0.0 firmware to my F-200. Has anyone tried copying mplayer from a v3.0.0 firmware onto their F-200 yet?
Does firmware v3.0.0 use Linux kernel 2.4.25 as firmware v4.0.0 on the F-200 uses? If so, then we can move over kernel modules easily, in case we are missing some additional networking modules.
Stay tuned to this thread for more finding and some shell scripts.