On Wed, 02 May 2001, "Tasnim Ahmed" wrote: > > > > > > Even when this is done it would be good to have this silkscreen keyboard > as a compile-time option. > > Do you have a sourceforge login? If so, I can add you to the project so > you can add this stuff to the CVS tree. > > > > So I would complete its dynamic aspect i.e. keyboard map from file on the > weekend and then send you. > Just made an account "tasnim" on source forge as my nick "debugger" was > ofcourse already taken :( > before adding anything to CVS I'll try to make sure it does remain as a > compile option with #ifdef(s) > anyways as somebody mentioned "good that C in CVS stands for concurrent" ;) > can rollback if its the wrong thing. Okay. Sounds like this would make a great compile time option for the r3912 touchscreen driver. I just added you to the sourceforge project > > > > > I tried pppd, but it complains that ppp support isn't in the kernel even > when it is. Oh well. If you want to try it too, just get the standard pppd > source distrobution and change the 'gcc' in the makefile. > > > > > > I think to CVS the new linux-vr kernel, it may have better serial support as > mentioned on the URL I sent later on. And maybe that magically fixes this > pppd problem as well, while breaking some other stuff. CCYAU used to send me > his work but lately he is posting on ucSimm list so I guess VTech got rid of > him I tried the newer linux-vr kernel, but the framebuffer didn't work. Maybe they've fixed this in the few weeks since I've tried it, but there doesn't seem to be much concern for the Helio ar linux-vr any more. The only difference between the pocketlinux kernel and the pico/linux kernel is that I fixed (well, kludged at least) the touchscreen power management. It would be nice to keep all this in CVS so the romdisk is easy for everyone to work on. (Or at least both Tasnim and I :) We could just put everything necessary to build pico/linux ROM image for Helio in one directory, including romdisk binaries, tools, and kernel source. Alternatively, since the kernel's so big, it could go in a separate CVS package. As far as the romdisk goes, I think it's necessary to keep it non-tarred in CVS so it's easy to update individual files. The makefile would need to be run as root; it could make a copy of the CVS directory, chown it to root, and untar a .tar.gz file with the device nodes and such before making the cramfs. I'd like a way to simply check out a picolinux-helio module from CVS, and be able to build and modify the ROM image. I definitely don't want this project falling into the picolinux 'only I know how to compile it' trap. > > > regards, > -debugger Good luck with everything! I should have the virtual keyboard done soon. Still, it sounds like your not-so-virtual keyboard could be a better option for the helio. It would be a great to offer both! -- To the systems programmer, users and applications server only to provide a test load. _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/pgui-devel
