2011-12-06 114 views
0

我想在一個ARM系統上嵌入tslib,以便使用觸摸屏設備;我已經成功安裝了它,但不幸的是我無法檢索所有筆記來重新執行它。 x)tslib沒有創建設備

我交叉編譯庫文件,我把它們放到/usr/lib;我創建conf文件/etc/ts.conf和我已經出口了良好的環境變量:

export TSLIB_TSDEVICE="/dev/event2" 
export TSLIB_CONFFILE="/etc/ts.conf" 

這裏是我的問題:tslib的似乎沒有創建事件設備時,我將設備。在這裏是結果* ts_calibrate *:ts_open: No such file or directory

我認爲它試圖打開的/ dev /事件2因爲它沒有被創建tslib的不存在。

任何想法?

感謝

回答

0

你需要自己mknod/dev/event2?你是否積極的讓你的圖書館使設備節點?

1

你有什麼樣的內核+用戶空間?設備文件創建通常是 內核hotplug + udev或mdev的工作。

在任何情況下,tslib不應該創建設備文件。你有兩個選擇:

  • 手動創建的設備,只要你的busybox包含mknod的實用程序:

    mknod event2 c 13 66 
    

    ,其中66次設備號,它應大於事件1次多一個。

  • 推出的mdev -s,看看你的/ dev目錄變化

  • 的內容找出爲什麼沒有檢測出排氣裝置/創建:請郵寄的01​​輸出,並且開機後dmesg

+0

我們有一個基於Debian的特定內核(我們使用Busybox),但是我們修補了很多東西。在/ dev我已經有2個設備,event0和event1;觸摸屏應該是/ dev/event2。檢測到觸摸屏,因爲幀緩衝區庫工作正常。 ;) –

+0

我添加了「usbtouchscreen」模塊,其中包含eGalax驅動程序;現在,dmesg給我:'<6>輸入:eGalax Inc.USB TouchController as /devices/platform/str8100-ehci/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/輸入/輸入2',但我仍然無法看到如何獲得輸入:/ –

+0

嘗試安裝模塊後mdev -s – shodanex

0

其實mknod在我們的工具箱中不可用。推出mdev -s時沒有什麼變化,我已經嘗試過。 :/ 這裏是UNAME結果:Linux MYNAME 2.6.24.4 #3 Fri Dec 2 16:54:41 CET 2011 armv4l unknown(MYNAME只是系統的名字,我取代了它的私密性原因;))

而且dmesg

<6>usb 1-1.3: new high speed USB device using str8100-ehci and address 23 
<6>usb 1-1.3: configuration #1 chosen from 1 choice 
<6>hub 1-1.3:1.0: USB hub found 
<6>hub 1-1.3:1.0: 4 ports detected 
<6>usb 1-1.3.2: new high speed USB device using str8100-ehci and address 24 
<6>usb 1-1.3.2: configuration #1 chosen from 1 choice 
<6>udlfb: DisplayLink AT-7 - serial #200694 
<6>udlfb: vid_17e9&pid_02fc&rev_0104 driver's dlfb_data struct at c1031000 
<6>udlfb: console enable=0 
<6>udlfb: fb_defio enable=0 
<6>udlfb: vendor descriptor length:23 data:23 5f 01 0021 00 04 04 07 00 01 
<4>udlfb: DL chip limited to 1500000 pixel modes 
<4>dlfb_alloc_urb_list 
<4>dlfb_release_urb_work : INIT_DELAYED_WORK dlfb_release_urb_work 
<4>dlfb_release_urb_work : after INIT_DELAYED_WORK 
<4>usb_fill_bulk_urb 
<4>usb_fill_bulk_urb end 
<4>dlfb_release_urb_work : INIT_DELAYED_WORK dlfb_release_urb_work 
<4>dlfb_release_urb_work : after INIT_DELAYED_WORK 
<4>usb_fill_bulk_urb 
<4>usb_fill_bulk_urb end 
<4>dlfb_release_urb_work : INIT_DELAYED_WORK dlfb_release_urb_work 
<4>dlfb_release_urb_work : after INIT_DELAYED_WORK 
<4>usb_fill_bulk_urb 
<4>usb_fill_bulk_urb end 
<4>dlfb_release_urb_work : INIT_DELAYED_WORK dlfb_release_urb_work 
<4>dlfb_release_urb_work : after INIT_DELAYED_WORK 
<4>usb_fill_bulk_urb 
<4>usb_fill_bulk_urb end 
<4>dlb_alloc_urb_list : before sema_init 
<4>dlb_alloc_urb_list : after sema_init 
<5>udlfb: allocated 4 65024 byte urbs 
<4>dlfb_setup_modes 
<4>dlfb_get_edid 
<4>dlfb_is_valid_mode 
<6>udlfb: 800x480 valid mode 
<4>udlfb: Reallocating framebuffer. Addresses will change! 
<4>dlfb_ops_check_var 
<4>dlfb_is_valid_mode 
<6>udlfb: 800x480 valid mode 
<5>udlfb: set_par mode 800x480 
<4>dlfb_set_video_mode 
<4>dlfb_get_urb end 
<4>dlfb_set_vid_cmds 
<4>dlfb_submit_urb 
<4>dlfb_submit_urb : after usb_submit_urb ret=0 
<4>dlfb_set_video_mode end 
<4>dlfb_urb_completion 
<4>up release_urb_work !!! 
<4>dlfb_urb_completion end 
<4>dlfb_handle_damage 
<4>dlfb_get_urb end 
<4>dlfb_submit_urb 
<4>dlfb_submit_urb : after usb_submit_urb ret=0 
<6>udlfb: DisplayLink USB device /dev/fb1 attached. 800x480 resolution. Using 1504K framebuffer memory 
<4>dlfb_urb_completion 
<4>up release_urb_work !!! 
<4>dlfb_urb_completion end 
<6>usb 1-1.3.3: new full speed USB device using str8100-ehci and address 25 
<3>usb 1-1.3.3: device descriptor read/64, error -32 
<3>usb 1-1.3.3: device descriptor read/64, error -32 
<6>usb 1-1.3.3: new full speed USB device using str8100-ehci and address 26 
<3>usb 1-1.3.3: device descriptor read/64, error -32 
<3>usb 1-1.3.3: device descriptor read/64, error -32 
<6>usb 1-1.3.3: new full speed USB device using str8100-ehci and address 27 
<3>usb 1-1.3.3: device not accepting address 27, error -32 
<6>usb 1-1.3.3: new full speed USB device using str8100-ehci and address 28 
<3>usb 1-1.3.3: device not accepting address 28, error -32 
<6>usb 1-1.3: USB disconnect, address 23 
<6>usb 1-1.3.2: USB disconnect, address 24 
<6>udlfb: USB disconnect starting 
<4>dlfb_free_framebuffer_work 
<4>udlfb: fb_info for /dev/fb1 has been freed 
<4>dlfb_free 
<5>udlfb: Waiting for completes and freeing all render urbs 
<4>udlfb: freeing dlfb_data c1031000 
<6>usb 1-1: USB disconnect, address 12 
<6>usb 1-1: new high speed USB device using str8100-ehci and address 29 
<6>usb 1-1: configuration #1 chosen from 1 choice 
<6>hub 1-1:1.0: USB hub found 
<6>hub 1-1:1.0: 4 ports detected 
0

tslib不會創建一個輸入設備;您的觸摸屏的設備驅動程序可以。 tslib使用它,你可以撥打電話ts_read()獲得過濾樣本。有X11和Qt5包裝這樣做。這就是它一直的方式。

tslib版本1.3開始,您可以使用tslib/tools/ts_uinput創建輸入設備以指向您的環境,請參閱tslib's project page

截至目前,如果你想測試這個,有tslib-1.3-rc1