Date: Sun, 13 Mar 2005 13:50:28 -0800 From: "Loren M. Lang" <lorenl@alzatex.com> To: Mikko Ty?l?j?rvi <mbsd@pacbell.net> Cc: FreeBSD Mailing list <freebsd-questions@freebsd.org> Subject: Re: Synaptics Touchpad driver Message-ID: <20050313215028.GN18080@alzatex.com> In-Reply-To: <20050313104455.A54006@sotec.home> References: <20050313074746.GA17624@alzatex.com> <20050313104455.A54006@sotec.home>
next in thread | previous in thread | raw e-mail | index | archive | help
--jnYfR+Q8IWTs8BNa
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Mar 13, 2005 at 10:48:46AM -0800, Mikko Ty?l?j?rvi wrote:
>=20
> Hi,
>=20
> On Sat, 12 Mar 2005, Loren M. Lang wrote:
>=20
> >It seems that FreeBSD 5.3 now has support in the kernel for the
> >synaptics touchpad that my laptop has. Right now it's just running as a
> >normal mouse, it looks like the support is disabled by default. In
> >isa/psm.c, I can see the synaptics support in there, but it's disabled
> >unless hw.psm.synaptics_support is set to 1. My question is how do I
> >set it to one? It's setup as a TUNABLE_INT, but there is no sysctl for
> >it. Does it only appear on boot?
>=20
> It is not a sysctl, it is a kernel tunable. You control it from the
> boot loader, for example by putting
>=20
> hw.psm.synaptics_support=3D"1"
>=20
> into /boot/loader.conf. See loader.conf(5) and /boot/defaults/loader.conf
> for more information.
That's what I was wondering and I tried to set it in the loader, but I
haven't noticed a difference. No added sysctls to tune the touchpad, no
kernel messages showing anything obvious, the touchpad still acts the
same, etc. Also, I looked through the kernel sources for other
TUNABLE_INT's:
=2E..
/usr/src/sys/cam/scsi/scsi_all.c: TUNABLE_INT_FETCH("kern.cam.scsi_de=
lay", &delay);
/usr/src/sys/cam/scsi/scsi_cd.c:TUNABLE_INT("kern.cam.cd.changer.min_busy_s=
econds", &changer_min_busy_seconds);
/usr/src/sys/cam/scsi/scsi_cd.c:TUNABLE_INT("kern.cam.cd.changer.max_busy_s=
econds", &changer_max_busy_seconds);
/usr/src/sys/cam/scsi/scsi_cd.c: TUNABLE_INT_FETCH(tmpstr, &softc->m=
inimum_command_size);
/usr/src/sys/cam/scsi/scsi_da.c:TUNABLE_INT("kern.cam.da.retry_count", &da_=
retry_count);
/usr/src/sys/cam/scsi/scsi_da.c:TUNABLE_INT("kern.cam.da.default_timeout", =
&da_default_timeout);
/usr/src/sys/cam/scsi/scsi_da.c: TUNABLE_INT_FETCH(tmpstr, &softc->m=
inimum_cmd_size);
=2E..
sysctls -a|grep cam:
kern.cam.scsi_delay: 15000
kern.cam.cd.changer.min_busy_seconds: 5
kern.cam.cd.changer.max_busy_seconds: 15
kern.cam.da.retry_count: 4
kern.cam.da.default_timeout: 60
It looks like all these tunables are also sysctls.
>=20
> $.02,
> /Mikko
--=20
I sense much NT in you.
NT leads to Bluescreen.
Bluescreen leads to downtime.
Downtime leads to suffering.
NT is the path to the darkside.
Powerful Unix is.
Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc
Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2
=20
--jnYfR+Q8IWTs8BNa
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFCNLWkbTXoRwEYo9IRAhIvAJ9IBPI8bF0rVZRgX5eFyjsDnmnKIwCfXN0+
+daInZppReBjBU+dprbOTWg=
=zJPc
-----END PGP SIGNATURE-----
--jnYfR+Q8IWTs8BNa--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050313215028.GN18080>