First of all thanks for referring me to a good link. This thanks goes to Sven Neumann especially.
My New problems I tried using the Divine, but I could not use it because, I don't know how to use/install it. So What I did was, I edited the make files (.am, .in etc) and added divine as another driver like linus_input, keyboard, ps2 etc. After adding the driver, I compiled the directfb again (make clean, make etc). I found that the divine library was successfully compiled without any problem. Now, what should I do, How will inform the application to use divine driver. How will make directfb to load divine driver like it is loading the keyboard and mouse driver. When I went through the examples, I found that the application is explicitly calling a function to load a specific driver, If I want to load divine driver, how will I do that, because I don't have the DID value for this. Can I add to the header file ?. One more help if possible, When I checkedout the CVS version of Divine, I am not getting the make files, I found that the repository itself is not having, When read the readme, I found that make file will be only available on release version. But I don't know how to get the release version for Divine. I think Divine is yet to be released. In which case, can you tell me how to generate the make file, I tried using autogen.sh, it is giving the following error whenever I run it. # ./autogen.sh ./autogen.sh : File not found <-------- Error displayed in the console (This is a comment and typed by me) Is it possible to test the divine driver with out writing a sample directfb application ? In which case, I can test the driver independent of the application. Why I am asking this is once I run the directfb application, I cannot switch consoles, so I will not be able to run the example application provided with Divine (Of course I can run it through a serial console, but ..) Any idea, suggestion and advice is useful RD -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject.
