Hi,
John McLean <[EMAIL PROTECTED]> writes:
> I'm trying to get directfb running on our ARM based board. (www.techsol.ca)
>
> The framebuffer and keyboard work fine with the console and
> qtembedded. When running directfb demo programs I get the following.
>
> ============================================
> # ./df_particle
> (*) parsing config file '/etc/directfbrc'.
>
> ---------------------- DirectFB v0.9.10 ---------------------
> (c)2000-2002 convergence integrated media GmbH
> -----------------------------------------------------------
>
> (*) Single Application Core.
> (!) DirectFB/Keyboard: TIOCNOTTY failed!
> --> Not a typewriter
> (!) DirectFB/Keyboard: TIOCSCTTY failed!
> --> Operation not permitted
these two messages are normal. Well, they indicate that our VT
handling is not as optimal as we'd like it to be, but you'll get the
same messages on a standard desktop PC.
> (*) DirectFB/GraphicsDevice: Generic Software Rasterizer 0.5 (convergence
> integ)
what I'm missing here is a line like the following:
(*) DirectFB/InputDevice: Keyboard 0.9 (convergence integrated media GmbH)
which would indicate that the Keyboard driver was loaded. Since the
keyboard driver doesn't do any probing, it should always be loaded. If
it can't put the keyboard into raw mode, it will complain, but we
should see a message indicating that this is the case.
>(#) DirectFBError [CreateInputDevice for keyboard failed]: ID not found!
well, that's the application that exits becaused it can't find a keyboard.
My guess is that the keyboard driver is not installed. Could you check
if ${prefix}/lib/directfb/inputdrivers/libdirectfb_keyboard.so is
available ?
Salut, Sven
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with
"unsubscribe directfb-users" as subject.
