Hello,
I'm new to the list.
I own 2 thinclients (Fujitsu siemens Futro B100), with a GX1 CPU, and a
CS5530A video chip.
I've seen on the Geode driver site, that help would be appreciated for
the developpment of the GX1 part.
If anyone needs help, I can send you one of my thinclients, or even
2014-07-22 19:00 GMT+03:00 Marc Gilet pw.mar...@laposte.net:
I own 2 thinclients (Fujitsu siemens Futro B100), with a GX1 CPU, and a
CS5530A video chip.
I've seen on the Geode driver site, that help would be appreciated for the
developpment of the GX1 part.
If anyone needs help, I can send
On Jul 13, 2014, at 15:11, Thomas Dickey dic...@his.com wrote:
* modify configure script to work around debris left by XQuartz
upgrades.
What is this about? This is the first I've heard of anything...
--Jeremy
___
Niltze!
After a Debian distribution upgrade [apt-get dist-upgrade] my
3-month-old X build [X.Org X Server 1.15.99.902 (1.16.0 RC 2) Release
Date: 2014-04-08] does not function properly anymore in a machine with
Intel i915.
I have since then built X from section: Build Process Based on
build.sh
On Jul 22, 2014, at 12:35, Thomas Dickey dic...@his.com wrote:
On Mon, Jul 21, 2014 at 11:12:18PM -0700, Jeremy Huddleston Sequoia wrote:
On Jul 13, 2014, at 15:11, Thomas Dickey dic...@his.com wrote:
* modify configure script to work around debris left by XQuartz
upgrades.
On Jul 21, 2014, at 19:09, Peter Hutterer peter.hutte...@who-t.net wrote:
On Sat, Jul 19, 2014 at 05:36:34PM -0700, Jeremy Huddleston Sequoia wrote:
Actually ... while this does address the crash, it now just causes a bunch
of our events to be ignored instead of processed.
So should that
Please also cherry-pick 1faa76670572e3478965fd2cd9ab60ab2d865e3a into
server-1.16-branch after the merge, thanks,
--Jeremy
The following changes since commit cff12936275db2f71f6d24f9ea0985a0d14af454:
glamor: sync_fence_set_triggered should use glFlush, not glFinish (2014-07-19
12:25:24
The following changes since commit cff12936275db2f71f6d24f9ea0985a0d14af454:
glamor: sync_fence_set_triggered should use glFlush, not glFinish (2014-07-19
12:25:24 -0700)
are available in the git repository at:
ssh://people.freedesktop.org/~ajax/xserver.git xserver-next
for you to fetch
Anytime a capability is first reported, the device is created, but after
that, it is only disabled/enabled.
This is a closer behavior to what Xorg does on VT switch, at the expense
of maybe leaving a dangling physical device if a capability goes for good.
Otherwise, any DeviceIntPtr (re)created
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/xf86Cursor.c | 2 --
hw/xfree86/common/xf86Events.c | 1 -
hw/xfree86/common/xf86Init.c | 2 --
hw/xfree86/loader/loader.c | 1 -
This is the only place they're actually used (well, aside from some XAA
code in the s3 driver, but one s3 and 2 XAA).
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 36
I guess this might have been needed for elfloader, except we didn't
support nds32 back then, so I assume this was cargo-culted from
ppc_flush_icache, which is also dead now.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
Yes yes, very clever, memmove works fine on gcc too, let's just do the
portable thing since none of this is performance code.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 69
Resend of the equivalent series from May. I'm sure I had to touch up
some of it to account for whatever arch patches we added between then
and now, but I forget which, so the individual patches lack versioning;
sorry about that.
Between this, the servermd.h rewrite, and the mi patch coming in
Can't be needed, we've never defined it in modular xserver.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 54
1 file changed, 54 deletions(-)
diff --git
I think the externs are there for the non-gcc case? And maybe there was
some assembly code to implement that once? Whatever, at this point on
ppc the compiler is either gcc or willing to pretend. The macros below
the decls take care of the actual eieio so the externs can just go.
Also remove a
2.6.0 was December 2003, you've had plenty of time to get your head in
the game.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 7 ---
1 file changed, 7 deletions(-)
diff --git a/hw/xfree86/common/compiler.h
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 64 +---
1 file changed, 1 insertion(+), 63 deletions(-)
diff --git a/hw/xfree86/common/compiler.h b/hw/xfree86/common/compiler.h
You can't tell from context here, but this is all inside #ifdef
__GNUC__, so this conditional can't do squat.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 2 --
1 file changed, 2 deletions(-)
diff --git
__USLC__ appears to mean the SCO OpenServer compiler, which configure.ac
doesn't think is an OS the xfree86 ddx supports. The conditionals
surrounding these pragmas effectively mean if not gcc and not Sun C,
and probably arbitrary pragmas aren't supported by arbitrary compilers.
Reviewed-by:
MetaWare High C++ compiler? xfree86 cvs history shows this being added
in a commit whose text is, classically, updates. metaware.com
redirects to a 404 on synopsys.com, which to me indicates it's not super
important to them, and their order form won't even tell you how much the
thing costs. At
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 61 +---
1 file changed, 1 insertion(+), 60 deletions(-)
diff --git a/hw/xfree86/common/compiler.h b/hw/xfree86/common/compiler.h
Only used by mach64's XAA code, which isn't built if XAA isn't
available, and it isn't.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 13 -
1 file changed, 13 deletions(-)
diff --git
Nothing in the server defines this, nor do any drivers.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/hw/xfree86/common/compiler.h
The top of this file already defines __sparc__ if __sparc is defined.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/xfree86/common/compiler.h
All of this is inside #ifdef __GNUC__, between that and configure.ac we
can assume there's a unixy thing under us. Given that there's no real
reason to limit the arch paths to particular OSes, so let's not.
The final #elif here, combined with the ones before it, effectively said
if not (alpha
Non-barrier-emitting MMIO writes. They appear to be utterly unused,
burn it all down.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h| 201 +++-
Whatever these are, they're not something grep can find, they must not
be used.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 4
1 file changed, 4 deletions(-)
diff --git a/hw/xfree86/common/compiler.h
Map SPARC_MMIO_IS_BE and PPC_MMIO_IS_BE to MMIO_IS_BE and use the same
macros for both since they're identical.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 39 ---
1 file
The majority of arches end up on the right-shift path here. I can't
think of any arch where that'd be slower than a divide, and semantically
it makes more sense to think of this as a shift operation anyway.
Signed-off-by: Adam Jackson a...@redhat.com
---
mi/micoord.h | 20
And remove the redundant redecl from the nds32 section.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/hw/xfree86/common/compiler.h
I guess this is meant to stub out all I/O port calls? Whatever, it's
not been defined by the buildsystem at least as far back as monolith
6.8.2.
Reviewed-by: Julien Cristau jcris...@debian.org
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/compiler.h | 40
isItTimeToYield in the conditional effectively didn't do anything here.
Take it out, and remove the comment since LBX proxies aren't a thing for
us anymore.
Signed-off-by: Adam Jackson a...@redhat.com
---
dix/dispatch.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
No real unifying theme here besides cleanup.
Two patches here do require trivial driver changes. 06/22 removes an
interface that simply can't work; naturally, two drivers (trident and
xgixp) do in fact use it. The fix requires no thought beyond
copypasta of, say, vesa's shadow setup code.
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/kdrive/Xkdrive.man | 7 ---
1 file changed, 7 deletions(-)
diff --git a/hw/kdrive/Xkdrive.man b/hw/kdrive/Xkdrive.man
index b37f9f1..c3e2089 100644
--- a/hw/kdrive/Xkdrive.man
+++ b/hw/kdrive/Xkdrive.man
@@ -4,10 +4,6 @@
.SH NAME
Xkdrive
git history is reference enough, thanks.
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/os-support/bsd/arm_video.c | 139 --
1 file changed, 139 deletions(-)
diff --git a/hw/xfree86/os-support/bsd/arm_video.c
b/hw/xfree86/os-support/bsd/arm_video.c
I ported these to pciaccess in:
commit 858fbbb40d7c69540cd1fb5315cebf811c6e7b3f
Author: Adam Jackson a...@redhat.com
Date: Fri Sep 16 13:33:04 2011 -0400
pci: Port xf86MapLegacyIO to pciaccess
As of yet there are still no drivers using them, and there's not a lot
of value
Signed-off-by: Adam Jackson a...@redhat.com
---
Xext/saver.c | 16 +---
1 file changed, 1 insertion(+), 15 deletions(-)
diff --git a/Xext/saver.c b/Xext/saver.c
index 8e92fdf..2c14ea0 100644
--- a/Xext/saver.c
+++ b/Xext/saver.c
@@ -467,9 +467,6 @@ CreateSaverWindow(ScreenPtr
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/modes/xf86Rotate.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/xfree86/modes/xf86Rotate.c b/hw/xfree86/modes/xf86Rotate.c
index 1627e61..54cbf2e 100644
--- a/hw/xfree86/modes/xf86Rotate.c
+++ b/hw/xfree86/modes/xf86Rotate.c
@@
The giant OBSOLETE DO NOT USE comment has been there since 2000,
probably it's safe to nuke by now.
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/xf86.h | 8
hw/xfree86/common/xf86pciBus.c | 27 ---
2 files changed, 35 deletions(-)
i810, mga, savage, and tdfx do reference these slots, but only to set
them to NULL, so while this does have API impact it's not actually used.
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/dri/dri.c | 73
hw/xfree86/dri/dri.h | 8
This came in between XFree86 4.3 and 4.4, I'm not entirely sure what it
was meant to do.
Signed-off-by: Adam Jackson a...@redhat.com
---
mi/mi.h | 3 ---
mi/miwindow.c | 14 --
2 files changed, 17 deletions(-)
diff --git a/mi/mi.h b/mi/mi.h
index feba5cb..d5a5ba3 100644
---
Given the #if 0 this was wrapping for no effect.
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/xf86RandR.c | 32
1 file changed, 32 deletions(-)
diff --git a/hw/xfree86/common/xf86RandR.c b/hw/xfree86/common/xf86RandR.c
index 2418731..08f656b
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/os-support/bus/xf86Pci.h | 12
1 file changed, 12 deletions(-)
diff --git a/hw/xfree86/os-support/bus/xf86Pci.h
b/hw/xfree86/os-support/bus/xf86Pci.h
index f69e55b..0397796 100644
--- a/hw/xfree86/os-support/bus/xf86Pci.h
Here's a trip down memory lane. Back when we merged kdrive we adopted
kdrive's version of shadow, which used damage directly instead of
hand-rolling it. However a couple of Xorg drivers referred to the
accumulated damage region in the shadow private directly, so I added a
hack to copy the damage
Cargo-culted from DRI1, not actually used for anything.
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xquartz/xpr/dri.c | 51 ---
hw/xquartz/xpr/dri.h | 8
pseudoramiX/pseudoramiX.c | 19 --
3 files changed, 78
XkbInterestPtrs are created by clients that already exist, meaning,
clients that have already had ProcVector installed as something other
than InitialProcVector.
Signed-off-by: Adam Jackson a...@redhat.com
---
xkb/xkbEvents.c | 9 -
1 file changed, 9 deletions(-)
diff --git
Arguably this would be useful API, but it's never called, and a careful
reading of the CPClipMask path reveals that callers would be fairly
disappointed.
Signed-off-by: Adam Jackson a...@redhat.com
---
render/picture.c| 81 -
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/os-support/bus/xf86Pci.h | 4
1 file changed, 4 deletions(-)
diff --git a/hw/xfree86/os-support/bus/xf86Pci.h
b/hw/xfree86/os-support/bus/xf86Pci.h
index 0397796..5b34310 100644
--- a/hw/xfree86/os-support/bus/xf86Pci.h
+++
Never been built since m12n, can't be needed.
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/doc/ddxDesign.xml | 3 +-
hw/xfree86/vgahw/Makefile.am | 2 -
hw/xfree86/vgahw/vgaCmap.c | 275 ---
3 files changed, 1 insertion(+), 279
The first patch had a c/p typo, plus didn't cope too well with the capabilities
being toggled one by one as weston does.
I also noticed that there is another patch around by Boyan Ding to fix the
same issue. It seemed to me that the behavior I implemented is the closest
to what (rootful?) Xorg
Never filled in.
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/os-support/xf86OSpriv.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/hw/xfree86/os-support/xf86OSpriv.h
b/hw/xfree86/os-support/xf86OSpriv.h
index 7f003e8..b56f45a 100644
--- a/hw/xfree86/os-support/xf86OSpriv.h
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/common/xf86Cursor.c | 17 +
1 file changed, 1 insertion(+), 16 deletions(-)
diff --git a/hw/xfree86/common/xf86Cursor.c b/hw/xfree86/common/xf86Cursor.c
index c6abf12..92c08af 100644
--- a/hw/xfree86/common/xf86Cursor.c
Anytime a capability is first reported, the device is created, but after
that, it is only disabled/enabled.
This is a closer behavior to what Xorg does on VT switch, at the expense
of maybe leaving a dangling physical device if a capability goes for good.
Otherwise, any DeviceIntPtr (re)created
The comment lies, shm hasn't used this code since:
commit fdef7be5c8d5989e0aa453d0a5b86d0a6952e960
Author: Alan Coopersmith alan.coopersm...@sun.com
Date: Tue Oct 9 18:44:04 2007 -0700
Sun bug 6589829: include zoneid of shm segment in access [...]
Signed-off-by: Adam
Signed-off-by: Adam Jackson a...@redhat.com
---
doc/Xserver-spec.xml | 6 ++
include/os.h | 37 +
os/utils.c | 48
3 files changed, 3 insertions(+), 88 deletions(-)
diff --git
This code is nonsensical. You end up creating a screen-sized pixmap
that's totally detached from everything else, which you then listen for
damage on, which means you'll never hear any damage, which means your
shadow update hooks will never get called. Any driver using this would
be sorely
On 22 July 2014 16:46, Adam Jackson a...@redhat.com wrote:
XkbInterestPtrs are created by clients that already exist, meaning,
clients that have already had ProcVector installed as something other
than InitialProcVector.
Signed-off-by: Adam Jackson a...@redhat.com
Reviewed-by: Daniel Stone
Hi,
On 22 July 2014 16:55, Carlos Garnacho carl...@gnome.org wrote:
Anytime a capability is first reported, the device is created, but after
that, it is only disabled/enabled.
This is a closer behavior to what Xorg does on VT switch, at the expense
of maybe leaving a dangling physical
ping?
From: David Ung [dav...@nvidia.com]
Sent: Thursday, July 17, 2014 5:19 PM
To: xorg-devel@lists.x.org
Cc: David Ung
Subject: [PATCH] randr: Fix logic in RRPointerToNearestCrtc
RRPointerToNearestCrtc is suppose to snap to the nearest Crtc,
but the
On 07/22/14 07:58 AM, Adam Jackson wrote:
Resend of the equivalent series from May. I'm sure I had to touch up
some of it to account for whatever arch patches we added between then
and now, but I forget which, so the individual patches lack versioning;
sorry about that.
Between this, the
On 07/22/14 08:46 AM, Adam Jackson wrote:
The comment lies, shm hasn't used this code since:
commit fdef7be5c8d5989e0aa453d0a5b86d0a6952e960
Author: Alan Coopersmith alan.coopersm...@sun.com
Date: Tue Oct 9 18:44:04 2007 -0700
Sun bug 6589829: include zoneid of shm
https://bugs.freedesktop.org/show_bug.cgi?id=77903
--- Comment #6 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #5)
did this re-appear ?
No, you seem to be using the standalone glamor 0.6.0 release or another
snapshot of the standalone glamor tree which doesn't have the fix for
These things were nagging at me while I was writing the RandR patch. They
remove a lot of code so I will only feel comfortable pushing them once they are
reviewed. Thanks a lot.
Connor Behan (5):
Unify allocators
Unify byte swappers
Remove R128ConnectorType and R128BIOSConnector
Remove
RandR and Xv were using almost the same code to grab offscreen memory
from EXA and XAA.
Signed-off-by: Connor Behan connor.be...@gmail.com
---
src/r128.h | 1 +
src/r128_crtc.c | 72 --
src/r128_probe.h | 7 +---
src/r128_video.c | 103
In the radeon UMS driver these make sense because there are many types
of radeon cards and new ones keep coming out. With r128 on the other
hand, there are only three types of cards (VGA only, DVI only and
Mobility). The extra organization that these data structures allow is
not necessary.
The cursor loading function was using a lot of code to swap bytes for
big endian systems. For awhile now, the solid picture support for EXA
has had a more optimized function that does the same thing.
Signed-off-by: Connor Behan connor.be...@gmail.com
---
src/r128_cursor.c | 67
I have yet to see a use for the DGA code included in the driver.
According to radeon commits, it should be safe to replace it with DiDGA.
Signed-off-by: Connor Behan connor.be...@gmail.com
---
src/Makefile.am | 2 +-
src/r128.h| 13 --
src/r128_accel.c | 4 +-
src/r128_dga.c|
There are probably no reasons left to use Xinerama over xrandr. This
removes the screen based dualhead code and the BIOS Display option in
xorg.conf. Additionally, R128ValidMode() is wrapped so that it can be
aware of multiple displays.
Even though some Crtc functions refer to them, PanelXRes and
69 matches
Mail list logo