Hi ,
If the ViewSonic display (EDID vendor "VSC", prod id 19227) is changed to low
than "1280x1024" ( 800x600, 640x480,
1024x768), there are 2 black borders on the top and bottom of the screen, while
resolution with "1280x1024" works fine.
Because the display don't support vertical fresh over 75
On Sunday 28 September 2008, Peter Hutterer wrote:
> On Sat, Sep 27, 2008 at 06:10:32PM +0100, Magnus Kessler wrote:
> > Since updating to the current git version of xorg-server, inputproto
> > and xf86-input-synaptics I observe extra pointer movements for every
> > event generated by the touchpad.
On Sun, Sep 28, 2008 at 08:23:51AM +0100, Magnus Kessler wrote:
> I have just reverted the part of commit
> c405a69f83dab77cfe6c76f718a3ca5614a85918 that passes the actual x/y ranges
> to xf86InitValuatorAxisStruct. Now the extra movement is gone, but I get a
> somewhat quicker cursor movement
The creation of the repeater fifo in the synaptics driver looks dubious. The
file mode should be ORed with the S_IFIFO flag and the dev parameter should
be null. The mknod(3p) man page suggests using mkfifo instead.
The following patch (compile tested only) uses mkfifo and the symbolic names
fo
> I'd bet against that :-). Core 2 has magnificent SSE performance indeed,
> but that's true for MMX just as well.
Well, Core2 (and AMD K10) got support for 128bit operations per clock,
whereas previous processors only supported 64bit at once, and took 2
cycles for 128 bit operations.
MMX is just 6
Peter,
On Tue, Sep 23, 2008 at 04:01:19PM +0930, Peter Hutterer wrote:
> On Mon, Sep 22, 2008 at 08:08:37PM +0200, Lukas Hejtmanek wrote:
> > the current git head of the Xserver segfaults on any keystroke. Trace is
> > attached:
>
> Can I have a log please?
any progress here?
--
Lukáš Hejtmáne
On Sun, Sep 28, 2008 at 10:09:01AM +0100, Magnus Kessler wrote:
> The creation of the repeater fifo in the synaptics driver looks dubious. The
> file mode should be ORed with the S_IFIFO flag and the dev parameter should
> be null. The mknod(3p) man page suggests using mkfifo instead.
Agreed.
>
On Sunday 28 September 2008, Peter Hutterer wrote:
> On Sun, Sep 28, 2008 at 10:09:01AM +0100, Magnus Kessler wrote:
> > The creation of the repeater fifo in the synaptics driver looks
> > dubious. The file mode should be ORed with the S_IFIFO flag and the dev
> > parameter should be null. The mkno
On 28.09.2008 11:52, Clemens Eisserer wrote:
>> I'd bet against that :-). Core 2 has magnificent SSE performance indeed,
>> but that's true for MMX just as well.
> Well, Core2 (and AMD K10) got support for 128bit operations per clock,
> whereas previous processors only supported 64bit at once, and
Hi,
I have a laptop with Synaptics touchpad that feels "out of control"
even after playing with the parameters for a couple of nights. I
think the reason is that vertical motion is faster than horizontal
motion.
"synclient -m" shows that x coordinates vary between 1060 - 5900 and y
coordinates b
Hello,
Here is a patch to add the support for the internet keys of my Genius
keyboard.
Samuel
diff --git a/rules/base.lists.part b/rules/base.lists.part
index b08ab24..6191894 100644
--- a/rules/base.lists.part
+++ b/rules/base.lists.part
@@ -38,7 +38,7 @@
cymotionlinux \
Can anyone tell me the status of AIGLX and Xephyr?
Thanks
--Yan
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Tomeu Vizoso wrote:
> Ooops. cc'ing to some other people/list in the hope someone more
> knowledgeable than me will comment.
Thanks. Please Cc me on posts like these to make sure I don't miss them.
No, it doesn't bother me to receive 0.001% more mail.
I've also Cc'd the Xorg list in case some
On Sun, Sep 28, 2008 at 19:49, Simon Thum <[EMAIL PROTECTED]> wrote:
>> I have a laptop with Synaptics touchpad that feels "out of control"
>> even after playing with the parameters for a couple of nights. I
>
> One of the important thing with synaptics is that it does acceleration,
> which is als
Peter Hutterer wrote:
> On Sun, Sep 28, 2008 at 08:23:51AM +0100, Magnus Kessler wrote:
>> I have just reverted the part of commit
>> c405a69f83dab77cfe6c76f718a3ca5614a85918 that passes the actual x/y ranges
>> to xf86InitValuatorAxisStruct. Now the extra movement is gone, but I get a
>> somew
Yan Seiner seiner.com> writes:
>
> Can anyone tell me the status of AIGLX and Xephyr?
AIGLX has been merged into main since ages. It is even on by default if your
driver supports it in current releases.
Xephyr is available in distributions; but I do not know if it has been part of
an officia
Barry Scott wrote:
> We would love to have a -nocursor that got ride of the cursor from the
> screen added to Xorg.
>
> We have a patch to do this that we use.
Maybe a little off-topic here, but I back this proposal of totally
disabling cursor at X level. We also use Barry's patch:
http://lists.
Riccardo Lucchese wrote:
>> Was fbdev running with EXA or XAA? (does fbdev even support EXA?)
> http://www.x.org/wiki/ExaStatus lists fbdev in the `Probably unsuitable
> for EXA support' section; so, I guess XAA.
Confirmed: there's absolutely no EXA code in xf86-video-fbdev. Too bad,
it would h
On Sunday 28 September 2008, Simon Thum wrote:
> Peter Hutterer wrote:
[...]
> > Check out GetPointerEvents in xserver/dix/getevents.c.
> >
> > We take valuator coordinates, scale them to screen coords based on the
> > axis information and then scale them back to device coords*.
> >
> > The screen
Hi,
I would like to know if there was a possibility to use "intel" drivers
(not i810) with *two displays* (e.g. :0.0 and :0.1) but only *one X
server*.
I could do it with i810 drivers, but then I switched to the "intel"
one, which is better in many ways, but not for my dual screen purpose
!
I'm cu
Tero Saarni wrote:
> I've disabled acceleration with xset m 1 1 and set both MinSpeed and
> MaxSpeed to 0.1. The pointer moves the same distance vertically and
> horizontally but as the touchpad is twice as wide as it is tall I
> would have expected it to travel twice the distance horizontally.
We
Romain Chossart gmail.com> writes:
>
> Hi,
>
> I would like to know if there was a possibility to use "intel" drivers
> (not i810) with *two displays* (e.g. :0.0 and :0.1) but only *one X
> server*.
[...]
> - Maximizing takes whole "virtual" screen
This is a bug in your window manager, AFAIK
Andrew Barr wrote:
> Yan Seiner seiner.com> writes:
>
>
>> Can anyone tell me the status of AIGLX and Xephyr?
>>
>
> AIGLX has been merged into main since ages. It is even on by default if your
> driver supports it in current releases.
>
> Xephyr is available in distributions; but I do no
On Sun, 2008-09-28 at 20:41 +, Andrew Barr wrote:
> Romain Chossart gmail.com> writes:
>
> >
> > Hi,
> >
> > I would like to know if there was a possibility to use "intel" drivers
> > (not i810) with *two displays* (e.g. :0.0 and :0.1) but only *one X
> > server*.
>
> [...]
>
> > - Maximi
Romain Chossart gmail.com> writes:
> I would like to know if there was a possibility to use "intel" drivers
> (not i810) with *two displays* (e.g. :0.0 and :0.1) but only *one X
> server*.
FWIW, the driver maintainers are reasonably good about keeping and updated and
informative man page (part
On Sun, Sep 28, 2008 at 03:11:46PM +0100, Magnus Kessler wrote:
> Testing status against EEXIST is wrong and we should check errno instead if
> we want to allow the use of an existing file. However, since we pass a file
> name that in principle could be any existing file (not just fifos) is there
I have read lots of things on site site... no information about my
concern is given infortunately.
--
Romain Chossart
On Sun, Sep 28, 2008 at 5:56 PM, Andrew Barr
<[EMAIL PROTECTED]> wrote:
> Romain Chossart gmail.com> writes:
>
>> I would like to know if there was a possibility to use "intel" dr
On Sun, 2008-09-28 at 12:31 -0700, Romain Chossart wrote:
> Hi,
>
> I would like to know if there was a possibility to use "intel" drivers
> (not i810) with *two displays* (e.g. :0.0 and :0.1) but only *one X
> server*.
Your terminology isn't quite correct, what you're calling displays, are
actual
On Sun, Sep 28, 2008 at 07:26:06PM +0200, Simon Thum wrote:
>> The screen coords are used to move the cursor and the scaling is done based
>> on
>> the axis ranges. Hence the different acceleration when you change the axis
>> range to 0,-1 (in which case the screen coords are used as axis ranges).
29 matches
Mail list logo