Next
Previous
Contents
You are still with us, so you have a GGI kernel running and you are prepared
for the next step. The new kernel has hooks to register input and display
drivers that are loaded as modules. You will have to create the drivers first.
To do this, please do the following steps:
- Look at your graphics card and find out the hardware that's on it.
Especially you need to know:
- chipset manufacturer, chipset name/trademark/ID
- ramdac manufacturer, chip name/trademark/ID
- clock chip type and name/manufacturer/ID
- monitor type and parameters
If you don't know much about your card, but know it is a VGA compatible
device, try VGA settings. Use these too if your card is not
supported in "native" mode.
- Change over to the ggi-v.e.r/driver directory.
- If you did not patch the kernel from this source tree,
echo /where/the/linuxsrc/is > .kernelsrc
e.g.
echo /usr/src/linux-ggi > .kernelsrc
(This is normally done while patching the kernel.)
- Run "make".
This will run the configure script first and let you do the
configuration by hand or automatically. You can also create a
config file with a normal editor, we suggest you create a
normal VGA config first and modify this one. See the README.CONFIG
file for more details.
After it, make will build dependencies and compile all the drivers
needed to create a driver as stated in ggi-v.e.r/driver/.config.
From now on, running "make" will rebuild this driver. If you want
to change the configuration, run "make config; make clean; make"
- Run "make input"
This will compile all the configured input drivers.
- Run (cd ../util ; make setmouse)
This will compile a setup utility foe the mouse which is
used by the
insert
script.
- Insmod the new drivers. Normally
insert
does the job.
The new drivers will be located in the "modules" directory.
The toplevel "util" directory includes several programs to help
you tweak your mouse, mode settings, etc...
Please refer also to the corresponding files in the driver/.../.../
directories for possible options, known problems and other hints.
NOTE: With the 2.1 kernels, you need to upgrade your modutils to at least
version 2.1.34, otherwise module loading will not work.
Once the driver(s) are inserted, your system is - from the kernel side -
prepared so you can run the library and demos. Note that you will have to
insert the modules again after each boot. So a script to do this is not
a bad idea.
Next
Previous
Contents