[Armadillo:05117] Re: Armadillo 440 タッチパネルを有効に戻す方法をご存じありませんか
Takenoshita Koyo
email@hidden
2010年 4月 21日 (水) 18:42:48 JST
竹之下です。
> 他のUSBデバイスを抜いて起動し、USB機器を後から挿したところ、タッチパネル
> が動くようになりました。
> ただ、組み込みで使うため、通常はUSB機器は差しっぱなしになります。
> 番号を固定する方法をご教示いただけませんでしょうか。
イベントデバイスの番号が変わると困るのは、起動スクリプトの
/etc/init.d/xfbdevで番号を決め打ちしているからです。
発想を少し変えて、番号が変わっても大丈夫なようにしてみます。
/etc/init.d/xfbdev を以下のものと差し替えると、番号がいくつ
になっても大丈夫だと思います。
==== start /etc/init.d/xfbdev ====
#!/bin/sh
. /etc/init.d/functions
PATH=/bin:/sbin:/usr/bin:/usr/sbin
echo -n "Starting Xfbdev: "
for input_ev in $(find /sys/class/input/event*); do
case $(cat $input_ev/device/name) in
"imx_adc_ts") TS_DEV=$(echo $input_ev | sed -e 's|/sys/class|/dev|');;
"gpio-keys") KEY_DEV=$(echo $input_ev | sed -e 's|/sys/class|/dev|');;
esac
done
if [ -z "$TS_DEV" -o -z "$KEY_DEV" ]; then
false
check_status
else
/usr/bin/Xfbdev -s 0 -mouse tslib,,device=$TS_DEV \
-keybd evdev,,device=$KEY_DEV >/dev/null 2>&1 &
check_status
fi
==== end /etc/init.d/xfbdev ====
Naoki Ueda さんは書きました:
> 竹之下様
>
> 上田です、
> お世話になります。
> さっそくのご回答、どうもありがとうございます。
> さっそく試してみましたところ、以下のようになり、タッチパネルがevent7に割
> り振られてしまっていました。
>
> 他のUSBデバイスを抜いて起動し、USB機器を後から挿したところ、タッチパネル
> が動くようになりました。
> ただ、組み込みで使うため、通常はUSB機器は差しっぱなしになります。
> 番号を固定する方法をご教示いただけませんでしょうか。
> 並行してマニュアルも探します。
>
> どうぞよろしくお願いいたします。
> 上田
>
> [email@hidden (ttymxc1) ~]# evtest /dev/input/event5
> Input driver version is 1.0.0
> Input device ID: bus 0x3 vendor 0x1871 product 0x1f0 version 0x8
> Input device name: "USB2.0 Camera"
> Supported events:
> Event type 0 (Sync)
> Event type 1 (Key)
> Event code 256 (Btn0)
> Testing ... (interrupt to exit)
>
> [email@hidden (ttymxc1) ~]# evtest /dev/input/event6
> Input driver version is 1.0.0
> Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
> Input device name: "gpio-keys"
> Supported events:
> Event type 0 (Sync)
> Event type 1 (Key)
> Event code 28 (Enter)
> Event code 102 (Home)
> Event code 139 (Menu)
> Event code 158 (Back)
> Testing ... (interrupt to exit)
>
> [email@hidden (ttymxc1) ~]# evtest /dev/input/event7
> Input driver version is 1.0.0
> Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
> Input device name: "imx_adc_ts"
> Supported events:
> Event type 0 (Sync)
> Event type 1 (Key)
> Event code 330 (Touch)
> Event type 3 (Absolute)
> Event code 0 (X)
> Value 2029
> Min 100
> Max 4000
> Event code 1 (Y)
> Value 2447
> Min 100
> Max 4000
> Event code 24 (Pressure)
> Value 0
> Min 0
> Max 1
> Testing ... (interrupt to exit)
> Event: time 1271057682.575173, -------------- Report Sync ------------
> Event: time 1271057682.595017, -------------- Report Sync ------------
> Event: time 1271057682.633307, -------------- Report Sync ------------
> Event: time 1271057682.645018, type 3 (Absolute), code 0 (X), value 981
> Event: time 1271057682.645033, type 3 (Absolute), code 1 (Y), value 2609
> Event: time 1271057682.645038, type 3 (Absolute), code 24 (Pressure),
> value 1
> Event: time 1271057682.645041, type 1 (Key), code 330 (Touch), value 1
> Event: time 1271057682.645046, -------------- Report Sync ------------
> Event: time 1271057682.665002, type 3 (Absolute), code 0 (X), value 592
> Event: time 1271057682.665019, type 3 (Absolute), code 1 (Y), value 2406
> Event: time 1271057682.665030, -------------- Report Sync ------------
> Event: time 1271057682.685000, type 3 (Absolute), code 0 (X), value 703
> Event: time 1271057682.685017, type 3 (Absolute), code 1 (Y), value 2415
> Event: time 1271057682.685027, -------------- Report Sync ------------
> Event: time 1271057682.705110, type 3 (Absolute), code 0 (X), value 899
> Event: time 1271057682.705126, type 3 (Absolute), code 1 (Y), value 2447
> Event: time 1271057682.705137, -------------- Report Sync ------------
> Event: time 1271057682.727066, type 3 (Absolute), code 0 (X), value 832
> Event: time 1271057682.727082, type 3 (Absolute), code 1 (Y), value 2366
> Event: time 1271057682.727092, -------------- Report Sync ------------
> Event: time 1271057682.745133, type 3 (Absolute), code 0 (X), value 1431
> Event: time 1271057682.745149, type 3 (Absolute), code 1 (Y), value 2527
> Event: time 1271057682.745160, -------------- Report Sync ------------
> Event: time 1271057682.765003, type 3 (Absolute), code 0 (X), value 1418
> Event: time 1271057682.765020, type 3 (Absolute), code 1 (Y), value 2424
> Event: time 1271057682.765031, -------------- Report Sync ------------
> Event: time 1271057682.784998, type 3 (Absolute), code 0 (X), value 1381
> Event: time 1271057682.785015, type 3 (Absolute), code 1 (Y), value 2371
> Event: time 1271057682.785026, -------------- Report Sync ------------
> Event: time 1271057682.805001, type 3 (Absolute), code 0 (X), value 1527
> Event: time 1271057682.805019, type 3 (Absolute), code 1 (Y), value 2320
> Event: time 1271057682.805029, -------------- Report Sync ------------
> Event: time 1271057682.827052, type 3 (Absolute), code 0 (X), value 1381
> Event: time 1271057682.827068, type 3 (Absolute), code 1 (Y), value 2252
> Event: time 1271057682.827081, -------------- Report Sync ------------
> Event: time 1271057682.845002, type 3 (Absolute), code 0 (X), value 1501
> Event: time 1271057682.845018, type 3 (Absolute), code 1 (Y), value 2169
> Event: time 1271057682.845028, -------------- Report Sync ------------
> Event: time 1271057682.865004, type 3 (Absolute), code 0 (X), value 1635
> Event: time 1271057682.865021, type 3 (Absolute), code 1 (Y), value 2146
> Event: time 1271057682.865032, -------------- Report Sync ------------
> Event: time 1271057682.885128, type 3 (Absolute), code 0 (X), value 1430
> Event: time 1271057682.885146, type 3 (Absolute), code 1 (Y), value 2125
> Event: time 1271057682.885157, -------------- Report Sync ------------
> Event: time 1271057682.905012, type 3 (Absolute), code 0 (X), value 1622
> Event: time 1271057682.905030, type 3 (Absolute), code 1 (Y), value 2150
> Event: time 1271057682.905042, -------------- Report Sync ------------
> Event: time 1271057682.925228, type 3 (Absolute), code 0 (X), value 1747
> Event: time 1271057682.925248, type 3 (Absolute), code 1 (Y), value 2164
> Event: time 1271057682.925260, -------------- Report Sync ------------
> Event: time 1271057682.945021, type 3 (Absolute), code 0 (X), value 1917
> Event: time 1271057682.945037, type 3 (Absolute), code 1 (Y), value 2167
> Event: time 1271057682.945049, -------------- Report Sync ------------
> Event: time 1271057682.965014, type 3 (Absolute), code 1 (Y), value 2204
> Event: time 1271057682.965035, -------------- Report Sync ------------
> Event: time 1271057682.986003, type 3 (Absolute), code 0 (X), value 1878
> Event: time 1271057682.986018, type 3 (Absolute), code 1 (Y), value 2257
> Event: time 1271057682.986030, -------------- Report Sync ------------
> Event: time 1271057683.005007, type 3 (Absolute), code 0 (X), value 1965
> Event: time 1271057683.005031, -------------- Report Sync ------------
> Event: time 1271057683.025011, type 3 (Absolute), code 0 (X), value 1973
> Event: time 1271057683.025028, type 3 (Absolute), code 1 (Y), value 2272
> Event: time 1271057683.025040, -------------- Report Sync ------------
> Event: time 1271057683.045004, type 3 (Absolute), code 0 (X), value 1897
> Event: time 1271057683.045020, type 3 (Absolute), code 1 (Y), value 2274
> Event: time 1271057683.045033, -------------- Report Sync ------------
> Event: time 1271057683.065005, type 3 (Absolute), code 0 (X), value 1931
> Event: time 1271057683.065024, type 3 (Absolute), code 1 (Y), value 2293
> Event: time 1271057683.065035, -------------- Report Sync ------------
> Event: time 1271057683.086936, type 3 (Absolute), code 0 (X), value 1990
> Event: time 1271057683.086953, type 3 (Absolute), code 1 (Y), value 2303
> Event: time 1271057683.086965, -------------- Report Sync ------------
> Event: time 1271057683.105003, type 3 (Absolute), code 0 (X), value 1983
> Event: time 1271057683.105019, type 3 (Absolute), code 1 (Y), value 2311
> Event: time 1271057683.105030, -------------- Report Sync ------------
> Event: time 1271057683.125014, type 3 (Absolute), code 0 (X), value 1993
> Event: time 1271057683.125031, type 3 (Absolute), code 1 (Y), value 2338
> Event: time 1271057683.125043, -------------- Report Sync ------------
>
>
> Takenoshita Koyo wrote:
>> 竹之下です。
>>
>> a440のユーザーランドには、evtest というテスト用のアプリ
>> が入っていますので、それを使ってデバイスが認識されているか
>> ご確認いただけますでしょうか？
>>
>> コマンドは、
>> evtest /dev/input/event1
>> です。
>>
>> evtest を実行して、タッチパネルに触れると、以下のような表示
>> になるはずです。
>>
>> [email@hidden (ttymxc1) ~]# evtest /dev/input/event1
>> Input driver version is 1.0.0
>> Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
>> Input device name: "imx_adc_ts"
>> Supported events:
>> Event type 0 (Sync)
>> Event type 1 (Key)
>> Event code 330 (Touch)
>> Event type 3 (Absolute)
>> Event code 0 (X)
>> Value 2436
>> Min 100
>> Max 4000
>> Event code 1 (Y)
>> Value 2716
>> Min 100
>> Max 4000
>> Event code 24 (Pressure)
>> Value 0
>> Min 0
>> Max 1
>> Testing ... (interrupt to exit)
>> Event: time 1271828405.883976, type 3 (Absolute), code 0 (X), value 646
>> Event: time 1271828405.883999, type 3 (Absolute), code 1 (Y), value 3002
>> Event: time 1271828405.884005, type 3 (Absolute), code 24 (Pressure),
>> value 1
>> Event: time 1271828405.884009, type 1 (Key), code 330 (Touch), value 1
>> Event: time 1271828405.884014, -------------- Report Sync ------------
>> Event: time 1271828405.894998, type 3 (Absolute), code 24 (Pressure),
>> value 0
>> Event: time 1271828405.895015, type 1 (Key), code 330 (Touch), value 0
>> Event: time 1271828405.895017, -------------- Report Sync ------------
>> Event: time 1271828405.914998, type 3 (Absolute), code 0 (X), value 594
>> Event: time 1271828405.915017, type 3 (Absolute), code 1 (Y), value 3022
>> Event: time 1271828405.915023, type 3 (Absolute), code 24 (Pressure),
>> value 1
>> Event: time 1271828405.915026, type 1 (Key), code 330 (Touch), value 1
>> Event: time 1271828405.915031, -------------- Report Sync ------------
>> Event: time 1271828405.935129, type 3 (Absolute), code 0 (X), value 595
>> Event: time 1271828405.935146, type 3 (Absolute), code 1 (Y), value 3019
>> Event: time 1271828405.935157, -------------- Report Sync ------------
>> Event: time 1271828405.954978, type 3 (Absolute), code 0 (X), value 618
>> Event: time 1271828405.954998, type 3 (Absolute), code 1 (Y), value 2980
>> Event: time 1271828405.955008, -------------- Report Sync ------------
>> Event: time 1271828405.974975, type 3 (Absolute), code 0 (X), value 647
>> Event: time 1271828405.974992, type 3 (Absolute), code 1 (Y), value 2972
>> Event: time 1271828405.975003, -------------- Report Sync ------------
>> Event: time 1271828405.994971, type 3 (Absolute), code 24 (Pressure),
>> value 0
>> Event: time 1271828405.994984, type 1 (Key), code 330 (Touch), value 0
>> Event: time 1271828405.994986, -------------- Report Sync ------------
>>
>> 表示が異なるようであれば、実行結果を貼り付けてください。
>>
>> ※ USBキーボードなど、インプットデバイスを接続しているとイベントデバイスの
>> 番号が変わる可能性があります。
>> 「Armadillo-400 シリーズソフトウェアマニュアル」の「8.7 タッチスク
>> リーン」
>> もご確認ください。
>>
>> 以上、よろしくお願いいたします。
>>
>> Naoki Ueda さんは書きました:
>>> 上田と申します。
>>>
>>> Armadillo440でタッチパネルが効かなくなってしまいました。
>>> make menuconfig でgdbserverをチェックしてmake all→makeのエラー
>>> その後 make menuconfig で元の設定に戻して（「戻したつもり」です）make、
>>> カーネルリージョンの書き換えをしたところ動かなくなりました。
>>> 付属のfunctesterというアプリケーションでも、タッチパネルが全く反応してい
>>> ません。
>>> どなたかタッチパネルを有効に戻す方法をご存じの方がおられましたら、ご教示
>>> ください。
>>> よろしくお願いいたします。
>>>
>>> 上田
>>> _______________________________________________
>>> armadillo mailing list
>>> email@hidden
>>> http://lists.atmark-techno.com/cgi-bin/mailman/listinfo/armadillo
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com Version: 9.0.814 / Virus Database:
>> 271.1.1/2824 - Release Date: 04/21/10 05:14:00
>>
>
> _______________________________________________
> armadillo mailing list
> email@hidden
> http://lists.atmark-techno.com/cgi-bin/mailman/listinfo/armadillo
--
Koyo Takenoshita
armadillo メーリングリストの案内