[ANNOUNCE] applewmproto 1.3.0
Jeremy Huddleston (3): Pad xAppleWMNotifyEvent up to 32 bytes to properly match sizeof(xEvent) Added XAppleWMAttachTransient to push that codepath from quartz- wm into Xplugin... needed for SL. 1.3.0 git tag: applewmproto-1.3.0 http://xorg.freedesktop.org/archive/individual/proto/applewmproto-1.3.0.tar.bz2 MD5: f6b7b47a19536b9e803229ac39550245 applewmproto-1.3.0.tar.bz2 SHA1: 81e887ce7bc1969544868d7a79270fd21c9e9d4e applewmproto-1.3.0.tar.bz2 http://xorg.freedesktop.org/archive/individual/proto/applewmproto-1.3.0.tar.gz MD5: a479b9237e537716dacdc4cc14ea40ee applewmproto-1.3.0.tar.gz SHA1: 2f8e6608ef30c0ee364573e52ab81e83d03d8a6f applewmproto-1.3.0.tar.gz ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
[ANNOUNCE] libAppleWM 1.3.0
Jeremy Huddleston (3): Remove compile warning about signedness Added XAppleWMAttachTransient for SnowLeopard 1.3.0 git tag: libAppleWM-1.3.0 http://xorg.freedesktop.org/archive/individual/lib/libAppleWM-1.3.0.tar.bz2 MD5: e79128571bb64e4c1286b8a1a8c4b8ab libAppleWM-1.3.0.tar.bz2 SHA1: 8fb77026babb9d96eba57e826bb92e8ff7fd767f libAppleWM-1.3.0.tar.bz2 http://xorg.freedesktop.org/archive/individual/lib/libAppleWM-1.3.0.tar.gz MD5: 8b44b7489994a576cfed56204fb07241 libAppleWM-1.3.0.tar.gz SHA1: 0129a179fa45c0261b2d47cbaefbca8696b2116d libAppleWM-1.3.0.tar.gz ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
[ANNOUNCE] libAppleWM 1.3.0
Jeremy Huddleston (3): Remove compile warning about signedness Added XAppleWMAttachTransient for SnowLeopard 1.3.0 git tag: libAppleWM-1.3.0 http://xorg.freedesktop.org/archive/individual/lib/libAppleWM-1.3.0.tar.bz2 MD5: e79128571bb64e4c1286b8a1a8c4b8ab libAppleWM-1.3.0.tar.bz2 SHA1: 8fb77026babb9d96eba57e826bb92e8ff7fd767f libAppleWM-1.3.0.tar.bz2 http://xorg.freedesktop.org/archive/individual/lib/libAppleWM-1.3.0.tar.gz MD5: 8b44b7489994a576cfed56204fb07241 libAppleWM-1.3.0.tar.gz SHA1: 0129a179fa45c0261b2d47cbaefbca8696b2116d libAppleWM-1.3.0.tar.gz ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
2D/3D Acceleration on 3dfx Voodoo 3
Hi, I'm trying to get proper hw acceleration using this 3dfx card so far it's not possible using 1280x1024 @ 24bit depth, which I'm currently using. I need some ideas, suggestions how to fix this :) dmesg | grep -i drm [0.275903] [drm] Initialized drm 1.1.0 20060810 [ 6587.330829] [drm] Initialized tdfx 1.0.0 20010216 for :01:00.0 on minor 0 lspci -nn | grep -i VGA 01:00.0 VGA compatible controller [0300]: 3Dfx Interactive, Inc. Voodoo 3 [121a:0005] (rev 01) glxinfo | grep render direct rendering: Yes OpenGL renderer string: Software Rasterizer Xorg.conf - http://pastebin.ca/1483668 Xorg.0.log - http://pastebin.ca/1483667 Thanks. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: 2D/3D Acceleration on 3dfx Voodoo 3
Hello, In the Message; Subject: 2D/3D Acceleration on 3dfx Voodoo 3 Message-ID : d2393e040907040002y634a155ame9781813afaf3...@mail.gmail.com Date Time: Sat, 4 Jul 2009 10:02:25 +0300 [Kristaps] == Kristaps Esterlins esterli...@gmail.com has written: Kristaps Hi, I'm trying to get proper hw acceleration using this 3dfx Kristaps card so far it's not possible using 1280x1024 @ 24bit depth, Kristaps which I'm currently using. I need Kristaps some ideas, suggestions how to fix this :) [...] Kristaps Xorg.conf - http://pastebin.ca/1483668 How about adding this to xorg.conf. Section DRI Mode 666 EndSection Regards, --- Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp Bill! You married with Computers. Not with Me! No..., with money. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
starter tips on fixing autodtection for a crusty old driver
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-trident/+bug/315329 Ye olde ancient Trident driver doesn't autodetect 1024x768 properly - it sets the display to 800x600 as the biggest supported mode. Looking at the xorg.0.log, it detects the TFT as 1024x768 properly, but thinks all 1024x768 modes are out of hsync or vsync range. Now, (a) it would be nice to have this autodetect because xorg.conf sucks (b) it's a crusty old driver which even I would class as we welcome your patch rather than any sort of showstopper. So. Where would one start on fixing autodetection code for a crusty old driver? - d. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: setting evdev properties from HAL?
Asbjørn Sannes wrote: But for Evdev Axis Calibration I have not found anything that works .. Any hints and suggestions are welcome :) One could probably do a patch which adds property manipulation to config/hal, but it didn't surface yet. I remember to have heard hal can be configured to invoke scripts like yours on device add/remove. Not sure of it, though. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: 2D/3D Acceleration on 3dfx Voodoo 3
As I recall, the Voodoo 3 only supports 3D acceleration at 16 bit. This is not a driver limitation, but a hardware limitation. Adam Kristaps Esterlins wrote: Hi, I'm trying to get proper hw acceleration using this 3dfx card so far it's not possible using 1280x1024 @ 24bit depth, which I'm currently using. I need some ideas, suggestions how to fix this :) dmesg | grep -i drm [0.275903] [drm] Initialized drm 1.1.0 20060810 [ 6587.330829] [drm] Initialized tdfx 1.0.0 20010216 for :01:00.0 on minor 0 lspci -nn | grep -i VGA 01:00.0 VGA compatible controller [0300]: 3Dfx Interactive, Inc. Voodoo 3 [121a:0005] (rev 01) glxinfo | grep render direct rendering: Yes OpenGL renderer string: Software Rasterizer Xorg.conf - http://pastebin.ca/1483668 Xorg.0.log - http://pastebin.ca/1483667 Thanks. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
3dfx/Westinghouse LCD configuration broken by upgrade
I'm using Ubuntu and Gentoo Linux, a 3dfx Voodoo 3 board and a Westinghouse LCD monitor model LCM-20v5 through a KVM switch (the Ubuntu and Gentoo are two different hosts). I had a working configuration with xorg on both, they have both been broken by recent upgrades to xorg. I can no longer get X to boot up to a working GUI. For the moment, I'll focus on the Ubuntu situation I have tried the output of Xorg --configure (http://pastebin.ca/1483889)(log file http://pastebin.ca/1483907) I have tried the old xorg.conf (http://pastebin.ca/1483892) (log file http://pastebin.ca/1483900) I have tried and empty xorg.conf. (log file http://pastebin.ca/1483925) The results are the same with all three: the Ubuntu bootup screen is normal (Graphical: Ubuntu logo, large name in an outline font, and a cylon progress bar with a bright segment moving back and forth) later followed by a brief moment with the usual Ubuntu busy cursor, then a black screen with occasional flickers of slightly gray). Useless, but I think I'd be satisfied with the mode that showed the cursor -- it was about as small as I remember for a 1280x1024 mode. The hardware is working to this extent: Dual-booting to windows 98 I get 7 different video modes from 640x480 all the way up to 1280x1024. Moreover, the Ubuntu live disk can at least find a 600x800 mode. I suspect there's something about the newer X and the monitor itself, rather than the video driver, because the Gentoo system also broke on upgrade, and it uses an ATI Rage chipset on the motherboard. The results there are about the same. How can I work to solve this? -- Kevin O'Gorman, PhD ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: starter tips on fixing autodtection for a crusty old driver
On Sat, Jul 4, 2009 at 6:55 AM, David Gerarddger...@gmail.com wrote: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-trident/+bug/315329 Ye olde ancient Trident driver doesn't autodetect 1024x768 properly - it sets the display to 800x600 as the biggest supported mode. Looking at the xorg.0.log, it detects the TFT as 1024x768 properly, but thinks all 1024x768 modes are out of hsync or vsync range. Now, (a) it would be nice to have this autodetect because xorg.conf sucks (b) it's a crusty old driver which even I would class as we welcome your patch rather than any sort of showstopper. So. Where would one start on fixing autodetection code for a crusty old driver? Something like this should do the trick: http://cgit.freedesktop.org/xorg/driver/xf86-video-savage/commit/?id=fd20f5ddc2ef5945a757f6afedff5fb6214b607e Alex ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: setting evdev properties from HAL?
On Sat, Jul 04, 2009 at 02:32:09PM +0200, Simon Thum wrote:
Asbjørn Sannes wrote:
But for Evdev Axis Calibration I have not found anything that works ..
Any hints and suggestions are welcome :)
One could probably do a patch which adds property manipulation to
config/hal, but it didn't surface yet.
I remember to have heard hal can be configured to invoke scripts like
yours on device add/remove. Not sure of it, though.
I started that once but I'm being told HAL is on its way out so I decided
not to finish them. If you want to pick it up - be my guest, patches below.
Having said that, it is questionable whether they will go upstream if you do
finish them. There is quite a push away from HAL and adding new HAL-only
functionality is not the way to go. Especially for things like this that can
be set at runtime.
Time is possibly better spent investigating libudev and finding out how to
automatically port current fdi configurations so they work on a udev-only
system.
Cheers,
Peter
From 74c05685e47586f70e0d7b324a1e29eac44e59b9 Mon Sep 17 00:00:00 2001
From: Peter Hutterer peter.hutte...@who-t.net
Date: Thu, 26 Mar 2009 14:23:09 +1000
Subject: [PATCH] config: rename LIBHAL_... defines for better namespacing.
---
config/hal.c | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/config/hal.c b/config/hal.c
index 36fa839..782fbb5 100644
--- a/config/hal.c
+++ b/config/hal.c
@@ -40,8 +40,8 @@
#include os.h
-#define LIBHAL_PROP_KEY input.x11_options.
-#define LIBHAL_XKB_PROP_KEY input.xkb.
+#define LIBHAL_OPTIONS_KEY input.x11_options.
+#define LIBHAL_XKB_OPTIONS_KEY input.xkb.
struct config_hal_info {
@@ -273,7 +273,7 @@ device_added(LibHalContext *hal_ctx, const char *udi)
if (psi_key){
/* normal options first (input.x11_options.propname) */
-if (!strncasecmp(psi_key, LIBHAL_PROP_KEY,
sizeof(LIBHAL_PROP_KEY)-1)){
+if (!strncasecmp(psi_key, LIBHAL_OPTIONS_KEY,
sizeof(LIBHAL_OPTIONS_KEY)-1)){
char* tmp;
/* only support strings for all values */
@@ -319,7 +319,7 @@ device_added(LibHalContext *hal_ctx, const char *udi)
} else
{
/* all others */
-add_option(options, psi_key +
sizeof(LIBHAL_PROP_KEY)-1, tmp_val);
+add_option(options, psi_key +
sizeof(LIBHAL_OPTIONS_KEY)-1, tmp_val);
xfree(tmp_val);
}
} else
@@ -335,15 +335,15 @@ device_added(LibHalContext *hal_ctx, const char *udi)
xkb_opts.options = strdup(tmp_val);
}
}
-} else if (!strncasecmp(psi_key, LIBHAL_XKB_PROP_KEY,
sizeof(LIBHAL_XKB_PROP_KEY)-1)){
+} else if (!strncasecmp(psi_key, LIBHAL_XKB_OPTIONS_KEY,
sizeof(LIBHAL_XKB_OPTIONS_KEY)-1)){
char* tmp;
/* only support strings for all values */
tmp_val = get_prop_string(hal_ctx, udi, psi_key);
-if (tmp_val strlen(psi_key) = sizeof(LIBHAL_XKB_PROP_KEY))
{
+if (tmp_val strlen(psi_key) =
sizeof(LIBHAL_XKB_OPTIONS_KEY)) {
-tmp = psi_key[sizeof(LIBHAL_XKB_PROP_KEY) - 1];
+tmp = psi_key[sizeof(LIBHAL_XKB_OPTIONS_KEY) - 1];
if (!strcasecmp(tmp, layout))
{
@@ -371,9 +371,9 @@ device_added(LibHalContext *hal_ctx, const char *udi)
{
/* server 1.4 had xkb options as strlist */
tmp_val = get_prop_string_array(hal_ctx, udi, psi_key);
-if (tmp_val strlen(psi_key) =
sizeof(LIBHAL_XKB_PROP_KEY))
+if (tmp_val strlen(psi_key) =
sizeof(LIBHAL_XKB_OPTIONS_KEY))
{
-tmp = psi_key[sizeof(LIBHAL_XKB_PROP_KEY) - 1];
+tmp = psi_key[sizeof(LIBHAL_XKB_OPTIONS_KEY) - 1];
if (!strcasecmp(tmp, .options)
(!xkb_opts.options))
xkb_opts.options = strdup(tmp_val);
}
--
1.6.0.6
From 96bbf362cb7a9c624189b6c53c4578a3496abddd Mon Sep 17 00:00:00 2001
From: Peter Hutterer peter.hutte...@who-t.net
Date: Thu, 26 Mar 2009 14:23:47 +1000
Subject: [PATCH] config: allow device labelling through hal keys.
Supports hal keys in the following format:
append key=input.x11_property.abc type=strlist123/append
append key=input.x11_property.abc type=strlist456/append
append key=input.x11_property.foo type=strlistbar/append
The above results in two properties being added to the input device:
abc - 123, 456
foo - bar
Where both abc and foo are properties that contain lists of Atoms (and
123, 456 and bar are Atoms created on-the-fly).
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
config/hal.c | 90
