Auto-detecting vmmouse

[Arto Pekkanen]

Awesome!

Thomas Hellstrom kirjoitti 29.08.2016 16:29:
> Hi!
> 
> It's on my todo list, unless someone beats me to it.
> 
> /Thomas
> 
> On 08/29/2016 02:18 PM, Arto Pekkanen wrote:
>> Is anybody working on a proper fix for this issue?
>> 
>> Having to patch and recompile X.org is not a proper fix.
>> 
>> Anthony Jenkins via freebsd-x11 kirjoitti 23.08.2016 21:36:
>>> On 08/23/2016 04:43 AM, Thomas Hellstrom wrote:
>>>> Hi!
>>>> 
>>>> With the advent of the devd-managed Xorg device auto-detection, the
>>>> automatic ability of loading the "vmmouse" driver instead of the
>>>> "mouse"
>>>> driver isn't there anymore.
>>>> 
>>>> Previously, with the hal-driven detection, a utility called
>>>> "vmmouse_detect" was run and the HAL suggested xorg driver was set
>>>> accordingly depending on the result of "vmmouse_detect".
>>>> 
>>>> So I was planning to restore this functionality somehow and when 
>>>> it's
>>>> working kindly ask whoever is responsible to automatically install
>>>> xf86-video-vmware and xf86-input-vmmouse whenever xorg is installed.
>>>> 
>>>> Unfortunately I have trouble finding documentation that describes
>>>> how to
>>>> set the xorg input driver name for a mouse device detected by devd. 
>>>> The
>>>> input driver name needs to be set based on the return code of the
>>>> "vmmouse_detect" utility.
>>>> 
>>>> Any help pointing me to a preferred way of doing this would be 
>>>> greatly
>>>> appreciated.
>>> Basically you will have to modify device_added(const char *line) in
>>> config/devd.c to create a new InputOption "object" and set the 
>>> "driver"
>>> option to "vmmouse" (assuming that's the driver name) using
>>> input_option_new().
>>> 
>>> I did my own implementation of config/devd.c (I think others have 
>>> also,
>>> but I think they're all basically similar) different from the one
>>> currently in x11-servers/xorg-server/, it uses a function table to 
>>> call
>>> a function for a given const char *line passed to device_added() to 
>>> make
>>> a decision about what driver to attach.
>>> 
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ScoobiFreeBSD_freebsd-2Dports_blob_xorg-2Dsynaptics_x11-2Dservers_xorg-2Dserver_files_patch-2Dconfig-5Fdevd.c&d=CwIDaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=vpukPkBtpoNQp2IUKuFviOmPNYWVKmen3Jeeu55zmEA&m=ZEdVZ4WvkFVmPYSSdr8gDNQJRcT_xdLT-5UC-W-fmZU&s=g5msGfDG8M69w7ZTtETKfDoFGdcUmNBceXVgnBz9O4U&e=
>>> 
>>> You'd add an entry to hw_types[] for the device node created by 
>>> devd(8),
>>> adding a new function to fill in the InputOption object depending on
>>> information from the system.
>>> 
>>> Anthony
>>> 
>>>> Thanks,
>>>> 
>>>> Thomas Hellström, VMWare
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> freebsd-x11 at freebsd.org mailing list
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freebsd.org_mailman_listinfo_freebsd-2Dx11&d=CwIDaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=vpukPkBtpoNQp2IUKuFviOmPNYWVKmen3Jeeu55zmEA&m=ZEdVZ4WvkFVmPYSSdr8gDNQJRcT_xdLT-5UC-W-fmZU&s=k6D2evC_l0AqKGT8WjctdDnIRoih2Gki6cEchxlsd_E&e=
>>>> To unsubscribe, send any mail to 
>>>> "freebsd-x11-unsubscribe at freebsd.org"
>> 

-- 
Arto Pekkanen