Re: Alps GlidePoint driver for synaptics.
David DEMELIER wrote: > Hello there, > > I noticed that for the moment there is no support for alps based > touchpads, is there anyone working on a driver for -CURRENT ? By "no support" do you mean that it does not work at all, even with moused? Or do you mean no support for custom features of the touchpad? I have a similar model on my Dell laptop and it works fine with moused for basic features. It's old enough though that it doesn't have any features that are not basic. :) Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Alps GlidePoint driver for synaptics.
Hello there, I noticed that for the moment there is no support for alps based touchpads, is there anyone working on a driver for -CURRENT ? This is my touchpad : I: Bus=0011 Vendor=0002 Product=0008 Version=7321 N: Name="AlpsPS/2 ALPS GlidePoint" P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input6 U: Uniq= H: Handlers=mouse2 event6 B: EV=f B: KEY=420 0 7 0 0 0 0 0 0 0 0 B: REL=3 B: ABS=103 Cheers, David. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Hi Eygene, I could only now test the new port and it works. Now it's just a matter of fine-tuning it (i.e. I'd like to increase the acceleration of the pointer) Thanks for the great job! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Cristian, good day. Thu, Feb 21, 2008 at 01:57:08AM +0200, Cristian KLEIN wrote: >> Yes, please, try the mentioned patch and report back ;)) > > Sorry for the really long delay. No problems ;)) > The patch works perfectly on my Fujitsu-Siemens V5545. Thanks for the report! Norikatsu already kindly committed my patch, so you can update your ports and rebuild Synaptics driver -- it should work too and you'll not miss the modifications. -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Eygene Ryabinkin wrote: Cristian, good day. Fri, Feb 08, 2008 at 10:32:51PM +0200, Cristian KLEIN wrote: Thank you very much for 'pinging'. :) As the driver synaptics driver din not change for month, I speculate there might have been a change in the Xorg API, especially related to sucking configuration options. No, I had found the first problem and sent the message to the list shortly after the 'ping' mail. It has the patch attached. If you had not received it, it is strange, but anyway, here is the URL http://lists.freebsd.org/pipermail/freebsd-hackers/2008-February/023272.html Make mistakenly thought that your Synaptics driver should be compiled for i386, not for amd64. Patch will change the situation back to normal. Is there any way I could help? Yes, please, try the mentioned patch and report back ;)) Sorry for the really long delay. The patch works perfectly on my Fujitsu-Siemens V5545. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Norikatsu, good day. Wed, Feb 20, 2008 at 02:34:17AM +0900, Norikatsu Shigemura wrote: > > Xorg server 1.4 already has "AllowEmptyInput", so Giulio and others > > who want to run only Synaptics driver, can add the string > > - > > Option "AllowEmptyInput" > > - > > to their "ServerFlags" section and see no automagically added devices. > > I've got it! I confidently committed these solutions! Thank you for the commit! I can only add that the "AllowEmptyInput" appeared in the xorg-server-1.3.99.0, dated 31-Jul-2007 (see http://xorg.freedesktop.org/releases/individual/xserver/). And FreeBSD port of xorg-server was updated from 1.2 to 1.4 at Thu Sep 13 19:44:55 2007: http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-servers/xorg-server/distinfo.diff?r1=1.7;r2=1.8 So maybe it is worth to mention in the pkg-message about old hack with the 'void' input device -- just in case someone will try to run new Synaptics driver with older xorg-server and problems will arise. > Thank you!! My pleasure! ;)) -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Hi Eygene. On Mon, 18 Feb 2008 21:23:24 +0300 Eygene Ryabinkin <[EMAIL PROTECTED]> wrote: > If you'll look at > > http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=blob;h=dbe158efc6e365cd5bd064d848df3a4f0c0d35f4;hb=43d9edd31e31b33b9da4a50d8ab05004881c8d5a;f=hw/xfree86/common/xf86Config.c#l1611 > you will see that server tries to add the mouse driver if there is > no drivers of type 'mouse' or 'void'. The hack with adding the "dummy" > input device with type "void" disables generation of default mouse > driver. This was the true hack and it was a bit beautified in > http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commit;h=ba9f5138fc32a7a7b97bcf941bc92751b7c6c2c0 > now there is a boolean option "AllowEmptyInput" that inhibits creation > of core mouse and keyboard in any case. Grrr orz > > So I don't know that it's > > correct to fix this problem by way of b. And, if x11-drivers/ > > xf86-input-void is not installed, that's solution will be crashed. > Xorg server 1.4 already has "AllowEmptyInput", so Giulio and others > who want to run only Synaptics driver, can add the string > - > Option "AllowEmptyInput" > - > to their "ServerFlags" section and see no automagically added devices. I've got it! I confidently committed these solutions! Thank you!! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: There is a better way that I had found while was answering to Norikatsu's letter: add the string - Option "AllowEmptyInput" - to your xorg.conf "ServerFlags" section and you should see no additional mouse devices and probably Synaptics mice will be alive. Ok, I'll try tomorrow... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Giulio, Mon, Feb 18, 2008 at 10:54:35PM +0100, Giulio Ferro wrote: > Eygene Ryabinkin wrote: >> Please, uncomment your 'Mouse1' device inside "ServerLayout", start >> moused and try again. The '' should disappear. >> And probably mices will start working. > > Ok, now I've uncommented both mouse1 and synaptics: > > InputDevice "Mouse1" "CorePointer" > InputDevice "Keyboard1" "CoreKeyboard" > InputDevice "Synaptics_Touchpad""CorePointer" > > > and the moused demon. > > Here's is what I get: > 1) The mouse pointer now moves Cool. > 2) The drag and drop with double click on the touchpad _doesn't_ work Never tried this feature myself. Will try it tomorrow on my notebook. Did it ever worked for you? > 3) Window scrolling with the touchpad _doesn't_ work (either horizontally or > vertically) Is something reported if you spawn 'xev' and try to scroll via touchpad while the pointer is upon the xev window? > I attach the log of the attempt. Seems like this is the old one: > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 18 15:46:59 2008 > [...] > (WW) : No Device specified, looking for one... > (II) : Setting Device option to "/dev/psm0" > (--) : Device: "/dev/psm0" > (==) : Protocol: "Auto" > (**) Option "AlwaysCore" > (**) : doesn't report core events > (==) : Emulate3Buttons, Emulate3Timeout: 50 > (**) : ZAxisMapping: buttons 4 and 5 > (**) : Buttons: 9 > (**) : Sensitivity: 1 > (II) evaluating device () > (II) XINPUT: Adding extended input device "" (type: MOUSE) > (II) evaluating device (Synaptics_Touchpad) > (II) XINPUT: Adding extended input device "Synaptics_Touchpad" (type: MOUSE) > (II) evaluating device (Keyboard1) > (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD) > Synaptics DeviceInit called > SynapticsCtrl called. > (II) : SetupAuto: hw.iftype is 3, hw.model is 13 > (II) : SetupAuto: protocol is SysMouse > (WW) fcntl(9, O_ASYNC): Inappropriate ioctl for device > Synaptics DeviceOn called > (EE) xf86OpenSerial: Cannot open device /dev/psm0 > Device busy. > (WW) Synaptics_Touchpad: cannot open input device > couldn't enable device 3 > > Fatal server error: > Caught signal 10. Server aborting > > Synaptics DeviceOff called -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Aargh, this is the funny thing: you have no devices that are handled by the 'mouse' driver. And Xorg automatically adds one. Please, uncomment your 'Mouse1' device inside "ServerLayout", start moused and try again. The '' should disappear. And probably mices will start working. It will be good to see Xorg.log from this attempt. Ok, now I've uncommented both mouse1 and synaptics: InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" InputDevice "Synaptics_Touchpad""CorePointer" and the moused demon. Here's is what I get: 1) The mouse pointer now moves 2) The drag and drop with double click on the touchpad _doesn't_ work 3) Window scrolling with the touchpad _doesn't_ work (either horizontally or vertically) I attach the log of the attempt. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-PRERELEASE amd64 Current Operating System: FreeBSD aurynmob2.giulioferro.it 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Wed Jan 30 22:06:30 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AURYNMOB2 amd64 Build Date: 18 February 2008 10:16:05AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 18 15:46:59 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Simple Layout" (**) |-->Screen "Screen 1" (0) (**) | |-->Monitor "My Monitor" (**) | |-->Device "* Generic VESA compatible" (**) |-->Input Device "Keyboard1" (**) |-->Input Device "Synaptics_Touchpad" (**) Option "DontVTSwitch" (**) Option "DontZap" (**) Option "DontZoom" (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/local/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/local/"). (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (==) RgbPath set to "/usr/local/share/X11/rgb" (==) ModulePath set to "/usr/local/lib/xorg/modules" (II) No default mouse found, adding one (**) |-->Input Device "" (II) Loader magic: 0x680ce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 104d,9016 rev 0c class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2a01 card , rev 0c class 06,04,00 hdr 01 (II) PCI: 00:1a:0: chip 8086,2834 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 104d,9016 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2841 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:2: chip 8086,2843 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2830 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2831 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,2832 card 1
Re: Synaptics Xorg driver for FreeBSD/amd64
Giulio, Roman, Mon, Feb 18, 2008 at 07:04:13PM +0300, Eygene Ryabinkin wrote: > Aargh, this is the funny thing: you have no devices that are handled > by the 'mouse' driver. And Xorg automatically adds one. > > Please, uncomment your 'Mouse1' device inside "ServerLayout", start > moused and try again. The '' should disappear. > And probably mices will start working. There is a better way that I had found while was answering to Norikatsu's letter: add the string - Option "AllowEmptyInput" - to your xorg.conf "ServerFlags" section and you should see no additional mouse devices and probably Synaptics mice will be alive. Roman, this concerns you too ;)) Please, try it if you prefer to use single pointer from touchpad. -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Norikatsu, good day. Tue, Feb 19, 2008 at 02:35:24AM +0900, Norikatsu Shigemura wrote: > Hi Eygene, thanks for your summary! You're welcome! > On Mon, 18 Feb 2008 19:04:13 +0300 > Eygene Ryabinkin <[EMAIL PROTECTED]> wrote: > > >> It seems to me that you have another mouse device called ' > >> pointer>' that uses "auto" protocol and finds your mouse at /dev/psm0 > > >> and being SysMouse. Can you show your full xorg.conf? > > > Sure, find it attached... > > Aargh, this is the funny thing: you have no devices that are handled > > by the 'mouse' driver. And Xorg automatically adds one. > > Please, uncomment your 'Mouse1' device inside "ServerLayout", start > > moused and try again. The '' should disappear. > > And probably mices will start working. > > It will be good to see Xorg.log from this attempt. > > I'm using x11-drivers/synaptics on FreeBSD/i386. I don't have > any problem which many people said. > > I have two questions: > > a. Anyone, do you install x11-drivers/xf86-input-void? > I didn't install x11-drivers/xf86-input-void. Personally, I am not using xf86-input-void, because I am using standard system mouse with synaptics touchpad, so I don't need 'void' input device. > b. If you install x11-drivers/xf86-input-void, please check > following setting. > > Section "InputDevice" > Identifier "dummy" > Driver "void" > EndSection > > I read source files of Xserver and void driver, but I didn't > understand these relations:-(. If you'll look at http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=blob;h=dbe158efc6e365cd5bd064d848df3a4f0c0d35f4;hb=43d9edd31e31b33b9da4a50d8ab05004881c8d5a;f=hw/xfree86/common/xf86Config.c#l1611 you will see that server tries to add the mouse driver if there is no drivers of type 'mouse' or 'void'. The hack with adding the "dummy" input device with type "void" disables generation of default mouse driver. This was the true hack and it was a bit beautified in http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commit;h=ba9f5138fc32a7a7b97bcf941bc92751b7c6c2c0 now there is a boolean option "AllowEmptyInput" that inhibits creation of core mouse and keyboard in any case. > So I don't know that it's > correct to fix this problem by way of b. And, if x11-drivers/ > xf86-input-void is not installed, that's solution will be crashed. Xorg server 1.4 already has "AllowEmptyInput", so Giulio and others who want to run only Synaptics driver, can add the string - Option "AllowEmptyInput" - to their "ServerFlags" section and see no automagically added devices. -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Hi Eygene, thanks for your summary! On Mon, 18 Feb 2008 19:04:13 +0300 Eygene Ryabinkin <[EMAIL PROTECTED]> wrote: > >> It seems to me that you have another mouse device called ' >> pointer>' that uses "auto" protocol and finds your mouse at /dev/psm0 > >> and being SysMouse. Can you show your full xorg.conf? > > Sure, find it attached... > Aargh, this is the funny thing: you have no devices that are handled > by the 'mouse' driver. And Xorg automatically adds one. > Please, uncomment your 'Mouse1' device inside "ServerLayout", start > moused and try again. The '' should disappear. > And probably mices will start working. > It will be good to see Xorg.log from this attempt. I'm using x11-drivers/synaptics on FreeBSD/i386. I don't have any problem which many people said. I have two questions: a. Anyone, do you install x11-drivers/xf86-input-void? I didn't install x11-drivers/xf86-input-void. b. If you install x11-drivers/xf86-input-void, please check following setting. Section "InputDevice" Identifier "dummy" Driver "void" EndSection I read source files of Xserver and void driver, but I didn't understand these relations:-(. So I don't know that it's correct to fix this problem by way of b. And, if x11-drivers/ xf86-input-void is not installed, that's solution will be crashed. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Mon, Feb 18, 2008 at 04:49:13PM +0100, Giulio Ferro wrote: > Eygene Ryabinkin wrote: >> Yes, the following lines are very suspicious: >> - >> - >> >> It seems to me that you have another mouse device called '> pointer>' that uses "auto" protocol and finds your mouse at /dev/psm0 >> and being SysMouse. Can you show your full xorg.conf? >> > > > Sure, find it attached... Aargh, this is the funny thing: you have no devices that are handled by the 'mouse' driver. And Xorg automatically adds one. Please, uncomment your 'Mouse1' device inside "ServerLayout", start moused and try again. The '' should disappear. And probably mices will start working. It will be good to see Xorg.log from this attempt. Thank you! -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Yes, the following lines are very suspicious: - - It seems to me that you have another mouse device called '' that uses "auto" protocol and finds your mouse at /dev/psm0 and being SysMouse. Can you show your full xorg.conf? Sure, find it attached... # File generated by xorgconfig. # # Copyright 2004 The X.Org Foundation # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of The X.Org Foundation shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from # The X.Org Foundation. # # ** # Refer to the xorg.conf(5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section "Module" # This loads the DBE extension module. Load"dbe" # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection "extmod" Option"omit xfree86-dga" # don't initialise the DGA extension EndSubSection # This loads the font modules #Load"type1" Load"freetype" #Load"xtt" # This loads the GLX module Load "glx" # This loads the DRI module Load "dri" Load"synaptics" EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. #RgbPath"/usr/local/share/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # FontPath "/usr/local/lib/X11/fonts/misc/" FontPath "/usr/local/lib/X11/fonts/TTF/" FontPath "/usr/local/lib/X11/fonts/OTF" FontPath "/usr/local/lib/X11/fonts/Type1/" FontPath "/usr/local/lib/X11/fonts/100dpi/" FontPath "/usr/local/lib/X11/fonts/75dpi/" FontPath "/usr/local/lib/X11/fonts/local/" #FontPath "/usr/local/lib/X11/fonts/Speedo/" #FontPath "/usr/local/lib/X11/fonts/TrueType/" #FontPath "/usr/local/lib/X11/fonts/freefont/" # The module search path. The default path is shown here. #ModulePath "/usr/local/lib/modules" EndSection # ** # Server flags section. # ** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #Option "NoTrapSignals" # Uncomment this to disable the VT switch sequence # (where n is 1 through 12). This allows clients to receive these key # events. Option "DontVTSwitch" # Uncomment this to disable the server abort sequence # This allows clients to re
Re: Synaptics Xorg driver for FreeBSD/amd64
Giulio, Mon, Feb 18, 2008 at 04:00:43PM +0100, Giulio Ferro wrote: > Eygene Ryabinkin wrote: >> And if you'll try >> 'InputDevice "Synaptics_Touchpad" "CorePointer" "SendCoreEvents"'? >> >> > Nothing changes, sorry... > >> If not, drop me a letter, I'll try to get the real hardware into >> my hands and test it. But this likely won't be done until the end >> of the week, sorry. >> > > Thanks again. I include the complete log of the xorg session, I hope it can > help you somehow. Yes, the following lines are very suspicious: - > (WW) : No Device specified, looking for one... > (II) : Setting Device option to "/dev/psm0" > (--) : Device: "/dev/psm0" > (==) : Protocol: "Auto" > (**) Option "AlwaysCore" > (**) : doesn't report core events > (==) : Emulate3Buttons, Emulate3Timeout: 50 > (**) : ZAxisMapping: buttons 4 and 5 > (**) : Buttons: 9 > (**) : Sensitivity: 1 > (II) evaluating device () > (II) XINPUT: Adding extended input device "" (type: MOUSE) > (II) evaluating device (Synaptics_Touchpad) > (II) XINPUT: Adding extended input device "Synaptics_Touchpad" (type: MOUSE) > (II) evaluating device (Keyboard1) > (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD) > Synaptics DeviceInit called > SynapticsCtrl called. > (II) : SetupAuto: hw.iftype is 3, hw.model is 13 > (II) : SetupAuto: protocol is SysMouse > (WW) fcntl(9, O_ASYNC): Inappropriate ioctl for device > Synaptics DeviceOn called > (EE) xf86OpenSerial: Cannot open device /dev/psm0 > Device busy. > (WW) Synaptics_Touchpad: cannot open input device > couldn't enable device 3 - It seems to me that you have another mouse device called '' that uses "auto" protocol and finds your mouse at /dev/psm0 and being SysMouse. Can you show your full xorg.conf? Thanks! -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
) MX[B]
[4] -1 0 0xfc006800 - 0xfc006fff (0x800) MX[B]E
[5] -1 0 0xfc005000 - 0xfc005fff (0x1000) MX[B]E
[6] -1 0 0xfc00 - 0xfc003fff (0x4000) MX[B]E
[7] -1 0 0xfc006000 - 0xfc0067ff (0x800) MX[B]E
[8] -1 0 0xfa00 - 0xfbff (0x200) MX[B]E
[9] -1 0 0xf600 - 0xf7ff (0x200) MX[B]E
[10] -1 0 0xfc304000 - 0xfc3047ff (0x800) MX[B]E
[11] -1 0 0xfc304c00 - 0xfc304fff (0x400) MX[B]E
[12] -1 0 0xfc30 - 0xfc303fff (0x4000) MX[B]E
[13] -1 0 0xfc304800 - 0xfc304bff (0x400) MX[B]E
[14] -1 0 0xcc00 - 0xcdff (0x200) MX[B](B)
[15] -1 0 0xd000 - 0xdfff (0x1000) MX[B](B)
[16] -1 0 0xce00 - 0xceff (0x100) MX[B](B)
[17] -1 0 0x - 0x (0x1) IX[B]
[18] -1 0 0x - 0x (0x1) IX[B]
[19] -1 0 0x3000 - 0x30ff (0x100) IX[B]E
[20] -1 0 0x1c00 - 0x1cff (0x100) IX[B]E
[21] -1 0 0x18c0 - 0x18df (0x20) IX[B]E
[22] -1 0 0x18b4 - 0x18b7 (0x4) IX[B]E
[23] -1 0 0x18e0 - 0x18e7 (0x8) IX[B]E
[24] -1 0 0x18e8 - 0x18ef (0x8) IX[B]E
[25] -1 0 0x18f0 - 0x18ff (0x10) IX[B]E
[26] -1 0 0x18a0 - 0x18af (0x10) IX[B]E
[27] -1 0 0x1880 - 0x189f (0x20) IX[B]E
[28] -1 0 0x1860 - 0x187f (0x20) IX[B]E
[29] -1 0 0x1840 - 0x185f (0x20) IX[B]E
[30] -1 0 0x1820 - 0x183f (0x20) IX[B]E
[31] -1 0 0x1800 - 0x181f (0x20) IX[B]E
[32] -1 0 0x2000 - 0x207f (0x80) IX[B](B)
(II) "extmod" will be loaded. This was enabled by default and also specified in
the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in
the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in
the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified
in the config file.
(II) "type1" will be loaded by default.
(II) "record" will be loaded by default.
(II) "dri" will be loaded. This was enabled by default and also specified in
the config file.
(II) LoadModule: "dbe"
(II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "freetype"
(II) Loading /usr/local/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.4.0, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX disabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "synaptics"
(II) Loading /usr/local/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "type1"
(II) Loading /usr/local/lib/xorg/modules/fonts//libtyp
Re: Synaptics Xorg driver for FreeBSD/amd64
Mon, Feb 18, 2008 at 02:49:00PM +0100, Giulio Ferro wrote: > Eygene Ryabinkin wrote: >> Please, try again if you have some spare time. > > Ok. Now the server starts, Good ;)) > but the mouse pointer isn't moving... Bad :(( > in the ServerLayout section I have this: >#InputDevice "Mouse1" "CorePointer" >InputDevice "Keyboard1" "CoreKeyboard" > InputDevice "Synaptics_Touchpad""CorePointer" And if you'll try 'InputDevice "Synaptics_Touchpad" "CorePointer" "SendCoreEvents"'? I have it in my Synaptics config @i386 and I vaguely recall that this was needed to enable the touchpad and USB mouse to work together. May be this will fix your problems. If not, drop me a letter, I'll try to get the real hardware into my hands and test it. But this likely won't be done until the end of the week, sorry. -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Please, try again if you have some spare time. Ok. Now the server starts, but the mouse pointer isn't moving... in the ServerLayout section I have this: #InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" InputDevice "Synaptics_Touchpad""CorePointer" and I didn't start the moused demon. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Giulio, good day. Long time ago, in December 2007, we discuissed the problem with Synaptics touchpad driver for FreeBSD in the freebsd-hackers list. I had corrected the problem and driver seems to work, but I need more testing with real hardware. I had opened the FreeBSD PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=120783 It will be great if you will be able to try the patch in the PR (I assume that you still have FreeBSD/amd64 and Xorg on some of your machines) and report the result either to the list or as the PR followup. Thank you! Hi Eygene, first of all thanks for your effort. Unfortunately I couldn't still get the synaptyc driver work on my laptop. Here's what I did: 1) I extracted the port driver with "make extract patch" 2) put your patch in /usr/ports/x11-drivers/synaptics/files (I named it "newpatch") 3) applied the patch with that directory with patch < newpatch 4) compiled the driver with make install clean 5) loaded the driver in /boot/loader.conf (as per pkg-message) 6) modified the /etc/X11/xorg.conf (//) 7) disabled the moused demon (//) When I launched startx the xorg server aborted with the same "No Device specified" I got the last time. I attach the complete log of the server. I hope it will be of help to you. Regards. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-PRERELEASE amd64 Current Operating System: FreeBSD aurynmob2.giulioferro.it 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Wed Jan 30 22:06:30 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AURYNMOB2 amd64 Build Date: 18 February 2008 10:16:05AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 18 13:23:34 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Simple Layout" (**) |-->Screen "Screen 1" (0) (**) | |-->Monitor "My Monitor" (**) | |-->Device "* Generic VESA compatible" (**) |-->Input Device "Keyboard1" (**) |-->Input Device "Synaptics_Touchpad" (**) Option "DontVTSwitch" (**) Option "DontZap" (**) Option "DontZoom" (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/local/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/local/"). (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (==) RgbPath set to "/usr/local/share/X11/rgb" (==) ModulePath set to "/usr/local/lib/xorg/modules" (II) No default mouse found, adding one (**) |-->Input Device "" (II) Loader magic: 0x680ce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 104d,9016 rev 0c class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2a01 card , rev 0c class 06,04,00 hdr 01 (II) PCI: 00:1a:0: chip 8086,2834 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 104d,9016 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f
Re: Synaptics Xorg driver for FreeBSD/amd64
Giulio, Mon, Feb 18, 2008 at 01:39:50PM +0100, Giulio Ferro wrote: > first of all thanks for your effort. No problems ;)) > Unfortunately I couldn't still get the synaptyc driver work on my laptop. > > Here's what I did: > 1) I extracted the port driver with "make extract patch" > 2) put your patch in /usr/ports/x11-drivers/synaptics/files (I named it > "newpatch") > 3) applied the patch with that directory with patch < newpatch No, the patch I had supplied is the patch-to-the-patch ;)) So you should 1) Do 'make clean' in the port's directory. 2) Apply the patch with 'patch -p1 < /path/to/the/supplied/patchfile'. 3) Build and install the port. Sorry, I was not clear enough on how to apply the modification. Please, try again if you have some spare time. Thanks! -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Cristian, good day. Fri, Feb 08, 2008 at 10:32:51PM +0200, Cristian KLEIN wrote: > Thank you very much for 'pinging'. :) As the driver synaptics driver din > not change for month, I speculate there might have been a change in the > Xorg API, especially related to sucking configuration options. No, I had found the first problem and sent the message to the list shortly after the 'ping' mail. It has the patch attached. If you had not received it, it is strange, but anyway, here is the URL http://lists.freebsd.org/pipermail/freebsd-hackers/2008-February/023272.html Make mistakenly thought that your Synaptics driver should be compiled for i386, not for amd64. Patch will change the situation back to normal. > Is there any way I could help? Yes, please, try the mentioned patch and report back ;)) -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Eygene Ryabinkin a scris: Cristian, good day. Wed, Jan 23, 2008 at 01:26:41PM +0200, [EMAIL PROTECTED] wrote: I just ran into the same problem. In xorg.conf I explicitly told the synaptics driver to use "psm" and "/dev/psm0", but the error message would suggest that it uses "event". Also, I tried to change the source code of the synaptics driver (synaptics.c) and hard-coded "psm" as the only driver, no matter what xorg.conf says. Synaptics still would not start, but this time complaining that no device was specified. Please note that I had "Device" in my xorg.conf, but the error suggests that the driver ignored it. Suppose I use the attached xorg.conf file, at some point, /var/log/Xorg.0.log shows the following error: (II) Synaptics touchpad driver version 0.14.6 (1406) Synaptics_Touchpad no synaptics event device found (checked 10 nodes) Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device (EE) PreInit failed for input device "Synaptics_Touchpad" (II) UnloadModule: "synaptics" As you said, it looks like synaptics is trying to use the "auto" protocol, although the configuration file tells it to use "psm". Now, if I put the attached patch in x11-drivers/synaptics/files, using the same xorg.conf, synaptics will fail like this: (II) Synaptics touchpad driver version 0.14.6 (1406) (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device (EE) PreInit failed for input device "Synaptics_Touchpad" (II) UnloadModule: "synaptics" It almost looks as if I have to hardcode the device too, because synaptics certainly ignores my options. This is a sort of 'ping' mail, sorry. To the point: I had reproduced the problem and will start looking into it once this message will fly from my mailserver. Stay tuned ;)) Thank you very much for 'pinging'. :) As the driver synaptics driver din not change for month, I speculate there might have been a change in the Xorg API, especially related to sucking configuration options. Is there any way I could help? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Me again. Mon, Feb 04, 2008 at 05:41:18PM +0300, Eygene Ryabinkin wrote: > This is a sort of 'ping' mail, sorry. To the point: I had reproduced > the problem and will start looking into it once this message will > fly from my mailserver. Stay tuned ;)) OK, things should be better with the attached patch. I was not able to fully test the resulting Synaptics driver, since I have no Synaptics beast at my amd64 machine ;)) But with the provided patch, my Synaptics driver tries to search for the psm device, as I told him, so, please, give it a try. Must be patched with 'patch -p1' and one should be in the port directory. -- Eygene >From 083c1be4c91da739436f2b1e509a96512ac05867 Mon Sep 17 00:00:00 2001 From: Eygene Ryabinkin <[EMAIL PROTECTED]> Date: Mon, 4 Feb 2008 19:17:43 +0300 Subject: [PATCH] Fix compilation at amd64 by overriding the ARCH variable properly. FreeBSD make sets ARCH variable to 'amd64' [1] and invokes GNU make. It inherits the ARCH variable and refuses to set it via ordinary '=' operator. So we must force ARCH assignments. [1] Try 'make -V ARCH' in the port directory. Signed-off-by: Eygene Ryabinkin <[EMAIL PROTECTED]> --- files/patch-Makefile |7 --- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/files/patch-Makefile b/files/patch-Makefile index 1ae3cbe..90870c5 100644 --- a/files/patch-Makefile +++ b/files/patch-Makefile @@ -1,5 +1,5 @@ Makefile.orig Sun Jul 16 00:58:26 2006 -+++ Makefile Sun Aug 13 10:47:35 2006 +--- Makefile.orig 2006-07-15 19:58:26.0 +0400 Makefile 2008-02-04 19:11:33.0 +0300 @@ -12,14 +12,14 @@ MANDIR = $(DESTDIR)$(PREFIX)/man @@ -8,7 +8,8 @@ + ARCH = $(shell uname -m) endif ifeq ($(ARCH),amd64) - ARCH = x86_64 +- ARCH = x86_64 ++ override ARCH = x86_64 endif ifeq ($(ARCH),x86_64) ARCH_DEFINES = -D__x86_64__ -D_XSERVER64 -- 1.5.3.8 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Cristian, good day. Wed, Jan 23, 2008 at 01:26:41PM +0200, [EMAIL PROTECTED] wrote: > >> I just ran into the same problem. In xorg.conf I explicitly told the > >> synaptics driver to use "psm" and "/dev/psm0", but the error message > >> would > >> suggest that it uses "event". > >> > >> Also, I tried to change the source code of the synaptics driver > >> (synaptics.c) and hard-coded "psm" as the only driver, no matter what > >> xorg.conf says. Synaptics still would not start, but this time > >> complaining > >> that no device was specified. Please note that I had "Device" in my > >> xorg.conf, but the error suggests that the driver ignored it. > > Suppose I use the attached xorg.conf file, at some point, > /var/log/Xorg.0.log shows the following error: > > (II) Synaptics touchpad driver version 0.14.6 (1406) > Synaptics_Touchpad no synaptics event device found (checked 10 nodes) > Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing > (EE) xf86OpenSerial: No Device specified. > Synaptics driver unable to open device > (EE) PreInit failed for input device "Synaptics_Touchpad" > (II) UnloadModule: "synaptics" > > As you said, it looks like synaptics is trying to use the "auto" protocol, > although the configuration file tells it to use "psm". > > Now, if I put the attached patch in x11-drivers/synaptics/files, using the > same xorg.conf, synaptics will fail like this: > > (II) Synaptics touchpad driver version 0.14.6 (1406) > (EE) xf86OpenSerial: No Device specified. > Synaptics driver unable to open device > (EE) PreInit failed for input device "Synaptics_Touchpad" > (II) UnloadModule: "synaptics" > > It almost looks as if I have to hardcode the device too, because synaptics > certainly ignores my options. This is a sort of 'ping' mail, sorry. To the point: I had reproduced the problem and will start looking into it once this message will fly from my mailserver. Stay tuned ;)) -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
> Cristian, good day. > > Mon, Jan 21, 2008 at 11:06:26PM +0200, Cristian KLEIN wrote: >> Eygene Ryabinkin wrote: >>> But what protocol is selected? From your Xorg log I assume that >>> it is either "event", "auto-dev" or not set at all. >> >> I just ran into the same problem. In xorg.conf I explicitly told the >> synaptics driver to use "psm" and "/dev/psm0", but the error message >> would >> suggest that it uses "event". >> >> Also, I tried to change the source code of the synaptics driver >> (synaptics.c) and hard-coded "psm" as the only driver, no matter what >> xorg.conf says. Synaptics still would not start, but this time >> complaining >> that no device was specified. Please note that I had "Device" in my >> xorg.conf, but the error suggests that the driver ignored it. > > Could you please provide your Xorg configuration file and the Xorg > logs for the run when you had hardcoded psm driver. It will also > be good to see the modified Synaptics driver source file. > > And the version and platform for your FreeBSD is? I don't know why I keep forgetting to include essential information. Sorry. cristi:~# uname -a FreeBSD hades 7.0-RC1 FreeBSD 7.0-RC1 #0: Mon Dec 24 10:10:07 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 cristi:~# pkg_info | grep xorg-server xorg-server-1.4_3,1 X.Org X server and related programs cristi:~# pkg_info | grep synaptics synaptics-0.14.6_2 The Synaptics touchpad X driver Suppose I use the attached xorg.conf file, at some point, /var/log/Xorg.0.log shows the following error: (II) Synaptics touchpad driver version 0.14.6 (1406) Synaptics_Touchpad no synaptics event device found (checked 10 nodes) Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device (EE) PreInit failed for input device "Synaptics_Touchpad" (II) UnloadModule: "synaptics" As you said, it looks like synaptics is trying to use the "auto" protocol, although the configuration file tells it to use "psm". Now, if I put the attached patch in x11-drivers/synaptics/files, using the same xorg.conf, synaptics will fail like this: (II) Synaptics touchpad driver version 0.14.6 (1406) (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device (EE) PreInit failed for input device "Synaptics_Touchpad" (II) UnloadModule: "synaptics" It almost looks as if I have to hardcode the device too, because synaptics certainly ignores my options. Any ideas? xorg.conf Description: Binary data patch-test2 Description: Binary data ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Cristian, good day. Mon, Jan 21, 2008 at 11:06:26PM +0200, Cristian KLEIN wrote: > Eygene Ryabinkin wrote: >> But what protocol is selected? From your Xorg log I assume that >> it is either "event", "auto-dev" or not set at all. > > I just ran into the same problem. In xorg.conf I explicitly told the > synaptics driver to use "psm" and "/dev/psm0", but the error message would > suggest that it uses "event". > > Also, I tried to change the source code of the synaptics driver > (synaptics.c) and hard-coded "psm" as the only driver, no matter what > xorg.conf says. Synaptics still would not start, but this time complaining > that no device was specified. Please note that I had "Device" in my > xorg.conf, but the error suggests that the driver ignored it. Could you please provide your Xorg configuration file and the Xorg logs for the run when you had hardcoded psm driver. It will also be good to see the modified Synaptics driver source file. And the version and platform for your FreeBSD is? > It almost seems that no matter what options I pass to synaptics, it does > not receive them. Is it possible that Xorg's option retrieval functions > have changed making the (relatively) old synaptics unusable? Maybe, but I am running Synaptics driver on my laptop for years and it works now without any problems. My laptop is i386, it runs FreeBSD 7-PRERELEASE, Xorg server 1.4_3,1 and synaptics 0.14.6_2. If you'll provide the information, I will try to look at the problem, but I expect to start investigations next week. -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Hi everybody, Eygene Ryabinkin wrote: Giulio, good day. Wed, Dec 12, 2007 at 05:50:21PM +0100, Giulio Ferro wrote: Eygene Ryabinkin wrote: -- (II) Synaptics touchpad driver version 0.14.6 (1406) Synaptics_Touchpad no synaptics event device found (checked 10 nodes) Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device And what if you'll specify - Option "Device""/dev/psm0" Option "Protocol" "psm" - in the xorg.conf? I assume that you have your synaptics touchpad as the /dev/psm0. Yes, I have the touchpad as /dev/psm0 But what protocol is selected? From your Xorg log I assume that it is either "event", "auto-dev" or not set at all. I just ran into the same problem. In xorg.conf I explicitly told the synaptics driver to use "psm" and "/dev/psm0", but the error message would suggest that it uses "event". Also, I tried to change the source code of the synaptics driver (synaptics.c) and hard-coded "psm" as the only driver, no matter what xorg.conf says. Synaptics still would not start, but this time complaining that no device was specified. Please note that I had "Device" in my xorg.conf, but the error suggests that the driver ignored it. It almost seems that no matter what options I pass to synaptics, it does not receive them. Is it possible that Xorg's option retrieval functions have changed making the (relatively) old synaptics unusable? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Giulio, good day. Wed, Dec 12, 2007 at 05:50:21PM +0100, Giulio Ferro wrote: > Eygene Ryabinkin wrote: >>> -- >>> (II) Synaptics touchpad driver version 0.14.6 (1406) >>> Synaptics_Touchpad no synaptics event device found (checked 10 nodes) >>> Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing >>> (EE) xf86OpenSerial: No Device specified. >>> Synaptics driver unable to open device >>> >> >> And what if you'll specify >> - >> Option "Device""/dev/psm0" >> Option "Protocol" "psm" >> - >> in the xorg.conf? I assume that you have your synaptics touchpad >> as the /dev/psm0. >> > > Yes, I have the touchpad as /dev/psm0 But what protocol is selected? From your Xorg log I assume that it is either "event", "auto-dev" or not set at all. > Unfortunately those settings are already specified in /e tc/X11/xorg.conf > in the > section "InputDevice" for the touchpad. > > If you look in the /usr/ports/x11-drivers/synaptics/pkg-message it's all > already there Yes, but I am not sure what you have in your /etc/X11/xorg.conf, sorry. Could you please show your configuration? Wed, Dec 26, 2007 at 06:21:04PM +0100, Giulio Ferro wrote: > Anyway I'm not sure this is the right way to do thinks. I'd dearly like to > listen from > the maintainer, maybe it can shed some light on the /dev/input/event > issue... Though I am not maintainer, but jugding from the source, your Synaptics driver tries to use the "event" protocol instead of "psm". -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
I have a USB mouse and I want to disable my touchpad. I am going to resend my post, I had originally posted to "freebsd-hardware" but now I am going to post to "freebsd-hackers" On Wed, 26 Dec 2007, Giulio Ferro wrote: Donnie wrote: On Dec 12, 10:51 am, Giulio Ferro <[EMAIL PROTECTED]> wrote: Unfortunately those settings are already specified in /e tc/X11/xorg.conf in the section "InputDevice" for thetouchpad. If you look in the /usr/ports/x11-drivers/synaptics/pkg-message it's all already there I had the same problem, but finally happened on this solution: despite what the pkg-message says, in xorg.conf you have to specify both a non-existent mouse and the touchpad, in addition to following all the other pkg-message directions. So, my xorg.conf has: Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "AlwaysCore" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Synaptics_Touchpad" "CorePointer" EndSection ### Note that touchpad MUST be CorePointer and non-existent mouse must be AlwaysCore ### Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" EndSection Section "InputDevice" Identifier"Synaptics_Touchpad" Driver"synaptics" Option"SendCoreEvents" Option"Device" "/dev/psm0" Option"Protocol""psm" Option"TouchpadOff" "0" Option"LeftEdge" "1700" Option"RightEdge" "5300" Option"TopEdge" "1700" Option"BottomEdge""4200" Option"FingerLow" "25" Option"FingerHigh" "30" Option"MaxTapTime" "180" Option"MaxTapMove" "220" Option"VertScrollDelta" "100" Option"MinSpeed""0.06" Option"MaxSpeed""0.06" Option"AccelFactor" "0.0010" Option"HorizScrollDelta""100" Option"UpDownScrolling" "on" Option"UpDownRepeat" "on" Option"LeftRightScrolling""on" Option"LeftRightRepeat" "on" Option"SHMConfig" "on" EndSection Good luck! -- Donnie Doesn't work, sorry. The server starts, but the mouse pointer isn't moving. Anyway I'm not sure this is the right way to do thinks. I'd dearly like to listen from the maintainer, maybe it can shed some light on the /dev/input/event issue... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" *--* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *--* ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Donnie wrote: On Dec 12, 10:51 am, Giulio Ferro <[EMAIL PROTECTED]> wrote: Unfortunately those settings are already specified in /e tc/X11/xorg.conf in the section "InputDevice" for thetouchpad. If you look in the /usr/ports/x11-drivers/synaptics/pkg-message it's all already there I had the same problem, but finally happened on this solution: despite what the pkg-message says, in xorg.conf you have to specify both a non-existent mouse and the touchpad, in addition to following all the other pkg-message directions. So, my xorg.conf has: Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "AlwaysCore" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Synaptics_Touchpad" "CorePointer" EndSection ### Note that touchpad MUST be CorePointer and non-existent mouse must be AlwaysCore ### Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" EndSection Section "InputDevice" Identifier"Synaptics_Touchpad" Driver"synaptics" Option"SendCoreEvents" Option"Device" "/dev/psm0" Option"Protocol""psm" Option"TouchpadOff" "0" Option"LeftEdge" "1700" Option"RightEdge" "5300" Option"TopEdge" "1700" Option"BottomEdge""4200" Option"FingerLow" "25" Option"FingerHigh" "30" Option"MaxTapTime" "180" Option"MaxTapMove" "220" Option"VertScrollDelta" "100" Option"MinSpeed""0.06" Option"MaxSpeed""0.06" Option"AccelFactor" "0.0010" Option"HorizScrollDelta""100" Option"UpDownScrolling" "on" Option"UpDownRepeat" "on" Option"LeftRightScrolling""on" Option"LeftRightRepeat" "on" Option"SHMConfig" "on" EndSection Good luck! -- Donnie Doesn't work, sorry. The server starts, but the mouse pointer isn't moving. Anyway I'm not sure this is the right way to do thinks. I'd dearly like to listen from the maintainer, maybe it can shed some light on the /dev/input/event issue... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Eygene Ryabinkin wrote: Giulio, good day. Good day. -- (II) Synaptics touchpad driver version 0.14.6 (1406) Synaptics_Touchpad no synaptics event device found (checked 10 nodes) Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device And what if you'll specify - Option "Device""/dev/psm0" Option "Protocol" "psm" - in the xorg.conf? I assume that you have your synaptics touchpad as the /dev/psm0. Yes, I have the touchpad as /dev/psm0 Unfortunately those settings are already specified in /e tc/X11/xorg.conf in the section "InputDevice" for the touchpad. If you look in the /usr/ports/x11-drivers/synaptics/pkg-message it's all already there ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics
Giulio, good day. Sat, Dec 08, 2007 at 12:55:35PM +0100, Giulio Ferro wrote: > I just wanted to report that the synaptics touchpad driver > (/usr/ports/x11-drivers/synaptics) > doesn't work in my configuration: > freebsd 7 beta4 - amd64 - synaptics-0.14.6_2 > > I set hw.psm.synaptics_support=1 in /boot/loader.conf, > disable moused, change /etc/X11/xorg.conf according to the instructions > in pkg-messages. > > Unfortunately every time I try to start X the following error occurs: > > -- > (II) Synaptics touchpad driver version 0.14.6 (1406) > Synaptics_Touchpad no synaptics event device found (checked 10 nodes) > Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing > (EE) xf86OpenSerial: No Device specified. > Synaptics driver unable to open device And what if you'll specify - Option "Device""/dev/psm0" Option "Protocol" "psm" - in the xorg.conf? I assume that you have your synaptics touchpad as the /dev/psm0. -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Synaptics
Hi, I just wanted to report that the synaptics touchpad driver (/usr/ports/x11-drivers/synaptics) doesn't work in my configuration: freebsd 7 beta4 - amd64 - synaptics-0.14.6_2 I set hw.psm.synaptics_support=1 in /boot/loader.conf, disable moused, change /etc/X11/xorg.conf according to the instructions in pkg-messages. Unfortunately every time I try to start X the following error occurs: -- (II) Synaptics touchpad driver version 0.14.6 (1406) Synaptics_Touchpad no synaptics event device found (checked 10 nodes) Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device (EE) PreInit failed for input device "Synaptics_Touchpad" (II) UnloadModule: "synaptics" Fatal server error: Caught signal 11. Server aborting -- Any idea is appreciated. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PSM Synaptics Touchpad Options
I've read quite a few posts regarding tunable psm settings to affect values such as PSM_TAP_THRESHOLD, PSM_TAP_TIMEOUT, etc., which should work with synaptics support. I've been unable to get any suggested sysctls or loader.conf tunables to affect my touchpad on 5.4-RELEASE. I've found that I can add appropriate lines to sys/conf/options to allow me to set PSM_TAP_THRESHOLD and similar values in my kernel config file, finally allowing me to disable the tap=click effect. Is there already a better solution which allows changes on running systems, such as sysctl based settings, or should I toss a send-pr in with the sys/conf/options patch to allow setting of these values in kernel config? -john psm0: flags 0x1000 irq 12 on atkbdc0 psm0: model Synaptics Touchpad, device ID 0 PSM_TAP_THRESHOLD opt_psm.h options PSM_TAP_THRESHOLD=150 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics touchpad extendid support.
> * Make moused map up/down into buttons 4/5: > > moused -m 4=2 -m 5=4 -p /dev/psm0 -t auto > > * Make X do the rest. From XF86Config (for XFree 4.2): > >Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "Auto" > Option "Device" "/dev/sysmouse" > Option "Resolution" "100" > Option "Emulate3Buttons" > Option "Buttons" "5" >EndSection This works perfectly. Thanks! >This makes X handle emulation of the middle button. Hmm... looks >like there already is a default ZAxisMapping. If you have >problems, try adding > > Option "ZAxisMapping" "4 5" Curiously, if I add this option I kill the up/down buttons altogether: xev shows no activity when they're pressed. Thanks Marcin and hope this can make it to the main tree soon! - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Synaptics touchpad extendid support.
First, many thanks to Marcin. On Sun, 5 Jan 2003, Rahul Siddharthan wrote: > Marcin Dalecki wrote: > > Here is my first cut at support for the Synaptics touchpads, which are > > commonly used on notebooks. Contrary to the default "Windows > > installation mode" those devices come up at boot, this is enabling > > full support for all buttons present on the device and works nicely > > with moused together. > > I just tried it. Couple of issues: Me too. > 1. The "speed" of the pointer on the screen is way faster now. I > corrected that with some XF86Config options. Easy enough to fix with scaling. To me the pointer also feels slightly "detached" or lagging, as if attached to my finger with a rubberband... Some kind of filtering, or an artifact from the absolute->relative conversion, perhaps. Oh, well, it works well enough. > 2. The pad has 4 buttons; left and right work as before. In between, > there are a small up and down button. Now the up button acts as the > middle button (button 3?) -- ie I can paste with it. The down button > still does nothing. I tried playing with the moused parameters and > the XF86Config ZAxisMapping settings, to no avail. > > 3. Earlier, tapping on the touchpad would emulate a left click. It > no longer does anything (not sure whether that's good or bad). I used to hate tapping, but now when it is gone, I can't decide whether I want it or not :-) A look in the specs show that tap processing has to be done entirely in software when the touchpad is in this mode, i.e. not just a matter of twiddling a bit. > What I'd like is to emulate 3 buttons with simultaneous left-right > clicking, as before; have the "up" button behave like scrolling a > mousewheel up; and have the "down" button behave like scrolling a > mousewheel down. I thought the > Option "ZAxisMapping" "4 5" > in XF86Config, and > moused -m 4=3 -m 5=4 > would do it. But no luck (though the above moused options do stop the > up button from acting like a middle button). > > Any ideas, anyone? I just made it work (-current, XFree86 4.2.1). Like this: The buttons are 1/3 (left/right) and 4/2 (up/down). Looks like moused is incapable of both mapping physical button 2 to something and at the same time emulating a middle button as left+right (with the -3 flag). But the following works in X: * Make moused map up/down into buttons 4/5: moused -m 4=2 -m 5=4 -p /dev/psm0 -t auto * Make X do the rest. From XF86Config (for XFree 4.2): Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/sysmouse" Option "Resolution" "100" Option "Emulate3Buttons" Option "Buttons" "5" EndSection This makes X handle emulation of the middle button. Hmm... looks like there already is a default ZAxisMapping. If you have problems, try adding Option "ZAxisMapping" "4 5" Now I have to decide whether I want this, or if I want a real middle button. Decisions, decisions... $.02, /Mikko To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Synaptics touchpad extendid support.
Rahul Siddharthan wrote: Marcin Dalecki wrote: Here is my first cut at support for the Synaptics touchpads, 2. The pad has 4 buttons; left and right work as before. In between, there are a small up and down button. Now the up button acts as the middle button (button 3?) -- ie I can paste with it. The down button still does nothing. Well for certain the down button does something in esp. it is posting button 4 events. Watch out xev please - you should see it there. Actually, I don't. If I run moused without button options, ie moused -t auto -d /dev/psm0 I see the up button but not the down button. If I run either moused -t auto -d /dev/psm0 -3 or moused -t auto -d /dev/psm0 -m 4=2 -m 5=4 I see neither the up button nor the down button in xev. Please take a look at your dmesg. Here is what I get reported: Synaptics Touchpad: model: 1 firmware ver.: 4.6 rot180: Yes portrait: No sensor: 18 hardware: 47 newABS: Yes capPen: No simpleCmd: Yes geometry: 1 capExtended:Yes capSleep: Yes capFourButtons: Yes capMultiFinger: Yes capPalmDetect: Yes psm0: irq 12 on atkbdc0 psm0: model Synaptics TouchPad, device ID 0 orm0: at iomem 0xc-0xcbfff on isa0 What I'd like is to emulate 3 buttons with simultaneous left-right clicking, as before; have the "up" button behave like scrolling a mousewheel up; and have the "down" button behave like scrolling a mousewheel down. I thought the Option "ZAxisMapping" "4 5" Option Buttons 5? Yes, that was there. in XF86Config, and moused -m 4=3 -m 5=4 would do it. But no luck (though the above moused options do stop the up button from acting like a middle button). moused -m 4=2 -m 5=4 should do it. No luck, see above. Perhaps my hardware isn't a Synaptics touchpad? (although it gets detected as one with your patch). It's a Compaq Presario 1200 around a year old. This is very unlikely. Becouse in case it wouldn't be a synaptics would make it very very unlikely to do anything at all after the detection :-). And you get at the middle button. If you like you could please try to enable the following: #if 0 -log(LOG_DEBUG, "psmintr: %02x %02x %02x %02x %02x %02x\n", - sc->ipacket[0], sc->ipacket[1], sc->ipacket[2], - sc->ipacket[3], sc->ipacket[4], sc->ipacket[5]); + log(LOG_DEBUG, "psmintr: %02x %02x %02x %02x %02x %02x\n", + sc->ipacket[0], sc->ipacket[1], sc->ipacket[2], + sc->ipacket[3], sc->ipacket[4], sc->ipacket[5]); #endif debugging code in the psm.c driver code to see whatever there is some kind of button reporting at all if you press the down button. And I would recommand that you take a look at the documentation at www.synaptics.com. Yes they actually provide *full documentation* on the web! There are minor differences in the packet format for older firmware revisions as well. So plase compare your dmesg with what I have reported above. Have fun! -- Marcin Dalecki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Synaptics touchpad extendid support.
Marcin Dalecki wrote: > >>Here is my first cut at support for the Synaptics touchpads, > >2. The pad has 4 buttons; left and right work as before. In between, > >there are a small up and down button. Now the up button acts as the > >middle button (button 3?) -- ie I can paste with it. The down button > >still does nothing. > Well for certain the down button does something in esp. it is posting > button 4 events. Watch out xev please - you should see it there. Actually, I don't. If I run moused without button options, ie moused -t auto -d /dev/psm0 I see the up button but not the down button. If I run either moused -t auto -d /dev/psm0 -3 or moused -t auto -d /dev/psm0 -m 4=2 -m 5=4 I see neither the up button nor the down button in xev. > >What I'd like is to emulate 3 buttons with simultaneous left-right > >clicking, as before; have the "up" button behave like scrolling a > >mousewheel up; and have the "down" button behave like scrolling a > >mousewheel down. I thought the > > Option "ZAxisMapping" "4 5" > Option Buttons 5? Yes, that was there. > >in XF86Config, and > > moused -m 4=3 -m 5=4 > >would do it. But no luck (though the above moused options do stop the > >up button from acting like a middle button). > > moused -m 4=2 -m 5=4 should do it. No luck, see above. Perhaps my hardware isn't a Synaptics touchpad? (although it gets detected as one with your patch). It's a Compaq Presario 1200 around a year old. Thanks - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Synaptics touchpad extendid support.
Rahul Siddharthan wrote: Marcin Dalecki wrote: Here is my first cut at support for the Synaptics touchpads, which are commonly used on notebooks. Contrary to the default "Windows installation mode" those devices come up at boot, this is enabling full support for all buttons present on the device and works nicely with moused together. I just tried it. Couple of issues: 1. The "speed" of the pointer on the screen is way faster now. I corrected that with some XF86Config options. Yes that was intentional, since there are two ways to scale the speed, namely moused and XFree. However the speed you can see is already scaled down by an significant amount anyway. Unfortunately the current sysmouse dosn't understand a witt about absolute mouse coordinates as far as I understand the code... 2. The pad has 4 buttons; left and right work as before. In between, there are a small up and down button. Now the up button acts as the middle button (button 3?) -- ie I can paste with it. The down button still does nothing. I tried playing with the moused parameters and the XF86Config ZAxisMapping settings, to no avail. Well for certain the down button does something in esp. it is posting button 4 events. Watch out xev please - you should see it there. Having a middle button was the reaon per se I did this hack in first place, so this choice of numbering is likely here to stay. 3. Earlier, tapping on the touchpad would emulate a left click. It no longer does anything (not sure whether that's good or bad). Yes this kind of functionality is still not there, since it would involve quite a lot of code, which I didn't find apriopriate to place in kernel space. What I'd like is to emulate 3 buttons with simultaneous left-right clicking, as before; have the "up" button behave like scrolling a mousewheel up; and have the "down" button behave like scrolling a mousewheel down. I thought the Option "ZAxisMapping" "4 5" Option Buttons 5? in XF86Config, and moused -m 4=3 -m 5=4 would do it. But no luck (though the above moused options do stop the up button from acting like a middle button). moused -m 4=2 -m 5=4 should do it. left is 1 upis 2 right is 3 down is 4 Any ideas, anyone? Yes. The next cut should define a custom SYNAPTICS mouse protocol and move the whole logics out of the kernel to moused. There it should be possible to implement all the extendid features one desires without too much hassle. And without in esp. frequent reboots due to kernel crashing :-). Thanks I'm glad this thingee works not just for my own hardware. Would you dare to report the firmware version on your system. Rahul -- Marcin Dalecki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Synaptics touchpad extendid support.
Marcin Dalecki wrote: > Here is my first cut at support for the Synaptics touchpads, which are > commonly used on notebooks. Contrary to the default "Windows > installation mode" those devices come up at boot, this is enabling > full support for all buttons present on the device and works nicely > with moused together. I just tried it. Couple of issues: 1. The "speed" of the pointer on the screen is way faster now. I corrected that with some XF86Config options. 2. The pad has 4 buttons; left and right work as before. In between, there are a small up and down button. Now the up button acts as the middle button (button 3?) -- ie I can paste with it. The down button still does nothing. I tried playing with the moused parameters and the XF86Config ZAxisMapping settings, to no avail. 3. Earlier, tapping on the touchpad would emulate a left click. It no longer does anything (not sure whether that's good or bad). What I'd like is to emulate 3 buttons with simultaneous left-right clicking, as before; have the "up" button behave like scrolling a mousewheel up; and have the "down" button behave like scrolling a mousewheel down. I thought the Option "ZAxisMapping" "4 5" in XF86Config, and moused -m 4=3 -m 5=4 would do it. But no luck (though the above moused options do stop the up button from acting like a middle button). Any ideas, anyone? Thanks Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Synaptics touchpad extendid support.
Here is my first cut at support for the Synaptics touchpads, which
are commonly used on notebooks. Contrary to the default "Windows installation mode"
those devices come up at boot, this is enabling full support for all buttons
present on the device and works nicely with moused together.
Have fun!
--
Marcin Dalecki
diff -urN src-old/sys/isa/psm.c src/sys/isa/psm.c
--- src-old/sys/isa/psm.c Tue Dec 31 00:35:19 2002
+++ src/sys/isa/psm.c Tue Dec 31 01:05:35 2002
@@ -277,6 +277,7 @@
static probefunc_t enable_4dplus;
static probefunc_t enable_mmanplus;
static probefunc_t enable_versapad;
+static probefunc_t enable_synaptics;
static int tame_mouse(struct psm_softc *, mousestatus_t *, unsigned char *);
static struct {
@@ -309,6 +310,8 @@
0x80, MOUSE_PS2_PACKETSIZE, enable_kmouse, },
{ MOUSE_MODEL_VERSAPAD,/* Interlink electronics VersaPad */
0xe8, MOUSE_PS2VERSA_PACKETSIZE, enable_versapad, },
+{ MOUSE_MODEL_SYNAPTICS, /* Synaptics TouchPad */
+ 0xc0, MOUSE_PS2SYNAP_PACKETSIZE, enable_synaptics, },
{ MOUSE_MODEL_GENERIC,
0xc0, MOUSE_PS2_PACKETSIZE, NULL, },
};
@@ -570,6 +573,7 @@
{ MOUSE_MODEL_EXPLORER,"IntelliMouse Explorer" },
{ MOUSE_MODEL_4D, "4D Mouse" },
{ MOUSE_MODEL_4DPLUS, "4D+ Mouse" },
+ { MOUSE_MODEL_SYNAPTICS,"Synaptics TouchPad" },
{ MOUSE_MODEL_GENERIC, "Generic PS/2 mouse" },
{ MOUSE_MODEL_UNKNOWN, NULL },
};
@@ -1964,7 +1968,7 @@
* the table to turn PS/2 mouse button bits (MOUSE_PS2_BUTTON?DOWN)
* into `mousestatus' button bits (MOUSE_BUTTON?DOWN).
*/
-static int butmap[8] = {
+static const int butmap[8] = {
0,
MOUSE_BUTTON1DOWN,
MOUSE_BUTTON3DOWN,
@@ -1974,7 +1978,7 @@
MOUSE_BUTTON2DOWN | MOUSE_BUTTON3DOWN,
MOUSE_BUTTON1DOWN | MOUSE_BUTTON2DOWN | MOUSE_BUTTON3DOWN
};
-static int butmap_versapad[8] = {
+static const int butmap_versapad[8] = {
0,
MOUSE_BUTTON3DOWN,
0,
@@ -1987,18 +1991,18 @@
register struct psm_softc *sc = arg;
mousestatus_t ms;
struct timeval tv;
-int x, y, z;
+int x, y, z, w;
int c;
int l;
int x0, y0;
/* read until there is nothing to read */
while((c = read_aux_data_no_wait(sc->kbdc)) != -1) {
-
+
/* discard the byte if the device is not open */
if ((sc->state & PSM_OPEN) == 0)
continue;
-
+
getmicrouptime(&tv);
if ((sc->inputbytes > 0) && timevalcmp(&tv, &sc->inputtimeout, >)) {
log(LOG_DEBUG, "psmintr: delay too long; resetting byte count\n");
@@ -2014,9 +2018,9 @@
continue;
#if 0
-log(LOG_DEBUG, "psmintr: %02x %02x %02x %02x %02x %02x\n",
- sc->ipacket[0], sc->ipacket[1], sc->ipacket[2],
- sc->ipacket[3], sc->ipacket[4], sc->ipacket[5]);
+ log(LOG_DEBUG, "psmintr: %02x %02x %02x %02x %02x %02x\n",
+ sc->ipacket[0], sc->ipacket[1], sc->ipacket[2],
+ sc->ipacket[3], sc->ipacket[4], sc->ipacket[5]);
#endif
c = sc->ipacket[0];
@@ -2320,6 +2324,80 @@
}
break;
+ case MOUSE_MODEL_SYNAPTICS:
+ /* TouchPad PS/2 absolute mode message format
+*
+* Bits:7 6 5 4 3 2 1 0 (LSB)
+*
+* ipacket[0]: 1 0 W3 W2 0 W1 R L
+* ipacket[1]: Yb Ya Y9 Y8 Xb Xa X9 X8
+* ipacket[2]: Z7 Z6 Z5 Z4 Z3 Z2 Z1 Z0
+* ipacket[3]: 1 1 Yc Xc 0 W0 D U
+* ipacket[4]: X7 X6 X5 X4 X3 X2 X1 X0
+* ipacket[5]: Y7 Y6 Y5 Y4 Y3 Y2 Y1 Y0
+*
+* Legend:
+* L: left physical mouse button
+* R: right physical mouse button
+* D: down button
+* U: up button
+* W: "wrist" value
+* X: x position
+* Y: x position
+* Z: pressure
+*
+* Absolute reportable limits:0 - 6143.
+* Typical bezel limites: 1472 - 5472.
+* Typical edge marings: 1632 - 5312.
+*/
+
+ /* Sanity check for out of sync packets. */
+ if ((sc->ipacket[0] & 0xc8) != 0x80 || (sc->ipacket[3] & 0xc8) != 0xc0)
+ continue;
+
+ ms.button = 0;
+ x = y = x0 = y0 = 0;
+
+ /* pressure */
+ z = sc->ipacket[2];
+ w = ((sc->ipacket[0] & 0x30) >> 2) |
+ ((sc->ipacket[0] & 0x04) >> 1) |
Re: PS/2 Mice device - synaptics touch pad.
Daniel O'Connor wrote: On Sat, 2002-11-30 at 02:54, Marcin Dalecki wrote: Looking further I discovered that the writing method is filled with a global nowrite() function. What should I do about it: 1. Just provide the trivial psmwrite() augmenting kernel level function, thus presering the higher level driver for XFree? 2. Move everything in to the kernel space?! (The driver isn't exactly small due to many features like border detection and so on...) I think number 1 is probably best, IMHO it should go into moused, but given the way the moused code is written that is pretty tough :( OK. I'm going for nr 1. augmented with moused. This will have the advantage of making it globally abstracted on the system no matter whatever XFree86 or not. Also if you follow step 1 you will have to provide some way of telling the psm device not to validate the input stream, because otherwise it will barf on the absolute packets. (I have done a little tinkering, but the moused/psm code makes my head explode) Yes the psm code is a bit rotten. But it's nothing in comparision to stuff I got used too under Linux ;-). I have looked at the 2 "other" BSE systems as well. OpenBSD has a bit of nice code separation and reordering but less functionality there. Where NetBSD did hide the PS/2 mice code I couldn't find out. Right now I have augmented the current psm.c with the device detection code for Synaptics touch pads: one sends a magic command sequence and gets a magic reply containing model info and stuff. Thus the tinkering in psm.c will certainly not affect any other PS/2 device type. psm0: current command byte:0045 HERE WE GO psm0: found Synaptics touch pad psm0: irq 12 on atkbdc0 psm0: model Synaptics touch pad, device ID 0-00, 2 buttons psm0: config:, flags:, packet size:3 psm0: syncmask:c0, syncbits:00 orm0: at iomem 0xc-0xcbfff on isa0 Now it's time to elaborate on device type printing and to write a psmwrite for this type of devices... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PS/2 Mice device - synaptics touch pad.
On Sat, 2002-11-30 at 02:54, Marcin Dalecki wrote: > Looking further I discovered that the writing method is filled with a > global nowrite() function. > > What should I do about it: > > 1. Just provide the trivial psmwrite() augmenting kernel level function, thus > presering the higher level driver for XFree? > > 2. Move everything in to the kernel space?! (The driver isn't exactly > small due to many features like border detection and so on...) I think number 1 is probably best, IMHO it should go into moused, but given the way the moused code is written that is pretty tough :( Also if you follow step 1 you will have to provide some way of telling the psm device not to validate the input stream, because otherwise it will barf on the absolute packets. (I have done a little tinkering, but the moused/psm code makes my head explode) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
PS/2 Mice device - synaptics touch pad.
Hello everybody. Well currently right now I'm trying to make all the buttons (4 of them) of my synaptics touch pad to work under BSD. Despite beeing embedid in a notebook, this device is physically attached to the PS/2 port. It knows about two operating modes - relative, aka normal PS/2 mouse protocoll, basically just usable for windows installs, - absolute, which gives full access to all buttons and not just two as well as absolute coordinates of the pressing point on the pad. I have already an XFree86 input device driver for it, which is working fine if run under Linux. Under FreeBSD the driver doesn't work as expected. A little bit of digging turned up that writing to the /dev/psm0 device fails. But I certainly *have* to write to the device to put it in to absolute mode. Looking further I discovered that the writing method is filled with a global nowrite() function. What should I do about it: 1. Just provide the trivial psmwrite() augmenting kernel level function, thus presering the higher level driver for XFree? 2. Move everything in to the kernel space?! (The driver isn't exactly small due to many features like border detection and so on...) -- Marcin Dalecki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: i-Buddie 4: Synaptics touch pad FreeBSD support?]
On Fri, 2002-09-27 at 16:54, Guido Van Hoecke wrote: > The windoze driver offers a set of extra features which I found useful > and which I would appreciate on a FreeBSD box: > - configurable touch behaviour > - edge motion > - scrolling > - button actions (including virtual btns supplied by the 4 corners) > I'm very willing to supply more info on these features. > > I have no idea whether any of these are supplied by the tpconfig stuff. > The only feature I found any mention of in that package, is the ability > to disable the 'tap to click'. But maybe that is just a lack of > documentation. None of those features are possible without putting the device in absolute mode :( I should just get off my lazy ass and get it to work :) If anyone is interested the specs are readily available from the synaptics web site. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: i-Buddie 4: Synaptics touch pad FreeBSD support?]
Stephen Montgomery-Smith wrote: > If you want to get tpconfig to work (so that you can customise various > features of the touchpad), I have a PR that will allow you to do this. > It is a combination of a hack to the kernel, and a port of tpconfig. > Look at > http://www.freebsd.org/cgi/query-pr.cgi?pr=24299 > http://www.freebsd.org/cgi/query-pr.cgi?pr=20352 I am afraid that I do not have (yet) enough FreeBSD experience to grasp the impact of these. I am already very pleased that I can use the standard ps/2 mouse driver to use the touch pad. I had to use moused_enable="NO" in my /etc/rc.conf and use Option "Protocol" "auto" Option "Device" "/dev/psm0" Option "Emulate3Buttons" to have the mouse working properly, and was happy that this also took care of the touch pad. The windoze driver offers a set of extra features which I found useful and which I would appreciate on a FreeBSD box: - configurable touch behaviour - edge motion - scrolling - button actions (including virtual btns supplied by the 4 corners) I'm very willing to supply more info on these features. I have no idea whether any of these are supplied by the tpconfig stuff. The only feature I found any mention of in that package, is the ability to disable the 'tap to click'. But maybe that is just a lack of documentation. -- Guido Van Hoecke <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: i-Buddie 4: Synaptics touch pad FreeBSD support?]
If you want to get tpconfig to work (so that you can customise various features of the touchpad), I have a PR that will allow you to do this. It is a combination of a hack to the kernel, and a port of tpconfig. Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=24299 http://www.freebsd.org/cgi/query-pr.cgi?pr=20352 -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: i-Buddie 4: Synaptics touch pad FreeBSD support?]
On 27 Sep 2002, Daniel O'Connor wrote: > You can put them into a special mode which allows you to do more stuff > with them (get absolute position and pressure information and the like). I'd love to see FreeBSD get theremin support. ;-) [ Orthogonally cool is using syntapics touchpad output to generate entropy for /dev/random. ] Brandon D. Valentine -- http://www.geekpunk.net [EMAIL PROTECTED] ++[>++<-]>[<++>-]<.>[>+<-]>[<+>-]<+.+++..++ +.>>+[<++>-]<++.<<+++.>.+++.--..>+. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: i-Buddie 4: Synaptics touch pad FreeBSD support?]
On Fri, 2002-09-27 at 09:01, Brandon D. Valentine wrote: > This is just a laptop with a touchpad. Chances are pretty good it's > supported out of the box by FreeBSD's moused and even better than if you > can't get sysmouse support that there's a driver in XFree86 for it. The > linux driver is completely irrelevant not to mention the fact that I > can't seem to download it in order to see what they thought was so > special about their trackpad it was worthy of its own driver. Most of > them just act like PS/2 mice. You can put them into a special mode which allows you to do more stuff with them (get absolute position and pressure information and the like). There is a driver for X which does this, but it doesn't work on FreeBSD because you can't tell our PSM driver to move asside (it insists on sanity checking packets). I got part way through hacking moused to grok my Synaptics touch pad, but I got stuck because once it's in absolute mode the psm driver doesn't like the packets it outputs and resets it :( IMHO moused should do most of the work that psm now does, but I don't have any patches yet :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: i-Buddie 4: Synaptics touch pad FreeBSD support?]
Brandon D. Valentine wrote: > This is just a laptop with a touchpad. Chances are pretty good it's > supported out of the box by FreeBSD's moused and > ... > Most of them just act like PS/2 mice. Thanks, you're right: it works like a charm on the test notebook; I had never thought to try it that way. Guido. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [Fwd: i-Buddie 4: Synaptics touch pad FreeBSD support?]
On Fri, 27 Sep 2002, Guido Van Hoecke wrote: > So I went to see at http://www.synaptics.com/support/downloads.cfm and > found a pointer to a linux 'tpconfig' touch pad driver available at > http://compass.com/synaptics/ which has not yet been ported to FreeBSD. This is just a laptop with a touchpad. Chances are pretty good it's supported out of the box by FreeBSD's moused and even better than if you can't get sysmouse support that there's a driver in XFree86 for it. The linux driver is completely irrelevant not to mention the fact that I can't seem to download it in order to see what they thought was so special about their trackpad it was worthy of its own driver. Most of them just act like PS/2 mice. Molehill !Mountain Brandon D. Valentine -- http://www.geekpunk.net [EMAIL PROTECTED] ++[>++<-]>[<++>-]<.>[>+<-]>[<+>-]<+.+++..++ +.>>+[<++>-]<++.<<+++.>.+++.--..>+. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
[Fwd: i-Buddie 4: Synaptics touch pad FreeBSD support?]
I hope it is acceptable to send this also to the hackers list, due to
the absence of traffic about touch pads on the questions list:
Original Message
Subject: i-Buddie 4: Synaptics touch pad FreeBSD support?
Date: Fri, 27 Sep 2002 00:40:48 +0200
From: Guido Van Hoecke <[EMAIL PROTECTED]>
Newsgroups: gmane.os.freebsd.questions
I am experimenting with FreeBSD to be prepared when my new i-Buddie 4
arrives. (Specs at http://desknote.biz/sub/spec-i-buddie4.htm). I wonder
whether anybody has any experience with this new 'desknote' computer.
I specifically would like support for the Synaptics touch pad, but did
not find much in the FreeBSD documentation, nor in the ports collection.
So I went to see at http://www.synaptics.com/support/downloads.cfm and
found a pointer to a linux 'tpconfig' touch pad driver available at
http://compass.com/synaptics/ which has not yet been ported to FreeBSD.
So I tried to use this on my little FreeBSD testbox:
~/tpconfig-3.1.3 # ./configure
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for fcntl.h... (cached) yes
checking for unistd.h... (cached) yes
updating cache ./config.cache
creating ./config.status
creating Makefile
~/tpconfig-3.1.3 # ./make
"Makefile", line 254: Need an operator
make: fatal errors encountered -- cannot continue
~/tpconfig-3.1.3 #
I used vim to add line numbers in the Makefile and copypasted the result:
1 # Generated automatically from Makefile.in by configure.
2 # Makefile.in generated automatically by automake 1.4 from Makefile.am
3
4 # Copyright (C) 1994, 1995-8, 1999 Free Software Foundation, Inc.
5 # This Makefile.in is free software; the Free Software Foundation
6 # gives unlimited permission to copy and/or distribute it,
7 # with or without modifications, as long as this notice is preserved.
8
9 # This program is distributed in the hope that it will be useful,
10 # but WITHOUT ANY WARRANTY, to the extent permitted by law; without
11 # even the implied warranty of MERCHANTABILITY or FITNESS FOR A
12 # PARTICULAR PURPOSE.
13
14 # Source: $Id: Makefile.am,v 1.2 2000/11/05 21:50:25 cph Exp $
15
16
17 SHELL = /bin/sh
18
19 srcdir = .
20 top_srcdir = .
21 prefix = /usr/local
22 exec_prefix = ${prefix}
23
24 bindir = ${exec_prefix}/bin
25 sbindir = ${exec_prefix}/sbin
26 libexecdir = ${exec_prefix}/libexec
27 datadir = ${prefix}/share
28 sysconfdir = ${prefix}/etc
29 sharedstatedir = ${prefix}/com
30 localstatedir = ${prefix}/var
31 libdir = ${exec_prefix}/lib
32 infodir = ${prefix}/info
33 mandir = ${prefix}/man
34 includedir = ${prefix}/include
35 oldincludedir = /usr/include
36
37 DESTDIR =
38
39 pkgdatadir = $(datadir)/tpconfig
40 pkglibdir = $(libdir)/tpconfig
41 pkgincludedir = $(includedir)/tpconfig
42
43 top_builddir = .
44
45 ACLOCAL = aclocal
46 AUTOCONF = autoconf
47 AUTOMAKE = automake
48 AUTOHEADER = autoheader
49
50 INSTALL = /usr/bin/install -c
51 INSTALL_PROGRAM = ${INSTALL} $(AM_INSTALL_PROGRAM_FLAGS)
52 INSTALL_DATA = ${INSTALL} -m 644
53 INSTALL_SCRIPT = ${INSTALL_PROGRAM}
54 transform = s,x,x,
55
56 NORMAL_INSTALL = :
57 PRE_INSTALL = :
58 POST_INSTALL = :
59 NORMAL_UNINSTALL = :
60 PRE_UNINSTALL = :
61 POST_UNINSTALL = :
62 CC = gcc
63 MAKEINFO = makeinfo
64 PACKAGE = tpconfig
65 VERSION = 3.1.3
66
67 AUTOMAKE_OPTIONS = "VERSION=1.2"
68 bin_PROGRAMS = tpconfig
69 tpconfig_SOURCES = tpconfig.c synaptics.c ALPS.c utils.c
70 MAINTAINERCLEANFILES = Makefile.in configure aclocal.m4
install-sh
missing mkinstalldirs COPYING INSTALL
71
72 # don't know why this is being omitted...
73 EXTRA_DIST = configure
74 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
75 mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
76 CONFIG_CLEAN_FILES =
77 PROGRAMS = $(bin_PROGRAMS)
78
79
80 DEFS = -DPACKAGE=\"tpconfig\" -DVERSION=\"3.1.3\" -DHAVE_FCNTL_H=
