ASUS T101MT
Mnauel bbasd
I recentcly buy this machine Asus T101MT
I like very much ANDROID and I try to install into T101MT. But the
toucscreen do not work. I tray to recomplile the kernel witn option
T101*, etc.. But the recompilation fail. All other work properly
(wifi, camera, ...) but NOT the touch scren.
Please there is a way to set working the touch screen??
Best regards
Mbo
Al Sutton
Al.
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>
dubois
On my EEE PC T101MT with the Froyo version, the touch screen doesn't
work and the camera is upside down. Same than Ubuntu and I found the
drivers there :
https://help.ubuntu.com/community/T101MT
Someone could me give some advise how to install them....
Thanks for any helps
Mnauel bbasd
I'm trying to compile Android-x86 in Ubuntu. But i have problem win the version that i use to compile it. I will try to use another version or ubuntu (10.10) into a Virtual Box machine and them try to copile Android-x86.
Them i will try to modify something a try to use the driver
https://help.ubuntu.com/community/T101MT
When I have any result I will show you
Thanks
Mnauel bbasd
perfect I get it
Every thing work perfly
The touch scren is ok ok ok ok...
Best regards
Chih-Wei Huang
Does multitouch work?
Could you share the procedures?
2011/1/5 Mnauel bbasd <mabo6...@gmail.com>:
> perfect I get it
>
> Every thing work perfly
> The touch scren is ok ok ok ok...
>
> Best regards
>
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Mnauel bbasd
Excuse me for the delay in answering and for my English.
The Multitouch not works. SORRY.
In order to activate the touch screen it is only necessary to make two little changes:
1.- Modifying the file index: eeep_info
Your you have to add a new entry
T101*)
EXTMOD="usbtouchscreen"
BOARD_USES_TSLIB=true
You have reported this posibility before. Thanks
2.- Modifying the file: eeepc_defconfig
We have to replace the line
# CONFIG_HID_EGALAX is not set
for this one
CONFIG_HID_EGALAX=y
¡¡¡ And that all !!!. Very easy but time to find it.
For people that are not able to compile, I attached the compiled kernel file, so that if this file is replaced for the one that have the usb iso boot, this will work directly.
I am trying a lot of applications ( audio, video, system, mail, etc ... ) and i have to say that may of them works very well.
I work in the Multitouch.
I would like to work on the development of Android-x86 with my ASUS T101MT.
Is it possible?
Best regards
--
Michael Klein
Thank you very much Mnauel. I am an extreme beginner and can not
compile. I was wondering if you could do the same fix but for the
t91mt instead of the t101mt. I understand how it should be done once I
would open up the kernel, but since I really do not know how to
compile, I am stuck.
Thanks again for all your work so far.
>
>
> > Nice work.
> > Does multitouch work?
>
> > Could you share the procedures?
>
>
> > > Every thing work perfly
> > > The touch scren is ok ok ok ok...
>
> > > Best regards
>
> > --
> > Chih-Wei
> > Android-x86 project
> >http://www.android-x86.org
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Android-x86" group.
> > To post to this group, send email to andro...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
> >http://groups.google.com/group/android-x86?hl=en.
>
>
>
> 3264KViewDownload
Mnauel bbasd
I modify the eeep_info file wiht 2 new products:
T91MT)
EXTMOD="usbtouchscreen"
BOARD_USES_TSLIB=true
;;
T101MT)
EXTMOD="usbtouchscreen"
BOARD_USES_TSLIB=true
;;
Find attached the new kernel file
The display screen timeout fail. Change to 30 minutes.
It would be better a new option in the display setting to deactive the timeout without any time.
Regards
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
Chih-Wei Huang
> Excuse me for the delay in answering and for my English.
> The Multitouch not works. SORRY.
> In order to activate the touch screen it is only necessary to make two
> little changes:
> 1.- Modifying the file index: eeep_info
> Your you have to add a new entry
> T101*)
> EXTMOD="usbtouchscreen"
> BOARD_USES_TSLIB=true
> You have reported this posibility before. Thanks
> 2.- Modifying the file: eeepc_defconfig
> We have to replace the line
> # CONFIG_HID_EGALAX is not set
> for this one
> CONFIG_HID_EGALAX=y
> ¡¡¡ And that all !!!. Very easy but time to find it.
Set BOARD_USES_TSLIB=true for T101* is correct.
It enables the touchscreen calibration for T101*.
But set EXTMOD="usbtouchscreen" and
CONFIG_HID_EGALAX=y
confused me. The two drivers seem to be
independent and should not be used together.
Actually usbtouchscreen is not enabled in
eeepc_defconfig, so the setting has no effect.
I guess HID_EGALAX is the key.
So my suggestion is remove EXTMOD="..." and
set CONFIG_HID_EGALAX=m (set to be a module)
If auto-detect works for eGalax touch panel,
the module should be loaded correctly.
If not, set EXTMOD="hid-egalax".
Please verify these changes.
> For people that are not able to compile, I attached the compiled kernel
> file, so that if this file is replaced for the one that have the usb iso
> boot, this will work directly.
It's better to give your change in a patch format
so we developers can know what you did exactly.
cd device/asus/eeepc
git diff
> I am trying a lot of applications ( audio, video, system, mail, etc ... )
> and i have to say that may of them works very well.
>
> I work in the Multitouch.
> I would like to work on the development of Android-x86 with my ASUS T101MT.
> Is it possible?
You have worked on it.
If you meant to get a developer account of android-x86.org,
send me a private email. Thank you.
Regards,
Mnauel bbasd
You are right
The key is
CONFIG_HID_EGALAX=y
This is enough to make work the touch screen in the Asus T101MT (not sure in T91MT).
I can not load the module because I always have a compile error and I only are able to generate the kernel file and not the iso image.
I think that it is relelated with the java version. I use 6.2.0 with ubuntu 9.10 64 and I can not install another version ??. I will try to install an Ubuntu (which version??) in a virtual machine and try to compile from the virtual machine...
This is the error:
host StaticLib: libpng (out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/libpng.a)
echo out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/png.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngerror.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pnggccrd.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngget.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngmem.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngpread.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngread.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngrio.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngrtran.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngrutil.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngset.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngtrans.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngvcrd.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngwio.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngwrite.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngwtran.o out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/pngwutil.o | xargs ar crsP out/host/linux-x86/obj/STATIC_LIBRARIES/libpng_intermediates/libpng.a
host Executable: aapt (out/host/linux-x86/obj/EXECUTABLES/aapt_intermediates/aapt)
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.4/../../../libz.so when searching for -lz
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.2.4/../../../libz.a when searching for -lz
/usr/bin/ld: skipping incompatible /usr/lib/libz.so when searching for -lz
/usr/bin/ld: skipping incompatible /usr/lib/libz.a when searching for -lz
/usr/bin/ld: cannot find -lz
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/aapt_intermediates/aapt] Error 1
If you or anyone kow the solution and can help me, I will be able to check and verify that the module is loaded correctly
Best regards
Chih-Wei Huang
2011/1/9 Mnauel bbasd <mabo6...@gmail.com>:
> host Executable: aapt
> (out/host/linux-x86/obj/EXECUTABLES/aapt_intermediates/aapt)
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-linux-gnu/4.2.4/../../../libz.so when searching for -lz
> /usr/bin/ld: skipping incompatible
> /usr/lib/gcc/x86_64-linux-gnu/4.2.4/../../../libz.a when searching for -lz
> /usr/bin/ld: skipping incompatible /usr/lib/libz.so when searching for -lz
> /usr/bin/ld: skipping incompatible /usr/lib/libz.a when searching for -lz
> /usr/bin/ld: cannot find -lz
> collect2: ld returned 1 exit status
> make: *** [out/host/linux-x86/obj/EXECUTABLES/aapt_intermediates/aapt] Error
> 1
--
Mnauel bbasd
I already have compiled the image and try all the combinations. Before your comments, I already had tried to reinstall the "zlib-dev" libraries, but my Linux is 64 and I never thought in using the 32 library version. I have also needed the library "ncurses" of 32.
The eGalax touch panel auto-detect NOT WOK.
We have to add the line
EXTMOD="hid-egalax"
With this line it work.
Now, when you start the first time Android you enter directly into the calibration screen. Before this, I made the calibration manually using the command ts_calibration, although it was not necessary.
In a few days I will generate a patch to see you all the modifications in order to modify the next release of Android-x86, but you know perfectly the little modifications (I will install a linux of 32 to make sure that the kernel and iso are correctly generated).
Best Regards
mabo
(my nickname is mabo)
Chih-Wei Huang
I have put all necessary changes to the git repository
according to your testing
Please sync and verify it.
(revert your changes first)
Thank you!
2011/1/9 Mnauel bbasd <mabo6...@gmail.com>:
> I already have compiled the image and try all the combinations. Before your
> comments, I already had tried to reinstall the "zlib-dev" libraries, but my
> Linux is 64 and I never thought in using the 32 library version. I have also
> needed the library "ncurses" of 32.
>
> The eGalax touch panel auto-detect NOT WOK.
>
> We have to add the line
> EXTMOD="hid-egalax"
> With this line it work.
>
> Now, when you start the first time Android you enter directly into the
> calibration screen. Before this, I made the calibration manually using the
> command ts_calibration, although it was not necessary.
>
> In a few days I will generate a patch to see you all the modifications in
> order to modify the next release of Android-x86, but you know perfectly the
> little modifications (I will install a linux of 32 to make sure that the
> kernel and iso are correctly generated).
>
> Best Regards
> mabo
> (my nickname is mabo)
--
Kyle Dresser
On Jan 9, 9:52 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> Hello mabo,
> I have put all necessary changes to the git repository
> according to your testing
> Please sync and verify it.
> (revert your changes first)
> Thank you!
>
>
>
>
>
> > I already have compiled the image and try all the combinations. Before your
> > comments, I already had tried to reinstall the "zlib-dev" libraries, but my
> > Linux is 64 and I never thought in using the 32 library version. I have also
> > needed the library "ncurses" of 32.
>
> > The eGalax touch panel auto-detect NOT WOK.
>
> > We have to add the line
> > EXTMOD="hid-egalax"
> > With this line it work.
>
> > Now, when you start the first time Android you enter directly into the
> > calibration screen. Before this, I made the calibration manually using the
> > command ts_calibration, although it was not necessary.
>
> > In a few days I will generate a patch to see you all the modifications in
> > order to modify the next release of Android-x86, but you know perfectly the
> > little modifications (I will install a linux of 32 to make sure that the
> > kernel and iso are correctly generated).
>
> > Best Regards
> > mabo
> > (my nickname is mabo)
>
> --
> Chih-Wei
>
> - Show quoted text -
Chih-Wei Huang
Check your eeepc_info to see
if it has settings for T91MT?
2011/1/10 Kyle Dresser <dre...@gmail.com>:
> Touchscreen is not working on T91MT with 2011-1-10 eeepc nightly...
--
kinneko
I tried this patch for T91MT.
diff --git a/eeepc_defconfig b/eeepc_defconfig
index ecd310a..a716e18 100644
--- a/eeepc_defconfig
+++ b/eeepc_defconfig
@@ -1809,7 +1809,7 @@ CONFIG_USB_HID=y
# CONFIG_HID_LOGITECH is not set
# CONFIG_HID_MAGICMOUSE is not set
# CONFIG_HID_MICROSOFT is not set
-# CONFIG_HID_MOSART is not set
+CONFIG_HID_MOSART=m
# CONFIG_HID_MONTEREY is not set
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_ORTEK is not set
diff --git a/eeepc_info b/eeepc_info
index 3f4a71b..7caa2a6 100644
--- a/eeepc_info
+++ b/eeepc_info
@@ -17,6 +17,11 @@ eeepc_info()
UVESA_MODE=${UVESA_MODE:-1024x600}
BOARD_USES_TSLIB=true
;;
+ T91MT)
+ FB0DEV=
+ UVESA_MODE=${UVESA_MODE:-1024x600}
+ BOARD_USES_TSLIB=true
+ ;;
T101)
BOARD_USES_TSLIB=true
;;
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index 4822e34..67d25ea 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -529,5 +529,6 @@
#define USB_DEVICE_ID_KYE_ERGO_525V 0x0087
#define USB_DEVICE_ID_KYE_GPEN_560 0x5003
+#define USB_DEVICE_ID_TURBOX_TOUCHSCREEN_MOSART 0x7100
#endif
But usb_image not include hid_mosart.ko.
Is there any setting elsewhere?
Chih-Wei Huang
Probably the kernel & modules are not recompiled
correctly. To ensure the kernel is recompiled,
(in the top dir of android-x86 tree)
rm -f out/target/product/eeepc/kernel
Then make again.
2011/1/10 kinneko <kin...@gmail.com>:
--
kinneko
The mosart driver is built.
./out/target/product/eeepc/system/lib/modules/2.6.35.7-android-x86-eeepc+/kernel/drivers/hid/hid-mosart.ko
but not include in out/target/product/eeepc/eeepc_usb.img.
2011/1/10 Chih-Wei Huang <cwh...@android-x86.org>:
Chih-Wei Huang
rm -f out/target/product/eeepc/system.*
and make again.
2011/1/10 kinneko <kin...@gmail.com>:
> Ubuntu 10.10 well working patched mosart driver.
>
> The mosart driver is built.
>
> ./out/target/product/eeepc/system/lib/modules/2.6.35.7-android-x86-eeepc+/kernel/drivers/hid/hid-mosart.ko
>
> but not include in out/target/product/eeepc/eeepc_usb.img.
--
Mnauel bbasd
I have recompiled the kenel and rebuilt the iso image with the last git repository and the touch screen is OK (NOT multitouch) on the ASUS T101MT.
The multitouch have to be next task, right?
What is the status of accelerate graphics drivers?
Best Regards
mabo
Chih-Wei Huang
> I have recompiled the kenel and rebuilt the iso image with the last git
> repository and the touch screen is OK (NOT multitouch) on the ASUS T101MT.
> The multitouch have to be next task, right?
Yes, do you have any progress?
> What is the status of accelerate graphics drivers?
Does T101MT also use GMA500?
BTW, anyone has the status about T91MT?
Mnauel bbasd
I dont have progress with multitouch. In Linux the multitouch is made by a deamon two-finger.
You can find the source code here:
https://help.ubuntu.com/community/T101MT?action=AttachFile&do=view&target=twofing-0.0.7.tar.gz
The Integrated Graphics for T101MT is GMA 3150
The Integrated Graphics for T91MT is GMA 500
Regards
mabo
jaegs
Thanks for working on the t101mt. I tried using eeepc-20110112.iso on
my t101mt and neither the touchscreen nor the wi-fi works (It
recognizes the network but can't connect.) I think working wifi is
more important than multitouch. Even though the screen supports
multitouch, it's somewhat clumsy on the plastic resistive screen.
On Jan 11, 12:22 pm, Mnauel bbasd <mabo666...@gmail.com> wrote:
> Hello Chih-Wey
>
> I have recompiled the kenel and rebuilt the iso image with the last git
> repository and the touch screen is OK (NOT multitouch) on the ASUS T101MT.
> The multitouch have to be next task, right?
> What is the status of accelerate graphics drivers?
>
> Best Regards
> mabo
>
>
>
>
>
>
>
> > Hello mabo,
> > I have put all necessary changes to the git repository
> > according to your testing
> > Please sync and verify it.
> > (revert your changes first)
> > Thank you!
>
> > .
Mnauel bbasd
I dont know how is made the nightly eeepc-20110112.iso. I use it from time to time but the touch screen no work. I think that it not has the module egalax.
Use the Test build 20110101 from http://www.android-x86.org/. Then replace the kernel file with the one that I provided some mails ago for the T101MT. With this procedure the touch screen will work,
The wifi always work. But, before to activate the wifi, you have to de-activate the ethernet. The two at the same time no work.
Other posibility is to recompile the kernet and generate the iso image from the git.
Regards
mabo
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
Kyle Dresser
suggested
above by Kinneko. I have also removed the system.img and kernel files
and rebuilt, as suggested by Chih-Wei, but I can't seem to get
./out/target/product/eeepc/system/lib/modules/2.6.35.7-android-x86-
eeepc+/kernel/drivers/hid/hid-mosart.ko
to be built. I have very little linux knowledge, and any help would
be
greatly appreciated.
Also FYI the android-x86-2.2-eeepc release does not have working
touchscreen for T91MT.
EDIT: I did a repo sync, deleted system.img and kernel and rebuilt
again. Now
./out/target/product/eeepc/system/lib/modules/2.6.35.7-android-x86-
eeepc+/kernel/drivers/hid/hid-mosart.ko
is built but still no touchscreen support. Also when booting the
machine now says "warning, not an asus product"
I have about three days of linux experience and I'm trying to learn as
much as possible, but I could be overlooking something very simple.
Any help would be fantastic. Thankyou.
jtjs
t91mt users. you can find more details here:
http://www.mail-archive.com/multi-t...@lists.launchpad.net/msg00544.html
jtjs
explicitly ignores the t91mt's touchscreen(this was an error during
the original mosart driver commit to the kernel).
Fortunately, there is a fix, although it's not in the mainline linux
kernel yet(afaik). Benjamin tissoiries made 3 patches for ubuntu back
in november, although they haven't been pushed into any official
release yet.
you can find the patches at this ubuntu mailing list thread:
http://www.mail-archive.com/multi-t...@lists.launchpad.net/msg00544.html
I believe they should work fine on android, I know from my own
experiences that they enable multitouch for the t91mt on ubuntu.
Kyle Dresser
Yup, the patches you mentioned got single touch working for T91MT!
Thankyou!!!!
Now for poulsbo support...
> For the t91mt there are some issues with the drivers. In fact, hid
> explicitly ignores the t91mt's touchscreen(this was an error during
> the original mosart driver commit to the kernel).
>
> Fortunately, there is a fix, although it's not in the mainline linux
> kernel yet(afaik). Benjamin tissoiries made 3 patches for ubuntu back
> in november, although they haven't been pushed into any official
> release yet.
>
> you can find the patches at this ubuntu mailing list thread:
Kyle Dresser
Modprobe hid-mosart
in connecbot.
jtjs
is in eeepc_info
kinneko
I'm now building these patch.
but my build environment is very slow...
Do you think that you do not have any problem with these patches?
root@T91MT:~/mydroid/device/asus/eeepc# git diff
diff --git a/eeepc_info b/eeepc_info
index 960a804..73c0578 100644
--- a/eeepc_info
+++ b/eeepc_info
@@ -15,11 +15,15 @@ eeepc_info()
UVESA_MODE=${UVESA_MODE:-1024x600}
BOARD_USES_TSLIB=true
;;
- T91MT|T101MT)
+ T91MT)
UVESA_MODE=${UVESA_MODE:-1024x600}
BOARD_USES_TSLIB=true
- EXTMOD="$EXTMOD hid-egalax"
+ EXTMOD="$EXTMOD hid-mosart"
;;
+ T101MT)
+ UVESA_MODE=${UVESA_MODE:-1024x600}
+ BOARD_USES_TSLIB=true
+ EXTMOD="$EXTMOD hid-egalax"
*)
;;
esac
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index c57315d..8c78cda 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1280,6 +1280,7 @@ static const struct hid_device_id hid_blacklist[] = {
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_ALU_WIRE
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_FOUNTAIN_TP_ON
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_GEYSER1_TP_ONL
+ { HID_USB_DEVICE(USB_VENDOR_ID_ASUS, USB_DEVICE_ID_ASUS_T91MT)},
{ HID_USB_DEVICE(USB_VENDOR_ID_BELKIN, USB_DEVICE_ID_FLIP_KVM) },
{ HID_USB_DEVICE(USB_VENDOR_ID_BTC, USB_DEVICE_ID_BTC_EMPREX_REMOTE) },
{ HID_USB_DEVICE(USB_VENDOR_ID_CANDO, USB_DEVICE_ID_CANDO_MULTI_TOUCH) }
@@ -1572,7 +1573,6 @@ static const struct hid_device_id hid_ignore_list[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_AIPTEK, USB_DEVICE_ID_AIPTEK_24) },
{ HID_USB_DEVICE(USB_VENDOR_ID_AIRCABLE, USB_DEVICE_ID_AIRCABLE1) },
{ HID_USB_DEVICE(USB_VENDOR_ID_ALCOR, USB_DEVICE_ID_ALCOR_USBRS232) },
- { HID_USB_DEVICE(USB_VENDOR_ID_ASUS, USB_DEVICE_ID_ASUS_T91MT)},
{ HID_USB_DEVICE(USB_VENDOR_ID_ASUSTEK, USB_DEVICE_ID_ASUSTEK_LCM)},
{ HID_USB_DEVICE(USB_VENDOR_ID_ASUSTEK, USB_DEVICE_ID_ASUSTEK_LCM2)},
{ HID_USB_DEVICE(USB_VENDOR_ID_AVERMEDIA, USB_DEVICE_ID_AVER_FM_MR800) }
diff --git a/drivers/hid/hid-mosart.c b/drivers/hid/hid-mosart.c
index e91437c..93b2cb4 100644
--- a/drivers/hid/hid-mosart.c
+++ b/drivers/hid/hid-mosart.c
@@ -90,6 +90,11 @@ static int mosart_input_mapping(struct hid_device *hdev, stru
case 0xff000000:
/* ignore HID features */
return -1;
+
+ case HID_UP_BUTTON:
+ /* ignore buttons */
+ return -1;
+
}
return 0;
@@ -230,6 +235,19 @@ static int mosart_probe(struct hid_device *hdev, const stru
return ret;
}
+#ifdef CONFIG_PM
+static int mosart_reset_resume(struct hid_device *hdev)
+{
+ struct hid_report_enum *re = hdev->report_enum
+ + HID_FEATURE_REPORT;
+ struct hid_report *r = re->report_id_hash[7];
+
+ r->field[0]->value[0] = 0x02;
+ usbhid_submit_report(hdev, r, USB_DIR_OUT);
+ return 0;
+}
+#endif
+
static void mosart_remove(struct hid_device *hdev)
{
hid_hw_stop(hdev);
@@ -257,6 +275,9 @@ static struct hid_driver mosart_driver = {
.input_mapped = mosart_input_mapped,
.usage_table = mosart_grabbed_usages,
.event = mosart_event,
+#ifdef CONFIG_PM
+ .reset_resume = mosart_reset_resume,
+#endif
};
static int __init mosart_init(void)
kinneko
diff --git a/eeepc_defconfig b/eeepc_defconfig
index 588c52b..4f6168d 100644
--- a/eeepc_defconfig
+++ b/eeepc_defconfig
@@ -1809,7 +1809,7 @@ CONFIG_HID_EGALAX=m
Chih-Wei Huang
I have pushed all the changes for T91MT
into git server.
Let me know if it works for you.
kinneko
My build is not yet over...
This pc is very slow.
latest build was ...
root@T91MT:~/mydroid# time make usb_img TARGET_PRODUCT=eeepc
real 380m6.110s
user 381m43.275s
sys 30m37.399s
now building libwebcore.
2011/1/17 Chih-Wei Huang <cwh...@android-x86.org>:
alexkhvlg
I'm have T101MT with mosart touch panel. "Bus 003 Device 002: ID
0486:0186 ASUS Computers, Inc."
1. I get newer version froyo-x86 after patch kinneko at 19:04.
2. Build it.
3. Touch screen not working. Also i enter "modprobe hid_mosart" and/or
"modprobe hid_egalax". Module loading, but touch still not work.
4. Now i change in file eeepc_info, in line T101M), I replace
EXTMOD="$EXTMOD hid-egalax" to EXTMOD="$EXTMOD hid-mosart".
Also add line in hid-core.c { HID_USB_DEVICE(USB_VENDOR_ID_ASUS,
USB_DEVICE_ID_ASUS_T101MT)}.
5. Built again. Still not working.
In all builts when android boot i can calibrate touch panel. That
means, kernel gets events from panel ?
Rebuild all android take more time. How i can rebuild only modules or
kernel ?
On 17 янв, 22:16, kinneko <kinn...@gmail.com> wrote:
> Thank you!
> My build is not yet over...
> This pc is very slow.
>
> latest build was ...
>
> root@T91MT:~/mydroid# time make usb_img TARGET_PRODUCT=eeepc
> real 380m6.110s
> user 381m43.275s
> sys 30m37.399s
>
> now building libwebcore.
>
alexkhvlg
mabo-Gmail
If you have a T101MT (not a T91MT) you have to use the module hi_egalax.
With this module loaded at start up the touch screen work.
Regard
Mabo
alexkhvlg <alex...@gmail.com> wrote:
jtjs
screen. The bus id he gave matches to what has been seen for that
revision.
On Jan 17, 4:55 pm, mabo-Gmail <mabo666...@gmail.com> wrote:
> Hi
>
> If you have a T101MT (not a T91MT) you have to use the module hi_egalax.
> With this module loaded at start up the touch screen work.
>
> Regard
> Mabo
>
kinneko
I tested new snapshot build for T91MT.
touch screen ok.
When android drop down to lock screen, screen break dwon.
http://farm6.static.flickr.com/5163/5365752468_f0d7c989bd.jpg
2011/1/17 kinneko <kin...@gmail.com>:
Chih-Wei Huang
> I tested new snapshot build for T91MT.
> touch screen ok.
Nice.
> When android drop down to lock screen, screen break dwon.
> http://farm6.static.flickr.com/5163/5365752468_f0d7c989bd.jpg
Well, I also see this problem on my T91 (no MT).
jtjs
verify the screen is working by going to another console and running
ts_calibrate, but the ui nolonger responds to the touch screen.
On Jan 17, 8:47 pm, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> 2011/1/18 kinneko <kinn...@gmail.com>:
Chih-Wei Huang
from the dmi data?
2011/1/18 jtjs <jtjs...@gmail.com>:
> Mabo: There is a revision of the t101mt that uses the mosart touch
> screen. The bus id he gave matches to what has been seen for that
> revision.
--
jtjs
forums...
Looking at the mosart driver though(hid-mosart.c), it has the
following near the bottom
static const struct hid_device_id mosart_devices[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_ASUS, USB_DEVICE_ID_ASUS_T91MT) },
{ }
};
Perhaps adding the T101MT to that list will solve alex's issue?
On Jan 17, 9:17 pm, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> Can we tell difference of the revisioned T101MT
> from the dmi data?
>
kinneko
When I turned it on once and came back from a screen lock, I was not
able to turn it off.
2011/1/18 kinneko <kin...@gmail.com>:
alexkhvlg
Mnauel bbasd
I have the same problem with the T101MT
By the moment, I use the program "KeepScreen" to block all applications and no problem. Android run hours without this problem.
I have Ubuntu 10.10, Windows 7 Home premium, and Android-x86 installed in the T101MT, with a multiboot. I have to say that, with many many differences, the best operation system is Android-x86. I use, for example, Repligo Reader to read pdf document and it is very fast and very nice....
Regards
mabo
alexkhvlg
{ HID_USB_DEVICE(USB_VENDOR_ID_ASUS,
USB_DEVICE_ID_ASUS_T91MT) },
USB_DEVICE_ID_ASUS_T101MT) },
{ }
};
And touch still not working.
Thats my DMI data:
# dmidecode 2.9
SMBIOS 2.6 present.
30 structures occupying 1337 bytes.
Table at 0x000F0740.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 0601
Release Date: 07/26/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 512 kB
Characteristics:
ISA is supported
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 KB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 8.12
Firmware Revision: 0.39
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: ASUSTeK Computer INC.
Product Name: T101MT
Version: x.x
Serial Number: ABOAAS167581
UUID: 00CE09B0-835A-4781-2C4C-BCAEC51260E4
Wake-up Type: Power Switch
SKU Number: T101MT
Family: Eee PC
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: T101MT
Version: x.xx
Serial Number: EeePC-0123456789
Asset Tag: To Be Filled By O.E.M.
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To Be Filled By O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
Manufacturer: ASUSTeK Computer INC.
Type: Notebook
Lock: Present
Version: x.x
Serial Number: 0x00000000
Asset Tag: 0x00000000
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
Handle 0x0004, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 1
Type: Central Processor
Family: <OUT OF SPEC>
Manufacturer: Intel
ID: CA 06 01 00 FF FB E9 BF
Version: Intel(R) Atom(TM) CPU N450 @ 1.66GHz
Voltage: 1.1 V
External Clock: 167 MHz
Max Speed: 1666 MHz
Current Speed: 1666 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: Not Provided
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 1
Core Enabled: 1
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1-Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 24 KB
Maximum Size: 24 KB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Parity
System Type: Data
Associativity: Other
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2-Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 512 KB
Maximum Size: 512 KB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 8-way Set-associative
Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J4A1
Internal Connector Type: None
External Reference Designator: LPT 1
External Connector Type: DB-25 male
Port Type: Parallel Port ECP/EPP
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A1
Internal Connector Type: None
External Reference Designator: COM A
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6A1
Internal Connector Type: None
External Reference Designator: Audio Mic In
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6A1
Internal Connector Type: None
External Reference Designator: Audio Line In
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6B1 - AUX IN
Internal Connector Type: On Board Sound Input From CD-ROM
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Audio Port
Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6B2 - CDIN
Internal Connector Type: On Board Sound Input From CD-ROM
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Audio Port
Handle 0x0011, DMI type 11, 5 bytes
OEM Strings
String 1: BCAEC51260E4
String 2: 10779226000506011077354002171
String 3: 90OAM1QD11214987E10AQ
String 4: 5
Handle 0x0012, DMI type 13, 22 bytes
BIOS Language Information
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0013, DMI type 15, 35 bytes
System Event Log
Area Length: 4 bytes
Header Start Offset: 0x0000
Header Length: 2 bytes
Data Start Offset: 0x0002
Access Method: Indexed I/O, one 16-bit index port, one 8-bit data
port
Access Address: Index 0x046A, Data 0x046C
Status: Invalid, Not Full
Change Token: 0x00000000
Header Format: No Header
Supported Log Type Descriptors: 6
Descriptor 1: End of log
Data Format 1: OEM-specific
Descriptor 2: End of log
Data Format 2: OEM-specific
Descriptor 3: End of log
Data Format 3: OEM-specific
Descriptor 4: End of log
Data Format 4: OEM-specific
Descriptor 5: End of log
Data Format 5: OEM-specific
Descriptor 6: End of log
Data Format 6: OEM-specific
Handle 0x0014, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 4 GB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x0015, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Array Handle: 0x0014
Partition Width: 0
Handle 0x0016, DMI type 17, 28 bytes
Memory Device
Array Handle: 0x0014
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM0
Bank Locator: BANK0
Type: Unknown
Type Detail: Unknown
Speed: Unknown
Manufacturer: Manufacturer00
Serial Number: SerNum00
Asset Tag: AssetTagNum0
Part Number: ModulePartNumber00
Handle 0x0017, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000000003FF
Range Size: 1 kB
Physical Device Handle: 0x0016
Memory Array Mapped Address Handle: 0x0015
Partition Row Position: 1
Interleaved Data Depth: 1
Handle 0x0018, DMI type 17, 28 bytes
Memory Device
Array Handle: 0x0014
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator: BANK1
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz (1.5 ns)
Manufacturer: Manufacturer01
Serial Number: SerNum01
Asset Tag: AssetTagNum1
Part Number: ModulePartNumber01
Handle 0x0019, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x0018
Memory Array Mapped Address Handle: 0x0015
Partition Row Position: 1
Interleaved Data Depth: 1
Handle 0x001A, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
Handle 0x001B, DMI type 41, 11 bytes
Unknown Type
Header and Data:
29 0B 1B 00 01 83 00 FF FF FF FF
Strings:
To Be Filled By O.E.M.
Handle 0x001C, DMI type 41, 11 bytes
Unknown Type
Header and Data:
29 0B 1C 00 01 04 00 FF FF FF FF
Strings:
To Be Filled By O.E.M.
Handle 0x001D, DMI type 127, 4 bytes
End Of Table
jtjs
multi input quirk. To enable this you need to remove the screen from
the blacklist in hid-core.c(so that it uses the built in driver
instead of mosart) and you need to add it to the blacklist in usbhid/
hid-quirks.c with the multi input quirk.. the entry in hid-quirks.c
should look something like this:
{ USB_VENDOR_ID_ASUS, USB_DEVICE_ID_ASUS_T101MT,
HID_QUIRK_MULTI_INPUT },
note that this will only ever work for single touch.
>
> read more »
alexkhvlg
I'm repo sync and remove touch from blacklist in hid-core.c
and add line in usbhid/hid-quirks.c and add line in hid-ids.h
#define USB_DEVICE_ID_ASUS_T101MT 0x0186
Full rebuild and touch not work. even ts_calibrate can get events from
touch screen.
>
> продолжение »
tomfa...@gmail.com
kinneko
I have same problem on eeepc-20110120_usb.img.
If you repo sync and make it, may be ok.
It is necessary for you to use Linux for build.
2011/1/20 <tomfa...@gmail.com>:
Tallinn Tallinn
What I did: obtained the iso, used unetbootwin to create a bootable usb-stick from it, booted the live cd version of android from this stick.
Result: touchscreen calibration appears upon boot and reacts on tocuh, but once the system is up, it is no longer responding to the touchscreen.
I did read this threat and guessed that I would have to reload usbhid and hid like described, but I noticed: none of those modules are running on my computer, and modprobe, rmmod give a segmentation fault.