On Tue, 2008-12-02 at 10:24 -0500, Devin Heitmueller wrote:
Looking through the archives, I have not seen any progress on Xvmc
support in the Intel driver for quite some time.
Could someone please summarize where Xvmc support is at for the
various Intel devices (g33/g35/g45 etc)?
XvMC
On Tue, 2008-12-02 at 17:13 -0500, sean darcy wrote:
I've also been waiting for SVDO support. Especially now that Keith
Packard writes today that XvMC support has been committed, the intel
chipsets would be a great basis for HTPC.
With NVIDIA's (closed source) VDPAU, Intel will need more
On Wed, Dec 03, 2008 at 11:53:27AM +0100, Khashayar Naderehvandi wrote:
I had problems with G45 too, but they were fixed during last Fedora
Rawhide cycle and Fedora 10 works OK. Not perfect yet -- activating
Compiz brings X into infinite loop after few minutes. Metacity
compositor
Hi,
On Wed, 2008-12-03 at 12:30 +0300, Руслан Бондарь wrote:
Hello all.
Sometimes my xorg server crashes.
Xorg-server version: 1.5.2
Linux distro: gentoo
X11 wm: openbox-3.4.7.2
I notice this problem only when I'm using dual-screen configuration.
I have dual headed nVidia GeForce 8600
On Mon, 2008-12-01 at 11:10 -0800, Alan Coopersmith wrote:
Xavier Bestel wrote:
On Mon, 2008-12-01 at 16:58 +0100, Nicolas Mailhot wrote:
Le Lun 1 décembre 2008 16:47, Alexander E. Patrakov a écrit :
Apriori, there is no sensible default keyboard layout.
There could be if the hardware
Hi,
xinput --reattach did the trick.
I didn't see the messages configure as mouse/keyboard/... as *additive*, so I
thought only one must occur.
But can one filter the device so that it is exactly and only a pointer? Or
the reverse?
Ι rewrote a little EvdevProbe's find/configure chain.
On Wed, 2008-12-03 at 19:45 +1100, garrone wrote:
On Tue, Dec 02, 2008 at 02:23:32PM -0500, Adam Jackson wrote:
On Tue, 2008-12-02 at 19:37 +1100, garrone wrote:
The intel man page (in xf86-video-intel) says:
SDVO and DVO TV outputs are not supported by the driver at this time.
I'm
Hi,
xinput --reattach did the trick.
I didn't see the messages configure as mouse/keyboard/... as *additive*, so I
thought only one must occur.
But can one filter the device so that it is exactly and only a pointer? Or
the reverse?
Ι rewrote a little EvdevProbe's find/configure chain.
Hi,
Could tinderbox be building xserver with all features enabled?
Right now some features are not build-tested and that ends with
unbuildable xserver with these features (dmx case for example).
Certainly. This looks like the missing list:
--enable-debug
--enable-builddocs
http://tinderbox.x.org/builds/2008-12-03-0012/
http://tinderbox.x.org/builds/2008-12-03-0012/logs/xserver/#build
In file included from Pci.c:130:
../../../../hw/xfree86/common/compiler.h:1041: error: expected '=', ',',
';', 'asm' or '__attribute__' before 'volatile'
On Wed, 2008-12-03 at 13:41 -0500, Adam Jackson wrote:
I've pushed a proposal for a pair of requests to get and set the primary
output to:
http://cgit.freedesktop.org/xorg/proto/randrproto/diff/?h=get-set-primaryid=c25389a1b5cb5cb513eb9486aca4df0d53d089df
Please just post diffs here.
On Wed, Dec 3, 2008 at 2:29 AM, Arkadiusz Miskiewicz [EMAIL PROTECTED] wrote:
Hi,
Could tinderbox be building xserver with all features enabled? Right now some
features are not build-tested and that ends with unbuildable xserver with
these features (dmx case for example).
Last I checked,
On Wednesday 03 of December 2008, Dan Nicholson wrote:
On Wed, Dec 3, 2008 at 2:29 AM, Arkadiusz Miskiewicz [EMAIL PROTECTED]
wrote:
Hi,
Could tinderbox be building xserver with all features enabled? Right now
some features are not build-tested and that ends with unbuildable xserver
On Wed, Dec 3, 2008 at 12:07 PM, Arkadiusz Miskiewicz [EMAIL PROTECTED] wrote:
On Wednesday 03 of December 2008, Dan Nicholson wrote:
On Wed, Dec 3, 2008 at 2:29 AM, Arkadiusz Miskiewicz [EMAIL PROTECTED]
wrote:
Hi,
Could tinderbox be building xserver with all features enabled? Right now
On Wednesday 03 of December 2008, Dan Nicholson wrote:
On Wed, Dec 3, 2008 at 12:07 PM, Arkadiusz Miskiewicz [EMAIL PROTECTED]
wrote:
On Wednesday 03 of December 2008, Dan Nicholson wrote:
On Wed, Dec 3, 2008 at 2:29 AM, Arkadiusz Miskiewicz [EMAIL PROTECTED]
wrote:
Hi,
Could
2008/12/3 Adam Jackson [EMAIL PROTECTED]:
http://www.freebsd.org/copyright/freebsd-doc-license.html
It's more explicit than I think is directly appropriate for X, since
much of our documentation source is not DocBook. But.
OK (probably). Any other licenses in the X.org tree that are worth
---
mi/mi.h |3 +++
xkb/ddxDevBtn.c |3 ++-
2 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/mi/mi.h b/mi/mi.h
index 444d3ad..1dc4780 100644
--- a/mi/mi.h
+++ b/mi/mi.h
@@ -222,6 +222,9 @@ extern void miClearDrawable(
GCPtr /*pGC*/
);
+void
---
glx/indirect_program.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/glx/indirect_program.c b/glx/indirect_program.c
index d23a0a9..cbea40e 100644
--- a/glx/indirect_program.c
+++ b/glx/indirect_program.c
@@ -103,7 +103,7 @@ int DoGetProgramString(struct
---
glx/render2.c |5 -
glx/render2swap.c |5 -
2 files changed, 0 insertions(+), 10 deletions(-)
diff --git a/glx/render2.c b/glx/render2.c
index a86a22a..b958d90 100644
--- a/glx/render2.c
+++ b/glx/render2.c
@@ -252,8 +252,3 @@ void __glXDisp_DrawArrays(GLbyte *pc)
Here's a series of compile warning fixes I came up with while looking at them
trying to figure out if anything was wrong that broke GLX (fix for that is
already pushed). The ddxDevBtn.c one looks like a real bugfix.
There are a few more that look important
xf86Xinput.c:654: warning: ‘idev’ may
---
hw/xfree86/common/xf86Bus.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/xfree86/common/xf86Bus.c b/hw/xfree86/common/xf86Bus.c
index c825d23..eaa0618 100644
--- a/hw/xfree86/common/xf86Bus.c
+++ b/hw/xfree86/common/xf86Bus.c
@@ -66,7 +66,7 @@ xf86AccessRec
On Sat, Nov 29, 2008 at 06:37:48PM +0100, eatdirt wrote:
sorry about the naive questions, I am a mandriva cooker tester/user, and
I have just discovered recently that soon, I'll have to start HAL to get
working device under X. So I have a few comments/questions:
1) Today, if you are not
Thanks. I'm afraid I have a problem even doing the uninstall. Could this be the
crux of all my trouble?
rpmdb: Page 105: bad prev_pgno 0 on overflow page (should be 106)
rpmdb: Page 105: overflow item incomplete
rpmdb: /var/lib/rpm/Requireversion: DB_VERIFY_BAD: Database verification failed
On Wed, Dec 03, 2008 at 07:59:49AM -0800, Sebastian Glita wrote:
xinput --reattach did the trick.
I didn't see the messages configure as mouse/keyboard/... as *additive*,
so I thought only one must occur.
No, mouse is basically axes + buttons, keyboards is keys, etc. More and more
devices have
On Wed, Dec 03, 2008 at 01:29:09PM -0800, Eric Anholt wrote:
Here's a series of compile warning fixes I came up with while looking at them
trying to figure out if anything was wrong that broke GLX (fix for that is
already pushed). The ddxDevBtn.c one looks like a real bugfix.
There are a
Adam Jackson [EMAIL PROTECTED] writes:
Because no one both: has SDVO TV out hardware, and is capable of making
it work.
Hmm. I think I have SDVO TV output in my i915G machine (MSI Hetis 915
- not sure about the exact capabilities but at least composite +
svideo). I even tried to look at it
On Wed, Dec 03, 2008 at 07:20:26AM -0800, Dan Nicholson wrote:
Hotplug hooks are added to the HAL core to allow the DDX to handle device
hotplugging. If a registered hook returns False, config/hal will continue
processing the event. This allows the DDX to examine the type of device
and
On Wednesday 03 December 2008 02:33:34 pm Peter Hutterer wrote:
http://who-t.blogspot.com/2008/12/evdev-xorgconf-hal-and-other-fud.html
That's a quick brain dump of input related things I could think of that are
repeatedly asked on the list, irc, and bugreports. The information is
accurate
On Wed, 2008-12-03 at 20:52 -0800, Paulo Cesar Pereira de Andrade wrote:
.gitignore | 92 ++-
Makefile.am|2
configure.ac |1
hw/xfree86/Makefile.am |4 -
On Wed, Dec 03, 2008 at 08:08:35PM -0800, vehemens wrote:
On Wednesday 03 December 2008 02:33:34 pm Peter Hutterer wrote:
http://who-t.blogspot.com/2008/12/evdev-xorgconf-hal-and-other-fud.html
That's a quick brain dump of input related things I could think of that are
repeatedly
Hi,
You appear to have taken my patch and s/fprintf(stderr, /perror(/.
Generally in a situation like this one would leave original authorship
intact (even my comments were preserved!).
Don't know why I changed that :-) It opens space for bikeshedding
on something that should never happen
I was able to make the two internal channels assign to the two TMDS
outputs by using the -crtc option, as follows.
xrandr --fb 1680x2100 \
--output VGA --off\
--output LVDS --off\
--output TMDS-1 --pos 0x1050 --mode 1680x1050 --crtc 0\
--output TMDS-2 --mode
Keith Packard wrote:
I suspect drivers will want to set the default primary output to
something other than None -- on a laptop, one can imagine always making
the LVDS 'primary'...
...unless this is a work laptop that generally sits in its dock with a
big monitor attached and external keyboard
Hi,
I just got my new USB DVB-T dongle, which features an IR receiver and
comes with a remote. It sort of works, but I have the following problem:
My X server is configured to use evdev for all its input. This is fine
also for the remote, since the kernel generates key input events for all
On Wed, Dec 3, 2008 at 7:28 PM, Peter Hutterer [EMAIL PROTECTED] wrote:
On Wed, Dec 03, 2008 at 07:20:26AM -0800, Dan Nicholson wrote:
Hotplug hooks are added to the HAL core to allow the DDX to handle device
hotplugging. If a registered hook returns False, config/hal will continue
processing
35 matches
Mail list logo
