On Wed, 17 Oct 2001, Ulhas Samant wrote: > I shall comment the said line and try to recompile. You have mentioned > of one more fix in fbdev g400 driver. (Can you please mention the > appropriate file if it's relevant to us ?).
It will not apply to you, as it is a sub0driver of the linux-fbdev target. At least, unless you port linux-fbdev and the mga driver to sun's raw framebuffer device (which assumes sun's raw framebuffer advice exposes the accelerator registers.) > By the way, Chris had mentioned that the tasks list (TODO) for LibGII was > with you and you were updating it. Can you pl, send it across ? I have just updated it in CVS -- here is how it now reads: - Get rid of the AC_TRY_RUN warning when running autogen.sh Note: This is related to endian detection done by a compiled and executed program AC_C_BIGENDIAN. It might be better to create a catalog of endianess that is indexed by $host_cpu set by AC_CANONICAL_HOST. - Implement a per-device key/value hash (which is sent across the communications channel, encapsulated in events, such that it is available via the gii_input handle even when using a remote device e.g. via filter-tcp) This will be general purpose, but in the short term, the reason for it is to give device information strings which are longer than what will fit in a gii_event structure. This hash is stateful, and must be updated when inputs are opened/closed or devices are added/removed from an input. See 06/2001 thread on ml entitled "device info" - Document using filters in the docbook. - Write a device driver/filter developers guide. - (wishlist) refactor the keytrans/mouse filters, make them configurable both by *optional* configuration file and via some sort of runtime control structure (using the abovementioned hash ?). Add joystick axis sensitivity curve. Write a neat GGI app that allows tuning keyboard/mouse/joystick. - Check that all drivers are giving a device name, not just name of driver. - Port a lot of programs to use LibGII as their event loop. This is the best sort of demo. GPM, X, Wine are obvious targets. ------------------------------------------ Long-term plan ------------------------------------------ - Update our userspace drivers from other sources (GPM, linux-console) thus porting the code from these projects to non-Linux platforms.
