Thanks.
I had to:
1. Compile my kernel with the input device enabled
2. Compile DirectFB with --with-inputdrivers=linuxinput
3. Create device in dev folder:
sh-2.05b# mknod /dev/input/mice c 13 63
sh-2.05b# mknod /dev/input/event0 c 13 64
sh-2.05b# mknod /dev/input/event1 c 13 65
sh-2.05b# mknod /dev/input/event2 c 13 66
sh-2.05b# mknod /dev/input/event3 c 13 67
This is the actual output of dfbinfo:
=======================| DirectFB 1.0.0 |=======================
(c) 2001-2007 The DirectFB Organization (directfb.org)
(c) 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2007-06-04 10:51)
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 925)...
(*) Direct/Thread: Running 'Linux Input' (INPUT, 926)...
(*) DirectFB/Input: Cirrus EP93xx 8x8 keypad matrix (1) 0.1 (directfb.org)
(*) Direct/Thread: Running 'Linux Input' (INPUT, 927)...
(*) DirectFB/Input: Cirrus Logic EP93xx Touchscreen (2) 0.1 (directfb.org )
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 928)...
(*) DirectFB/Input: Keyboard 0.9 (directfb.org)
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 929)...
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
Screen (00) FBDev Primary Screen (primary screen)
Caps: VSYNC POWER_MANAGEMENT
Layer (00) FBDev Primary Layer (primary layer)
Type: GRAPHICS
Caps: SURFACE BRIGHTNESS CONTRAST SATURATION
Input (11) Cirrus Logic EP93xx Touchscreen
Type:
Caps: AXES
Max. Axis: 1
Input (00) Keyboard (primary keyboard)
Type: KEYBOARD
Caps: KEYS
Input (01) IMPS/2 Mouse (primary mouse)
Type: MOUSE
Caps: AXES BUTTONS
Max. Axis: 2
Max. Button: 2
The mouse input work fine.
Not so good is the drawing of arrow. In all examples the arrow is not
correctly re-draw when I move the mouse.
any suggestion?
Giulio
2007/6/1, Ville Syrjälä <[EMAIL PROTECTED]>:
On Fri, Jun 01, 2007 at 03:12:16PM +0200, Giulio Pollini wrote:
> Hello,
> I'm working on embedded system.
> I have a usb mouse connect it.
>
> On start-up linux print:
> ...
> input: Logitech USB Mouse as /class/input/input0
> input: USB HID v1.10 Mouse [Logitech USB Mouse] on usb-ep93xx-1
> ...
>
>
>
> but when I run dbinfo utility...
>
>
> *sh-2.05b# ./dfbinfo*
>
> =======================| DirectFB 1.0.0 |=======================
> (c) 2001-2007 The DirectFB Organization (directfb.org)
> (c) 2000-2004 Convergence (integrated media) GmbH
> ------------------------------------------------------------
>
> (*) DirectFB/Core: Single Application Core. (2007-05-30 09:29)
> (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 1239)...
> (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 1240)...
> (*) DirectFB/Input: Keyboard 0.9 (directfb.org)
> (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org)
> (*) DirectFB/Core/WM: Default 0.3 (directfb.org)
>
>
> Screen (00) FBDev Primary Screen (primary screen)
> Caps: VSYNC POWER_MANAGEMENT
>
> Layer (00) FBDev Primary Layer (primary layer)
> Type: GRAPHICS
> Caps: SURFACE BRIGHTNESS CONTRAST SATURATION
>
>
> Input (00) Keyboard (primary keyboard)
> Type: KEYBOARD
> Caps: KEYS
>
> Where I'm wrong?
If you want to use the psmouse driver make sure you have compiled your
kernel with CONFIG_INPUT_MOUSEDEV. After that make sure you have the
/dev/input/mice device node.
My recommendation is to remove both keyboard and psmouse drivers and use
linuxinput instead. In that case you must compile your kernel with
CONFIG_INPUT_EVDEV. The device nodes should be named like
/dev/input/event0, /dev/input/event1, etc.
--
Ville Syrjälä
[EMAIL PROTECTED]
http://www.sci.fi/~syrjala/
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
