New TouchPad driver for E6520 / ALPS

[bmp152]

@bisk. Thanks for attempting to look up those DevIds. I can't seem to find much on my system either.

 

I was googling around a bit for the DevIds and found a link to another alps.c source code:  http://www.emmestech.com/linux/downloads/alps.c

static const struct alps_model_info alps_model_data[] = {
    { { 0x32, 0x02, 0x14 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },    /* Toshiba Salellite Pro M10 */
    { { 0x33, 0x02, 0x0a },    0x00, ALPS_PROTO_V1, 0x88, 0xf8, 0 },                /* UMAX-530T */
    { { 0x53, 0x02, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x53, 0x02, 0x14 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x60, 0x03, 0xc8 }, 0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },                /* HP ze1115 */
    { { 0x63, 0x02, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x63, 0x02, 0x14 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x63, 0x02, 0x28 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_FW_BK_2 },        /* Fujitsu Siemens S6010 */
    { { 0x63, 0x02, 0x3c },    0x00, ALPS_PROTO_V2, 0x8f, 0x8f, ALPS_WHEEL },            /* Toshiba Satellite S2400-103 */
    { { 0x63, 0x02, 0x50 },    0x00, ALPS_PROTO_V2, 0xef, 0xef, ALPS_FW_BK_1 },        /* NEC Versa L320 */
    { { 0x63, 0x02, 0x64 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x63, 0x03, 0xc8 }, 0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },    /* Dell Latitude D800 */
    { { 0x73, 0x00, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_DUALPOINT },        /* ThinkPad R61 8918-5QG */
    { { 0x73, 0x02, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, 0 },
    { { 0x73, 0x02, 0x14 },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_FW_BK_2 },        /* Ahtec Laptop */
    { { 0x20, 0x02, 0x0e },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },    /* XXX */
    { { 0x22, 0x02, 0x0a },    0x00, ALPS_PROTO_V2, 0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },
    { { 0x22, 0x02, 0x14 }, 0x00, ALPS_PROTO_V2, 0xff, 0xff, ALPS_PASS | ALPS_DUALPOINT },    /* Dell Latitude D600 */
    /* Dell Latitude E5500, E6400, E6500, Precision M4400 */
    { { 0x62, 0x02, 0x14 }, 0x00, ALPS_PROTO_V2, 0xcf, 0xcf,
        ALPS_PASS | ALPS_DUALPOINT | ALPS_PS2_INTERLEAVED },
    { { 0x73, 0x02, 0x50 }, 0x00, ALPS_PROTO_V2, 0xcf, 0xcf, ALPS_FOUR_BUTTONS },        /* Dell Vostro 1400 */
    { { 0x52, 0x01, 0x14 }, 0x00, ALPS_PROTO_V2, 0xff, 0xff,
        ALPS_PASS | ALPS_DUALPOINT | ALPS_PS2_INTERLEAVED },                /* Toshiba Tecra A11-11L */
    { { 0x73, 0x02, 0x64 },    0x9b, ALPS_PROTO_V3, 0x8f, 0x8f, ALPS_DUALPOINT },
    { { 0x73, 0x02, 0x64 },    0x9d, ALPS_PROTO_V3, 0x8f, 0x8f, ALPS_DUALPOINT },
    { { 0x73, 0x02, 0x64 },    0x8a, ALPS_PROTO_V4, 0x8f, 0x8f, 0 },
    { { 0x73, 0x03, 0x0a },    0x1d, ALPS_PROTO_V5, 0x8f, 0x8f, ALPS_DUALPOINT },        /* Dell Latitude E6430 */
    { { 0x73, 0x03, 0x50 },    0x0d, ALPS_PROTO_V6, 0xc8, 0xc8, 0 },                /* Dell Inspiron N5110 */
    { { 0x73, 0x03, 0x50 },    0x02, ALPS_PROTO_V6, 0xc8, 0xc8, 0 },                /* Dell Inspiron 17R 7720 */
};

The last 2 lines seem to provide a definition for 1 of the device codes we see during boot: 0x73, 0x03, 0x50. However, there appears to be no reference for the 0x73, 0x02, 0x02 device id. Perhaps that second 0x02 in the "Dell Inspiron 17R 7720" line indicates such?

 

I'm not sure if any of this helps to compile the new alps code, but I thought I'd pass it along to somebody smarter than me! Thanks again for your interest and hard work, whenever you get the chance. Enjoy the holiday.

[npjohnson]

Ugh. I recompiled the kext from the source, but after changing the SDK to 10.9, the kext refused to recompile, I had forgotten how long it had been since

I had delt with kexts, In the newest version of xcode, how to you compile the finished project?!?! I think I have 3 finger touch integrated (Likely buggy) and put in the Device IDs that I could. Is Bpedman still around? 3 months ago he made a commit and left some ideas, but I would love to see how he would've integrated it.

[bmp152]

Awesome! Thanks for all of your hard work...looking forward to testing the finished product once its compiled.

[Bronxteck]

try building as 64 bit. new Xcode has issues compiling 32 bit.

[npjohnson]

:0......................

 

No!!!!

 

I had gotten the two finger scrolling jumpy-ness fixed, and tried to integrate some of the code from the three finger touch synaptics version, but then disaster struck.

 

I installed PDA net to try to get mobile tethering. Now my Hackintosh wont boot. It gets to something called "{nspace handler), Anyone know of a fix?

 

If not... I have to restore from TimeMachine on Monday, and that would suck.

[Bronxteck]

tried booting with -x? hopefully it will get you back to desktop so you can undo whatever pda net did

[npjohnson]

Nope. -x -v -f  - s And all form of other flags didn't get it booting. Time Machine on Mon. It is. Thank you for the suggestion. Actually. -s got me to a prompt... anyway to undo recent changes from a #root prompt? Or is there a way to start the desktop from single user mode?

[Bronxteck]

if in -s exit then exit again should get to desktop if things are still functional or you can reinstall os over existing. it should preserve the data. if you knew what PDA did or installed you could remove it in -s terminal using terminal commands. that might involve dissecting the app/package to see what it contains. if it is a driver lets say you could remove them from s/l/e then do a touch s/l/e then boot with -f -v. you would have to first /mount -uw / at the -s prompt like it states to have user writable uw permissions to the drive.

[bisk]

Yep, I second that.  Assuming you have another Mac, use Pacifist to inspect the contents of that PDA net package and then just remove the kext(s) it installed from SLE while in single user mode.  Interesting that booting in safe mode doesn't suppress loading of the problematic kext.  Hope that your troubles are only being caused by a newly introduced kext !

[bisk]

Bronxteck,

 

When you say "if in -s exit then exit again should get to desktop ..."

 

Are you saying that it's possible to pop into graphics mode from single user mode w/o rebooting ?

 

That is to say by simply terminating the boot console ?