The call usbkbm_set_protocol(usbkbmd, SET_BOOT_PROTOCOL) in usbkbm was added in the the CR 6724581, which was used to support the apple NEW macbook pro's internal keyboard. The boot_protocol setting doesn't apply to the old macbook. The two setting (first report_procotol in hid, and then boot_protocol in usbkbm) make the old macbook hid controller confused.
The fix for this looks like to add a workaround for the old macbook in usbkbm according to the vendor_id/device_id. If so, what is the device_id of your macbook? Regards, Strony Frank van der Linden : > I found what causes this. > > To make the keyboard work on some later Macbook Pros, the usbkbm code > now explicitly sets the protocol to the keyboard "boot protocol". > > Apparently, this confuses the combined keyboard/trackpad controller in > my MacBook, and makes it switch to some strange mode for the mouse part. > > I removed the call in usbkbm.c, and now both the keyboard and internal > mouse work fine. > > I can't positively say that this is the cause of the problem for all > older MacBooks. The one in the bugreport was apparently in "raw mode". > Mine didn't seem to have that problem. It did not send 64-byte messages, > but 8-byte messages (as advertised). But the messages were screwed up. > > It'd be good to find a way to initialize all these Macbook controllers > so that they report the right trackpad data. > > - Frank > _______________________________________________ > driver-usb mailing list > driver-usb at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/driver-usb >
