Jump to content

cyberphilia2010

cyberphilia2010

Member Since 20 Mar 2010
Offline Last Active Jun 08 2010 11:41 AM
-----

Posts I've Made

In Topic: Snow Leopard on VAIO P(VGN-P90HS) working!

02 May 2010 - 11:17 AM

(I want to start a new post since this is not about TrackPad)

I found that iWork apps are not working due to the lack of support of QE/CI in GMA.
Is anybody working on this?
I wonder how hard this is to be added.
Actually, I do not care about photobooth and games, but I do care for iWork app.
So any workaround to get iWork is fine with me.
iWork is far better than MS Office...

In Topic: Snow Leopard on VAIO P(VGN-P90HS) working!

01 May 2010 - 01:59 AM

Motion eye, P is as follow.What application you test with cam?
PhotoBooth is broken becaues our Graphics/Display driver don't have QE/CI.
At least Skype can use P's motion eye.


I was testing the cam with iChat. iChat crashes when video is enabled, although I do not really use iChat :-) (I used it just for testing).
Your ioreg output of vaiop looks almost the same as my vaiox's.
So I checked with skype and I saw that my cam works fine! Thanks much for the head-up!
Now, the webcam part is resolved! (since I do not care about iChat).

In VoodooPS2ALPSGlidePoint.cpp:IsItALPS(), You can add singles array to your id.


Thanks for your suggestion.
Looking at the code, I noticed the override success=true, so I did not add my device id to the singles array.
So I left it at it is, since IsItALPS does not seem to get called elsewhere.
I am now wondering if this trackpad is really from ALPS or not...


getModel(&E6, &E7);

DEBUG_LOG("E7: { 0x%02x, 0x%02x, 0x%02x } E6: { 0x%02x, 0x%02x, 0x%02x }",
E7.byte0, E7.byte1, E7.byte2, E6.byte0, E6.byte1, E6.byte2);

success = IsItALPS(&E6,&E7);
DEBUG_LOG("ALPS Device? %s", (success ? "yes" : "no"));

// override
success = true;
_touchPadVersion = (E7.byte2 & 0x0f) << 8 | E7.byte0;



[update]

EgoOSX said on 12/31/2009 regariding HP/Compaq Mini that

Furthermore, any kext (voodoo or appleps2) that has ALPS support will cause the trackpad to be unusable. It recognizes the trackpad as an ALPS Glidepoint v 4.115 but no initialization of the trackpad takes place.


Syslog on my vaiox says "ALPS GlidePoint 4.115", so I think I am on the same boat...
4.115 is taken from the E7 report { 0x73, 0x02, 0x64 }. So apparently HP Mini got the same Trackpad as vaiox.

[update2]

It does seem that my vaiox got ALPS touchpad, though I am not 100% sure.
In Ubuntu forum, this guy got E7 report exactly the same as vaiox.
But this guy also may have thought his touchpad is from ALPS but it may actually be not...

http://ubuntuforums..../t-1316361.html

i then found in the sources, that the first three numbers must match some kind of a hardware fingerprint which they call "E7 report". in order to find out the numbers for my notebook i changed to debug mode by defining DEBUG at the beginning. i then recompiled and loaded the new module. and voilà, my E7 report contained: 73 02 64. so i put them in a new line like this one:

{ { 0x73, 0x02, 0x64 }, 0xf8, 0xf8, ALPS_FW_BK_2 },

and recompiled and loaded the whole thing.. and tataaaaa.. my ubuntu recognized an ALPS touchpad and when i checked the mouse settings in gnome i even saw the touchpad tab where i could choose all these options and disable the pad while typing etc.. but don't jump around yet.. because sadly it had no effect on the behaviour of the touchpad.. no matter what i set, it didn't change anything..

In Topic: Snow Leopard on VAIO P(VGN-P90HS) working!

30 April 2010 - 02:52 PM

Hmm?

044e:3017 is bluetooth, PS2 is not usb device.
You need understand PS2. device is identified by E6 E7 report.

05ca:18b6 is sd/ms card reader( P is 05ca:18b2 )
P's motion eye is appear in ioreg UMH-U10( 054c:038b )
And this is UVC(USB Video Class) camera.
No special/device specific dirive is need.


Oh I am sorry, I did not report right. USB info may not be of Trackpad and USB cam.

Ok, I have added the debug print at ApplePS2ALPSGlidePoint::getModel in TrackPad.kext and the syslog says,
E7: { 0x73, 0x02, 0x64 } E6: { 0x00, 0x00, 0x64 }
A weird thing is the same function (getModel) determines that it is not ALPS device.
I do not know if this is from ALPS or not. Is there any way to check that?

Also for the web cam, I have checked the ioreg output and found the following.
The device ID (0x18b6) and Vendor ID (0x5ca) are correct?
Am I looking at something different?

+-o Sony Visual Communication Camera@0 <class IOUSBInterface, id 0x0, registered, matched, active, busy 0 (1088 ms), retain 5>
| | | | {
| | | | "IOUserClientClass" = "IOUSBInterfaceUserClientV2"
| | | | "idProduct" = 0x18b6
| | | | "IOCFPlugInTypes" = {"2d9786c6-9ef3-11d4-ad51-000a27052861"="IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle"}
| | | | "iInterface" = 0x2
| | | | "bAlternateSetting" = 0x0
| | | | "bConfigurationValue" = 0x1
| | | | "USB Interface Name" = "Sony Visual Communication Camera"
| | | | "bInterfaceProtocol" = 0x0
| | | | "bInterfaceNumber" = 0x0
| | | | "bInterfaceSubClass" = 0x1
| | | | "idVendor" = 0x5ca
| | | | "bInterfaceClass" = 0xe
| | | | "locationID" = 0xfffffffffd800000
| | | | "bNumEndpoints" = 0x1
| | | | "bcdDevice" = 0x20
| | | | }
| | | |

[update]

As you said, I confirmed from ioreg that 044e:3017 is Broadcom bluetooth (but manufacturer is ALPS?).
I am puzzled about webcam.
Do you know what IOUSBCompositeDriver does?

| | +-o EHC1@1D,7 <class IOPCIDevice, id 0x0, registered, matched, active, busy 0 (1371 ms), retain 11>
| | | +-o IOService <class IOService, id 0x0, !registered, !matched, active, busy 0, retain 4>
| | | +-o AppleUSBEHCI <class AppleUSBEHCI, id 0x0, registered, matched, active, busy 0 (1212 ms), retain 12>
| | | +-o EHCI Root Hub Simulation@1D,7 <class IOUSBRootHubDevice, id 0x0, registered, matched, active, busy 0 (60 ms), retain 10>
| | | | +-o AppleUSBHub <class AppleUSBHub, id 0x0, registered, matched, active, busy 0 (2 ms), retain 7>
| | | | +-o IOUSBInterface@0 <class IOUSBInterface, id 0x0, !registered, !matched, active, busy 0, retain 6>
| | | +-o IOUSBMiscellaneousDevice@fd800000 <class IOUSBDevice, id 0x0, registered, matched, active, busy 0 (1173 ms), retain 9>
| | | +-o IOUSBCompositeDriver <class IOUSBCompositeDriver, id 0x0, !registered, !matched, active, busy 0, retain 4>
| | | +-o Sony Visual Communication Camera@0 <class IOUSBInterface, id 0x0, registered, matched, active, busy 0 (1090 ms), retain 5>
| | | +-o IOUSBInterface@1 <class IOUSBInterface, id 0x0, registered, matched, active, busy 0 (588 ms), retain 5>

In Topic: Snow Leopard on VAIO P(VGN-P90HS) working!

29 April 2010 - 07:48 AM

@ryuu123

Thanks for the info. I have downloaded the VoodooPSController source code from
http://forum.voodoop...opic,304.0.html
(20090511.zip)
And patched the Trackpad code with ALPS patch AB posted as you suggested.
http://forum.voodoop...opic,567.0.html

I can successfully build the code with or without the patch, but I don't seem to be able to enable TrackPad of vaiox even for the basic functionalities such as pointer moves and clicks.
VoodooPS2Trackpad.kext successfully gets loaded. I inserted lots of IOLog messages to make sure the kext is started.
I tried (1) including the trackpad kext into your VoodooPS2Controller as a plugin and (2) replace VoodooPS2Controller I built with yours, but neighther of these works (Trackpad does not operate, the mouse cursor stays still, but Bluetooth mouse works fine under this situation and also keyboard is fine too).

However, with your VoodooPS2Contoller, my trackpad operates fine.
It simply seems that TrackPad driver included in the zip does not seem to work with vaiox trackpad for some reason. The trackpad in vaiox is the following one, so it sure is from ALPS though.
Bus 003 Device 002: ID 044e:3017 Alps Electric Co., Ltd
I am not familiar with apple's HID system, but it is not clear to me why VoodooPS2Mouse included in your VoodooPS2Controller generally works fine with any trackpad.
Also, VoodooPS2Trackpad.kext seems successfully built and loaded, but something is wrong and it does not operate my trackpad.

Do you think of any hint to resolve this? This is my first time building a kext so any help would be appreciated.
(sorry for asking questions regarding the laptop you do not have, but vaiop and vaiox seem very similar...)

[update]
Also, I want to enable WebCam too, but which kexts vaiop is using for its motioneye camera?
My vaiox has the following motioneye camera, but it is not enabled by default.
Bus 001 Device 004: ID 05ca:18b6 Ricoh Co., Ltd

In Topic: Snow Leopard on VAIO P(VGN-P90HS) working!

27 April 2010 - 06:16 PM

@ryuu123

I have a couple of questions for building kexts, esp. VoodooTrackpad.kext (patched for ALPS).
Can you tell me where you got VoodooPS2Controller source?
I suspect that there exist svn trees for all the voodoo sub projects, but so far I could not get to it.
Maybe I should spend more time searching for them, but if you know where (or how to) let me know.
I found the tree for chameleon, but it does not seem to include the other voodoo stuff.
Also which version of VoodooPS2Controller code did you compile into your kext?
I would like to match up trackpad.kext with your kext. And I need to know if you have changed anything in ps2controller for suspend or for vaiop/vaiox specific stuff.

I also try building your kexts, just to see how things get built. This is a newbie question, but for vaiop, we should set the target to i386 right? I am not familiar with atom much...
© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy