2008/11/29 Colin Guthrie [EMAIL PROTECTED]:
eatdirt wrote:
Hi all,
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
On Sat 29.Nov'08 at 18:52:55 +, Matthew Garrett wrote:
On Sat, Nov 29, 2008 at 06:37:48PM +0100, eatdirt wrote:
1) Today, if you are not under the gas factory desktops, gnome/kde, you
don't need HAL. I never used/needed HAL. Will xorg still allow users to
not use HAL?
Yes,
2008/11/30 Kalle Vahlman [EMAIL PROTECTED]:
2008/11/29 Colin Guthrie [EMAIL PROTECTED]:
eatdirt wrote:
Hi all,
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
Hi folks
Today I looked at the usage of I32 in symbols/inet and found
interesting thing. There are 31 cases where it is used as XF86WWW and
17 cases where it is used as XF86HomePage. Could anyone explain the
substantial difference between these 2 keysyms (in the context of
desktop)? May be, we
Thanks again for the reply. Please see embedded comments.
- gmane wrote:
Actually this is wrong. We didn't split out the intel drivers back out
at that point it seems. I guess it was only did that later.
I'm trying to remember if there is was a problem with 2008.0 or not. It
was
Hello,
I'm using X.Org 1.5.2 (the one shipped with ubuntu intrepid ibex) and
I would like to setup my keyboard in the following way:
- use two layouts: US and french
- switch between the layouts by pressing both alt keys together
- use the caps lock key as compose
I tried this command:
$
- gw1500se wrote:
If anyone knows when the below problem was fixed (e.g. in what version)
that would be useful as I can then do a backport for you on 2008.0.
Just for the record, neither vesa nor vga work either.
Hmm, sounds like something more fundamental is wrong then. I'd imagine
On Fri, Nov 28, 2008 at 10:20:55AM -0800, Keith Packard wrote:
On Fri, 2008-11-28 at 17:03 +1000, Peter Hutterer wrote:
(a huge pile of patches)
These all look good to me; can you push them to a branch off of 1.6 so I
can merge them in?
I think I added that url in my first email, but
James,
Thanks for the insightful information - really interesting.
Unfortunately, as we all know, XKB is not that smart - it cannot
distinguish application launch context from application control
context. So a keysym has to be mapped to the keycode unconditionally.
My question was: what would be
On Fri, Nov 28, 2008 at 05:58:22AM -0800, Sebastian Glita wrote:
The mice and keyboards in xf86-input-evdev/src/evdev.c:EvdevProbe handle a
multiple-capability device wrong for my use.
I have a wireless USB receiver so I use both a mouse and a keyboard with the
same token.
In
On Fri, Nov 28, 2008 at 02:55:55PM +0200, Timo Aaltonen wrote:
---
hw/xfree86/common/xf86Config.c |5 +++--
hw/xfree86/doc/man/xorg.conf.man.pre |2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/hw/xfree86/common/xf86Config.c
Sergey == Sergey Udaltsov [EMAIL PROTECTED] writes:
Sergey Unfortunately, as we all know, XKB ... cannot distinguish
Sergey application launch context from application control context.
Apologies for ambiguity. These are two completely different keys at the
USB level; it is really the keyboard
Twas brillig at 10:28:24 01.12.2008 UTC+10 when [EMAIL PROTECTED] did gyre and
gimble:
PH Most other settings in the more popular input drivers are now
PH configurable at runtime too (where now == server 1.6), so you
PH basically just have to convince your DE to provide pretty
PH interfaces
Just ignore devices after MAXDEVICES has been reached, but warn the user that
the devices are ignored.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
hw/xfree86/common/xf86InPriv.h |2 +-
hw/xfree86/common/xf86Init.c |4 +++-
hw/xfree86/common/xf86Xinput.c | 29
Peter Hutterer wrote:
On Sun, Nov 30, 2008 at 09:17:47PM +0500, Alexander E. Patrakov wrote:
However, xorg gets things like keyboard layouts from HAL. This is also
policy, and also important to get i18n right. But, for some reason, this
is allowed to exist in HAL, and default mount options
Peter Hutterer wrote:
adding the list back
On Mon, Dec 01, 2008 at 09:55:03AM +0500, Alexander E. Patrakov wrote:
Obvious problem: it is too late to set the keyboard layout in the
desktop environment. The user has to type the login and the password
into the display manager, and the
On Mon, Dec 01, 2008 at 10:47:06AM +0500, Alexander E. Patrakov wrote:
Also, currently, for unconfigured Xorg, such newly-added keyboard gets
the us layout. This is also a hard-coded policy, should we remove it?
Ignoring both the rhetoric and the fact that neither of the input
maintainers are
On Mon, Dec 01, 2008 at 10:47:06AM +0500, Alexander E. Patrakov wrote:
Peter Hutterer wrote:
adding the list back
On Mon, Dec 01, 2008 at 09:55:03AM +0500, Alexander E. Patrakov wrote:
Obvious problem: it is too late to set the keyboard layout in the
desktop environment. The user has to
Below is the protocol spec for the X Generic Event Extension (XGE). It'll be
shipped with 1.6 even though there won't be any consumers for it yet.
(This is the current proto/xextproto/geproto.txt file as valid in my tree. Will
be pushed pending no objections.)
Cheers,
Peter
Peter Hutterer wrote:
I was referring to DE as a concept, not as a specific implementation. It
counts as part of whatever you're running afterwards, may be gnome, kde,
xfce or my-happy-bunch-of-shellscripts.
OK. Anyway, my point about XDM as the example implementation not
following the modern
I just want to voice my dislike of the HAL input layer stuff, but just
that it's the default. Right now that doesn't make any sense.
I try to keep uptodate with current GIT to make sure sparc doesn't
break.
But what I spend most of my time doing is figuring out what new
default breaks Xorg on
Hi,
The following program (requires XInput2) warps my pointer to (0,0)
instead of the requested (600,400). I'd be interested to know whether
this happens for other people, and if there's something obviously wong
with my code. Thanks!
// gcc -o xtest xtest.c -Wall -I/usr/include/X11 -lX11
On Mon, Dec 01, 2008 at 04:15:47PM +1000, Peter Hutterer wrote:
Below is the protocol spec for the X Generic Event Extension (XGE). It'll be
shipped with 1.6 even though there won't be any consumers for it yet.
(This is the current proto/xextproto/geproto.txt file as valid in my tree.
Will
23 matches
Mail list logo
