[ANNOUNCE] xkbprint 1.0.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 xkbprint generates a printable or encapsulated PostScript description of an XKB keyboard description. This is a minor bug fix janitorial release. Alan Coopersmith (4): Add README with pointers to mailing lists, bugzilla, git Migrate to xorg macros 1.3 XORG_DEFAULT_OPTIONS Fill in COPYING with notices from code xkbprint 1.0.2 James Cloos (3): Rename .cvsignore to .gitignore Add *~ to .gitignore to skip patch/emacs droppings Replace static ChangeLog with dist-hook to generate from git log Niveditha Rau (1): Fix typo in xkbprint man page Paulo Cesar Pereira de Andrade (2): Compile warning fixes. Correct make distcheck and sparse warnings. Pavel Kurashov (1): correct outline with cornerRadius Peter Breitenlohner (1): build fixes git tag: xkbprint-1.0.2 http://xorg.freedesktop.org/archive/individual/app/xkbprint-1.0.2.tar.bz2 MD5: 3d3eb10466442354d6b73b503b9829db SHA1: 36e4c8a143b6ab3672843c110db9357b39589927 http://xorg.freedesktop.org/archive/individual/app/xkbprint-1.0.2.tar.gz MD5: 5daee1936ba0b76f31a450f2f3b39adb SHA1: 54aa746f86a39089f0520e36b73f3e810ae64436 - -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (SunOS) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkr6a5oACgkQovueCB8tEw7jEACcDo6pNd+ZlieeR7ulVVO+tbk2 g04An0o9Qxpe8+mpVPpCgUox5S+2iJom =pLpp -END PGP SIGNATURE- ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
xkb - separate layout for each window
Hello, is there a way how to setup separate layout of keyboard for each window? Similar thing does gnome or some other desktops environments but I would like to setup this using setxkbmap or xorg.conf/hal. Is there a way? -- Lukáš Hejtmánek ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[PATCH] xfree86: Use SA_SIGINFO if available for SIGIO handlers
This one's slightly subtle, the fcntl(F_SETSIG) is required for -si_fd
to actually be filled in correctly, at least on Linux. I know this area
has been sensitive to platform variation in the past, so I'd appreciate
a second look from Solaris / BSD / Hurd people.
---
siginfo_t gives us the file descriptor that raised the signal directly,
so we don't need to select() for it. This gets evdev event processing
down to exactly one syscall in the common case.
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/os-support/shared/sigio.c | 40 -
1 files changed, 34 insertions(+), 6 deletions(-)
diff --git a/hw/xfree86/os-support/shared/sigio.c
b/hw/xfree86/os-support/shared/sigio.c
index aed5654..4f1ec55 100644
--- a/hw/xfree86/os-support/shared/sigio.c
+++ b/hw/xfree86/os-support/shared/sigio.c
@@ -95,12 +95,11 @@ static int xf86SigIOMax;
static int xf86SigIOMaxFd;
static fd_set xf86SigIOMask;
-/*
- * SIGIO gives no way of discovering which fd signalled, select
- * to discover
- */
+#ifndef SA_SIGINFO
+
+/* plain signals have no way of discovering which fd signalled. */
static void
-xf86SIGIO (int sig)
+sigio_handler (int sig)
{
inti;
fd_set ready;
@@ -126,6 +125,27 @@ xf86SIGIO (int sig)
errno = save_errno;
}
+#else /* have SA_SIGINFO */
+
+/* siginfo passes the triggering fd in, no need to select() */
+static void
+sigio_sigaction(int sig, siginfo_t *si, void *ctx)
+{
+int i;
+int save_errno = errno;
+
+for (i = 0; i MAX_FUNCS; i++) {
+if (xf86SigIOFuncs[i].f xf86SigIOFuncs[i].fd == si-si_fd) {
+(*xf86SigIOFuncs[i].f)(si-si_fd, xf86SigIOFuncs[i].closure);
+break;
+}
+}
+
+errno = save_errno;
+}
+
+#endif
+
static int
xf86IsPipe (int fd)
{
@@ -164,6 +184,9 @@ xf86InstallSIGIOHandler(int fd, void (*f)(int, void *),
void *closure)
xf86Msg(X_WARNING, fcntl(%d, F_SETOWN): %s\n,
fd, strerror(errno));
} else {
+#ifdef SA_SIGINFO
+fcntl(fd, F_SETSIG, SIGIO);
+#endif
installed = TRUE;
}
}
@@ -184,8 +207,13 @@ xf86InstallSIGIOHandler(int fd, void (*f)(int, void *),
void *closure)
}
sigemptyset(sa.sa_mask);
sigaddset(sa.sa_mask, SIGIO);
+#ifndef SA_SIGINFO
sa.sa_flags = 0;
- sa.sa_handler = xf86SIGIO;
+ sa.sa_handler = sigio_handler;
+#else
+sa.sa_flags = SA_SIGINFO;
+sa.sa_sigaction = sigio_sigaction;
+#endif
sigaction(SIGIO, sa, osa);
xf86SigIOFuncs[i].fd = fd;
xf86SigIOFuncs[i].closure = closure;
--
1.6.5.2
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [PATCH] xfree86: Use SA_SIGINFO if available for SIGIO handlers
Adam Jackson, le Tue 10 Nov 2009 14:53:50 -0500, a écrit : This one's slightly subtle, the fcntl(F_SETSIG) is required for -si_fd to actually be filled in correctly, at least on Linux. I know this area has been sensitive to platform variation in the past, so I'd appreciate a second look from Solaris / BSD / Hurd people. Looks fine concerning the Hurd which doesn't (yet) have the standard SA_SIGINFO, but an earlier GNU variation not announced through the SA_SIGINFO macro. Note however that si_fd is not standard, maybe configure should check for its existence. Samuel ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xkb - separate layout for each window
On Tue, Nov 10, 2009 at 01:19:09PM +0100, Lukas Hejtmanek wrote: is there a way how to setup separate layout of keyboard for each window? Similar thing does gnome or some other desktops environments but I would like to setup this using setxkbmap or xorg.conf/hal. Is there a way? no. the xkb map is actually kept in the client, in order to do what you propose you'd have to send mapping notify events with each enter/leave event and let the client refresh the keymap if necessary. Possible, but then you need to define what a window is. the definition of a window in the X protocol is merely a rectangular area on the screen clients can draw to (disclaimer: details missing). that applies to virtually every visible item on the screen, though with recent efforts those sometimes get consolidated into a single window. in short, what a window is on the client is fairly unpredictable and since windows appear and disappear all the time, a commandline interface for such a task would be entertaining but mostly useless. the definition of window you refer to is mostly implemented in the window manager and doesn't apply here. you really need the WM/DE to do this kind of stuff. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
radeon: different colors on different heads?
Hi all, I have two identical (Samsung 214T) monitors attached to the two outputs of a FireMV 2200 PCI card (RV280 based). I see something strange: there are some colors (mostly from the dark blue range) which are rendered completely differently by the two monitors. (One of them does black instead of dark blue.) Here is a test pattern I created: http://picasaweb.google.com/lh/photo/z8cGJO-qRn7iwUY7NLB7Fw?authkey=Gv1sRgCM60oc7kuoW24gEfeat=directlink ..and how it looks like: - on monitor 1 (buggy): http://picasaweb.google.com/lh/photo/aK0472ZaVi6tQzgcYOBGyA?authkey=Gv1sRgCM60oc7kuoW24gEfeat=directlink (The diagonal black strip is not the error in the photo; it's the error I am complaining about.) - on monitor 2 (normal): http://picasaweb.google.com/lh/photo/gXvQ9y72WMDhrjq3kQzicw?authkey=Gv1sRgCM60oc7kuoW24gEfeat=directlink * * * If I switch the connections of the two monitors, the problem jumps to monitor 2, so it's not the monitor's fault; something must be wrong with one of the heads of the video card. * * * Can this be something the software driver (radeon) does, or is this likely a hardware problem? Thank you for your help: Kristof ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: radeon: different colors on different heads?
Csillag Kristof wrote: Hi all, I have two identical (Samsung 214T) monitors attached to the two outputs of a FireMV 2200 PCI card (RV280 based). I see something strange: there are some colors (mostly from the dark blue range) which are rendered completely differently by the two monitors. (One of them does black instead of dark blue.) I have just tested the same thing with my FireMV 2400 PCI card (probably rv250 based), and the some error does _not_ appear. Kristof ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] xgc 1.0.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 xgc is an X11 graphics demo that shows various features of the X11 core protocol graphics primitives. This is mostly a minor build fix janitorial release, with the small addition of a colorized app-defaults file. Alan Coopersmith (7): Bug 14185: MAINTAINERCLEANFILES multiply defined in Makefile.am Change xgc_CFLAGS to AM_CFLAGS to make automake-1.10 happier Add README with pointers to mailing lists, bugzilla, git Include more detailed xgc man page description from Solaris Migrate to xorg macros 1.3 XORG_DEFAULT_OPTIONS Fill in COPYING with notices from main.c xgc.man xgc 1.0.2 James Cloos (4): Rename .cvsignore to .gitignore Add *~ to .gitignore to skip patch/emacs droppings Replace static ChangeLog with dist-hook to generate from git log xaw8 is gone, use xaw7 Jens Stroebel (1): correcting typo w. regards to XGC_CFLAGS Jeremy Huddleston (1): Build fix for file systems that are not case sensitive Paulo Cesar Pereira de Andrade (2): Ansification and compile warning fixes. Xgc now in Technicolor Peter Breitenlohner (1): enable VPATH build, reorganize app default files git tag: xgc-1.0.2 http://xorg.freedesktop.org/archive/individual/app/xgc-1.0.2.tar.bz2 MD5: fec79887ca14575bef4c757b4e95a693 SHA1: fbba25046970fa95af4ebbdb5ab0c8e1419531ed http://xorg.freedesktop.org/archive/individual/app/xgc-1.0.2.tar.gz MD5: 418f18f096df890740af8034295381fc SHA1: 6958385d07dc3c04825469c8d53d03e10fb500de - -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (SunOS) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkr6ZPwACgkQovueCB8tEw5rogCdHOMt86MuBUvgH/X+KIfvGBMM SYIAn1UOq8mQbKnfT7F79UBIU1uEFyMX =A4NT -END PGP SIGNATURE- ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] xkbprint 1.0.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 xkbprint generates a printable or encapsulated PostScript description of an XKB keyboard description. This is a minor bug fix janitorial release. Alan Coopersmith (4): Add README with pointers to mailing lists, bugzilla, git Migrate to xorg macros 1.3 XORG_DEFAULT_OPTIONS Fill in COPYING with notices from code xkbprint 1.0.2 James Cloos (3): Rename .cvsignore to .gitignore Add *~ to .gitignore to skip patch/emacs droppings Replace static ChangeLog with dist-hook to generate from git log Niveditha Rau (1): Fix typo in xkbprint man page Paulo Cesar Pereira de Andrade (2): Compile warning fixes. Correct make distcheck and sparse warnings. Pavel Kurashov (1): correct outline with cornerRadius Peter Breitenlohner (1): build fixes git tag: xkbprint-1.0.2 http://xorg.freedesktop.org/archive/individual/app/xkbprint-1.0.2.tar.bz2 MD5: 3d3eb10466442354d6b73b503b9829db SHA1: 36e4c8a143b6ab3672843c110db9357b39589927 http://xorg.freedesktop.org/archive/individual/app/xkbprint-1.0.2.tar.gz MD5: 5daee1936ba0b76f31a450f2f3b39adb SHA1: 54aa746f86a39089f0520e36b73f3e810ae64436 - -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (SunOS) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkr6a5oACgkQovueCB8tEw7jEACcDo6pNd+ZlieeR7ulVVO+tbk2 g04An0o9Qxpe8+mpVPpCgUox5S+2iJom =pLpp -END PGP SIGNATURE- ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
