Re: pkg 1.5.0 is out
On 14 апр. 2015 г., at 23:05, Baptiste Daroussin b...@freebsd.org wrote: Final pkg 1.5.0 has been released. Thank a lot for working on pkg! For pkg 1.6.0 among other things and depending on the time, here is what we do plan to work on: - please add here you personal ideas What I really miss a lot is support for package profiles: an ability to build the same port with different OPTIONs combination. For example: minimal nginx version; nginx version with passenger module (for puppet server) nginx version with some other rare options turned on for custom application. Right now I achieve this with manually renaming /var/db/ports/*/options files and some manipulations in /usr/ports/packages/All. But a framework to automatically handle this would be very useful. Thanks. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Jenkins build is back to normal : FreeBSD_HEAD #2665
See https://jenkins.freebsd.org/job/FreeBSD_HEAD/2665/changes ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg 1.5.0 is out
On Sun, Apr 19, 2015 at 02:22:15PM +0300, Dmitry Sivachenko wrote: On 14 апр. 2015 г., at 23:05, Baptiste Daroussin b...@freebsd.org wrote: Final pkg 1.5.0 has been released. Thank a lot for working on pkg! For pkg 1.6.0 among other things and depending on the time, here is what we do plan to work on: - please add here you personal ideas What I really miss a lot is support for package profiles: an ability to build the same port with different OPTIONs combination. For example: minimal nginx version; nginx version with passenger module (for puppet server) nginx version with some other rare options turned on for custom application. Right now I achieve this with manually renaming /var/db/ports/*/options files and some manipulations in /usr/ports/packages/All. But a framework to automatically handle this would be very useful. Thanks. This is already supported on pkg side, the work needs to be done in ports side, what you call profiles, I usually call it flavours but that is the same. Dependencies made on provides/requires allows to handle dependencies in this: For example A can depend on nginx (whatever profile): so it requires nginx B can only depend on nginx-passenger: so it requires nginx-passenger nginx itself provides: nginx nginx-passenger provides: nginx and nginx-passenger that should do what you want unfortunatly that mean both nginx nginx-passenger both have one origin: www/nginx and this will break portupgrade/portmaster/tinderbox/poudriere (I can easily make poudriere friendly for that but I can't for the others). So most of the work is now on ports land (and maybe a couple of bug fixes in pkg) Best regards, Bapt pgp5yADg8sSKe.pgp Description: PGP signature
Jenkins build became unstable: FreeBSD_HEAD-tests2 #948
See https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/948/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Request for Help] Reducing gcc 4.9 compilation warnings
On 18 April 2015 at 11:12, Craig Rodrigues rodr...@freebsd.org wrote: Hi, After the latest commits by members of freebsd-toolchain@ , I have managed to compile latest CURRENT world and GENERIC kernel on amd64 with an gcc 4.9 external toolchain by doing: pkg install devel/amd64-xtoolchain-gcc cd /usr/src sed -i -e 's/boot2//' sys/boot/i386/Makefile make buildworld CROSS_TOOLCHAIN=amd64-gcc NO_WERROR=yes WERROR= make buildkernel CROSS_TOOLCHAIN=amd64-gcc NO_WERROR=yes WERROR= It was necessary to skip boot2 from building because of errors reported here: https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-April/001658.html The boot2 compilation errors still need to be worked on. However, most other things compile with warnings. If folks are interested in looking at the warnings, you can see them here: https://jenkins.freebsd.org/job/FreeBSD_HEAD_amd64_gcc4.9/warnings17 Please look at these warnings, and if you see places to patch the code to eliminate the warnings, please submit patches and commit them if you can. Some time ago I tried to do something similar, but with gcc4.6 instead of gcc4.9. The vast majority of warnings (1548) are unused-but-set-variable and it may be worthwhile to just silence this warning, at least at low WARNS levels. It has caught real errors but is quite noisy and can cause quite a bit of churn. inline (count 515) is generally pure noise, and I think we should disable it. It can be helpful to find certain types of performance optimizations, but it should be opt-in. strict-aliasing (154) are likely all real bugs of some form. Very few exist in contrib code, and it would be good to fix them. Warning (111) seem to be a mix of warnings, but mostly in contrib code. maybe-uninitialized (111) is often noisy, and in a spot check were all false positives. deprecated-declarations (22) is all in contrib code Many of these are useful though and I've already fixed a few of the bugs reported. Perhaps it would be useful to do a second run of this, but with a modified share/mk to silence the most useless of these warnings? -- Eitan Adler ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
AUTOFS and NFS not playing together nicely
At the risk of being dubbed insane, here goes: On five FreeBSD 10.1-RELEASE-p9 production servers autofs(5) is enabled and working as advertised. On the same servers nfs v3 clients are also fat, dumb and happy. On a test server where autofs(5) is also enabled and working well, I am testing nfs v3 (later v4) server. Strange things are happening. When nfs mountd(8) is running, the autofs(5) auto-mount (via automountd) function seems to work, but the autofs(5) auto-unmount (via autounmountd) never occurs. Without nfs mountd(8), when the filesystem /disc is auto-mounted (via autoumountd), the mount(8) command shows status of (ufs, local, journaled soft-updates, auto-mounted) for the auto-mounted filesystem and after the autofs(5) timeout period (600 seconds) the filesystem is auto-unmounted (via autounmountd). No problem. With nfs mountd(8) the mount(8) command shows (ufs, local, journaled soft-updates). The auto-mounted filesystem is never (a long, long time) unmounted. Big problem. Without nfs mountd(8) running, the mount(8) command mount -o automounted /dev/ada0p8 /disc mounts the filesystem and the mount(8) command shows (ufs, local, journaled soft-updates, automounted) for the manually mounted filesystem and after the autofs(5) timeout period (600 seconds) the filesystem is auto-unmounted even though it was not mounted automatically. No problem. With nfs mountd(8), the mount(8) command mount -o automounted /dev/ada0p8 /disc mounts the filesystem but the mount(8) command shows (ufs, local, journaled soft-updates) and after the timeout period (600 seconds) the filesystem is remains mounted. Big problem. It appears that nfs mountd(8) is interferring with the mount(8) command's -o option processing but admittedly that is just a very weak SWAG. I have adequate hardware (real and virtual) to do any testing that may be suggested. Most days there is no time constraint either. The /etc/auto_master file is two lines: 1:/net -hosts -nobrowse,nosuid(original) 2:/-/etc/autofs/auto_disc The /etc/autofs/auto_disc file is one line: 1:/disc -fstype=ufs :/dev/ada0p8 Once again, everything works well when nfs mountd(8) is not present in the system. Thanks for any assistance that you may be able to supply. David Boyd. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
CTF: wpa_supplicant/hostapd 2.4 import
Hi, Please test the new wpa_supplicant/hostapd. Here's the patch against FreeBSD HEAD: https://people.freebsd.org/~rpaulo/wpa-2.4.diff Thanks, -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Jenkins build is back to stable : FreeBSD_HEAD-tests2 #949
See https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/949/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: CTF: wpa_supplicant/hostapd 2.4 import
On Sun, Apr 19, 2015 at 02:35:17PM -0700, Rui Paulo wrote: Hi, Please test the new wpa_supplicant/hostapd. Here's the patch against FreeBSD HEAD: https://people.freebsd.org/~rpaulo/wpa-2.4.diff ... Seems OK so far for both amd64 i386; sources (prior to applying above patch) @r281736. I only use wpa_supplicant, and I've only tested it lightly at home (which is among my less challenging 802.11 environments). Peace, david -- David H. Wolfskill da...@catwhisker.org Those who murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgp4GoTcVCVoc.pgp Description: PGP signature
Re: Call For Testers: Synaptics touchpads
On 08.04.2015 09:19, Rui Paulo wrote:
The attached patch adds support for newer touchpad features and implements two
finger scrolling.
Hi,
thanks for bringing two finger scrolling to the psm driver!
I've attached a patch of some more improvements and fixes. I hope some
of this stuff can make it into the driver:
- Two finger scrolling support for semi-MT touchpads. Those include
many of the older Synaptics touchpads before true multitouch support
(indicated by capMultiFinger). Semi-MT touchpads can report a second
finger position, but the X or Y coordinate may be swapped with some
coordinate of the first finger. This is a result of how the hardware
works internally. Therefore, all that can be reliably extracted is the
bounding box of the two finger positions. Semi-MT touchpads can be
recognized by the capAdvancedGestures capability bit. After setting the
mode byte, advanced gestures mode has to be enabled. Then, data packets
compatible with the capMultiFinger format are sent, so the same two
finger scrolling code can be leveraged. Enabling advanced gestures mode
on true multitouch touchpads should be harmless. Linux seems to always
enable advanced gestures mode. I don't have a real multitouch touchpad
for testing though.
- Put mode setting logic into own functions synaptics_preferred_mode()
and synaptics_set_mode() to have this in one place.
synaptics_passthrough_on() and synaptics_passthrough_off() currently
always use 0xc1 as the mode byte, which may be wrong for touchpads that
don't have capExtended (sorry, my fault).
- Expose X and Y resolution of touchpad to userland. Also expose minimum
and maximum X and Y coordinates. This is useful for programs in
userspace that read raw PSM packets (with PSM_LEVEL_NATIVE enabled) and
need to interpret the coordinates.
- Also send extended w mode packets (see section 3.2.9 of
511-000275-01_RevB.pdf) to userspace if PSM_LEVEL_NATIVE is enabled.
This is useful for userspace programs/drivers such as
xf86-input-synaptics that can handle these packets.
- Fix parsing of nExtendedQueries, and request extended/continued
capability bits depending on this value.
- capReportsMax, capClearPad, capAdvancedGestures and capCoveredPad must
be extracted from status[0] and not status[2], I think.
Two finger scrolling works reasonably well with my semi-MT touchpad
(Lenovo T420). However, it is very sensitive if I move my fingers very
slowly. I wonder if this is because it's a semi-MT touchpad or if I have
to tweak some setting. Also sometimes, if I move my fingers up, it
scrolls down, and vice versa. Maybe this is a result of how dxp and dyp
are calculated with the abs() function?
Cheers,
Jan
diff --git a/sys/dev/atkbdc/psm.c b/sys/dev/atkbdc/psm.c
index e8a2a93..4e41eef 100644
--- a/sys/dev/atkbdc/psm.c
+++ b/sys/dev/atkbdc/psm.c
@@ -483,6 +483,8 @@ static probefunc_t enable_versapad;
static void set_trackpoint_parameters(struct psm_softc *sc);
static void synaptics_passthrough_on(struct psm_softc *sc);
static void synaptics_passthrough_off(struct psm_softc *sc);
+static int synaptics_preferred_mode(struct psm_softc *sc);
+static void synaptics_set_mode(struct psm_softc *sc, int mode_byte);
static struct {
int model;
@@ -933,14 +935,8 @@ doopen(struct psm_softc *sc, int command_byte)
get_mouse_status(sc-kbdc, stat, 0, 3);
if ((SYNAPTICS_VERSION_GE(sc-synhw, 7, 5) ||
stat[1] == 0x47)
- stat[2] == 0x40) {
- /* Set the mode byte -- request wmode where
- * available */
- if (sc-synhw.capExtended)
-mouse_ext_command(sc-kbdc, 0xc1);
- else
-mouse_ext_command(sc-kbdc, 0xc0);
- set_mouse_sampling_rate(sc-kbdc, 20);
+ stat[2] == 0x40) {
+ synaptics_set_mode(sc, synaptics_preferred_mode(sc));
VLOG(5, (LOG_DEBUG, psm%d: Synaptis Absolute Mode
hopefully restored\n,
sc-unit));
@@ -2176,6 +2172,20 @@ psmioctl(struct cdev *dev, u_long cmd, caddr_t addr, int flag,
(*(int *)addr PSM_LEVEL_MAX))
return (EINVAL);
sc-mode.level = *(int *)addr;
+
+ if (sc-hw.model == MOUSE_MODEL_SYNAPTICS) {
+ /*
+ * If we are entering PSM_LEVEL_NATIVE, we want to
+ * enable sending of extended W mode packets to
+ * userland. Reset the mode of the touchpad so that the
+ * change in the level is picked up.
+ */
+ error = block_mouse_data(sc, command_byte);
+ if (error)
+return (error);
+ synaptics_set_mode(sc, synaptics_preferred_mode(sc));
+ unblock_mouse_data(sc, command_byte);
+ }
break;
case MOUSE_GETSTATUS:
@@ -2864,7 +2874,8 @@ proc_synaptics(struct psm_softc *sc, packetbuf_t *pb, mousestatus_t *ms,
/* Palm detection. */
if (!(
- (sc-synhw.capMultiFinger (w == 0 || w == 1)) ||
+ ((sc-synhw.capMultiFinger ||
+ sc-synhw.capAdvancedGestures) (w == 0 || w == 1)) ||
(sc-synhw.capPalmDetect w = 4 w = max_width) ||
(!sc-synhw.capPalmDetect *z = max_pressure) ||
(sc-synhw.capPen w == 2))) {
Re: [Request for Help] Reducing gcc 4.9 compilation warnings
On 19 April 2015 at 02:10, Eitan Adler li...@eitanadler.com wrote: On 18 April 2015 at 11:12, Craig Rodrigues rodr...@freebsd.org wrote: Hi, After the latest commits by members of freebsd-toolchain@ , I have managed to compile latest CURRENT world and GENERIC kernel on amd64 with an gcc 4.9 external toolchain by doing: pkg install devel/amd64-xtoolchain-gcc cd /usr/src sed -i -e 's/boot2//' sys/boot/i386/Makefile make buildworld CROSS_TOOLCHAIN=amd64-gcc NO_WERROR=yes WERROR= make buildkernel CROSS_TOOLCHAIN=amd64-gcc NO_WERROR=yes WERROR= It was necessary to skip boot2 from building because of errors reported here: https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-April/001658.html The boot2 compilation errors still need to be worked on. However, most other things compile with warnings. If folks are interested in looking at the warnings, you can see them here: https://jenkins.freebsd.org/job/FreeBSD_HEAD_amd64_gcc4.9/warnings17 Please look at these warnings, and if you see places to patch the code to eliminate the warnings, please submit patches and commit them if you can. Some time ago I tried to do something similar, but with gcc4.6 instead of gcc4.9. The vast majority of warnings (1548) are unused-but-set-variable and it may be worthwhile to just silence this warning, at least at low WARNS levels. It has caught real errors but is quite noisy and can cause quite a bit of churn. inline (count 515) is generally pure noise, and I think we should disable it. It can be helpful to find certain types of performance optimizations, but it should be opt-in. strict-aliasing (154) are likely all real bugs of some form. Very few exist in contrib code, and it would be good to fix them. Warning (111) seem to be a mix of warnings, but mostly in contrib code. maybe-uninitialized (111) is often noisy, and in a spot check were all false positives. deprecated-declarations (22) is all in contrib code Many of these are useful though and I've already fixed a few of the bugs reported. Perhaps it would be useful to do a second run of this, but with a modified share/mk to silence the most useless of these warnings? I just got a booting mips32 kernel using gcc-4.9.2, and boy are there a lot of warnings. I'm going to start fixing the ones I find - cleaner code is better code. Mostly. (I'd be happy with -Wall -Werror.) -adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: CTF: wpa_supplicant/hostapd 2.4 import
On Sun, Apr 19, 2015 at 02:35:17PM -0700, Rui Paulo wrote: Hi, Please test the new wpa_supplicant/hostapd. Here's the patch against FreeBSD HEAD: https://people.freebsd.org/~rpaulo/wpa-2.4.diff Seems to be working fine on amd64. Tested on ral(4) and run(4). Thanks. Thanks, -- Rui Paulo Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
