exaGetPixmapFirstPixel Question
Hi.
I am trying to make a ddx exa video driver at my owned target.
When I test the driver, I have met some error from Xserver.
The error log is bleow,
=
Fatal server error:
exaGetPixmapFirstPixel called for invalid bpp 1
=
And backtrace at the exaGetPixmapFirstPixel function is below
==
Breakpoint 1, exaGetPixmapFirstPixel (pPixmap=0x477618)
at ../../exa/exa_unaccel.c:507
507 switch (pPixmap->drawable.bitsPerPixel) {
(gdb) bt
#0 exaGetPixmapFirstPixel (pPixmap=0x477618) at ../../exa/exa_unaccel.c:507
#1 0x406529c0 in exaTryDriverSolidFill (pSrc=0x488ec0, pDst=0x488ce0,
xSrc=0, ySrc=0, xDst=5, yDst=10, width=1, height=127)
at ../../exa/exa_render.c:300
#2 0x40654c88 in exaComposite (op=1 '\001', pSrc=0x488ec0, pMask=0x0,
pDst=0x488ce0, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=5, yDst=10,
width=1, height=127) at ../../exa/exa_render.c:923
#3 0x0014ccc4 in damageComposite (op=1 '\001', pSrc=0x488ec0, pMask=0x0,
pDst=0x488ce0, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=5, yDst=10,
width=1, height=127) at ../../../miext/damage/damage.c:643
#4 0x0013392c in CompositePicture (op=1 '\001', pSrc=0x488ec0, pMask=0x0,
pDst=0x488ce0, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=5, yDst=10,
width=1, height=127) at ../../render/picture.c:1718
#5 0x0013b24c in ProcRenderComposite (client=0x433898)
at ../../render/render.c:723
#6 0x00140324 in ProcRenderDispatch (client=0x433898)
at ../../render/render.c:2056
#7 0x00024650 in Dispatch () at ../../dix/dispatch.c:445
#8 0x00022414 in main (argc=11, argv=0xbec9bd04, envp=0xbec9bd34)
at ../../dix/main.c:285
(gdb) p pPixmap->drawable.bitsPerPixel
$1 = 1 '\001'
=
At exaGetPixmapFirstPixel, the xserver calls the FatalError when the bpp of
the pixmap is 1.
I have two questions at this point.
1. Is this exa module bug? I mean the xserver has the bug?
2. Or my ddx video driver does not being working properly? Especially,
should I fix the createpixmap in my ddx driver?
- Should the my ddx driver deal with 1bpp pixmap as the special case
when the driver create the pixmap or modify the pixmap header? I mean that
the createpixmap in the ddx driver makes the bitsPerPixel 8bits
when the pixmap with 1bpp is requested .
Is there anyone who has the solution in this case?
Thanks.
soolim.
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Display shifted right maybe 10px
On 01/18/2010 02:47 AM, cour...@web.de wrote: > Hi Steve > > Have you tried to launch X without xorg.conf? > provided you have hal and dbus running? > It might be related to this: https://bugzilla.redhat.com/show_bug.cgi?id=511345 Is the mouse cursor not shifted? Adam signature.asc Description: OpenPGP digital signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
Well, according to my primitive understanding, xmodmap is normally
used for a little bit of tweaking of the keyboard layout (fiddling
with delete and backspace, for instance, or swapping CapsLock and
Ctrl).
Your file looks odd to me ("slash question slash question slash
question"). Since you didn't write it, it was presumably generated by
some piece of software, and maybe a confused and over-enthusiastic
piece of software. I don't have 248 keys on my keyboard.
If you are really lucky, then this was the entire source of your
problem. It might be informative to run the xmodmap command with this
file as an argument, and see if it instantly causes problems.
Cheers
Tom
2010/1/18 Ryan Daly :
> On 01/18/2010 04:23 PM, Tom Cowell wrote:
>> What was/is in the .xmodmaprc?
>
> 248 lines of things like this:
>
> keycode 61 = slash question slash question slash question
> keycode 62 = Shift_R NoSymbol Shift_R NoSymbol Shift_R
> keycode 63 = KP_Multiply XF86_ClearGrab KP_Multiply XF86_ClearGrab
> KP_Multiply XF86_ClearGrab
> keycode 64 = Alt_L Meta_L Alt_L Meta_L Alt_L Meta_L
> keycode 65 = space NoSymbol space NoSymbol space
> keycode 66 = Caps_Lock NoSymbol Caps_Lock NoSymbol Caps_Lock
> --
>
>
> This message and any files transmitted within are intended
> solely for the addressee or its representative and may
> contain company sensitive information. If you are not the
> intended recipient, notify the sender immediately and delete
> this message. Publication, reproduction, forwarding, or
> content disclosure is prohibited without the consent of the
> original sender and may be unlawful.
>
> Concurrent Technologies Corporation and its Affiliates.
> www.ctc.com 1-800-282-4392
>
>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/18/2010 04:23 PM, Tom Cowell wrote: > What was/is in the .xmodmaprc? 248 lines of things like this: keycode 61 = slash question slash question slash question keycode 62 = Shift_R NoSymbol Shift_R NoSymbol Shift_R keycode 63 = KP_Multiply XF86_ClearGrab KP_Multiply XF86_ClearGrab KP_Multiply XF86_ClearGrab keycode 64 = Alt_L Meta_L Alt_L Meta_L Alt_L Meta_L keycode 65 = space NoSymbol space NoSymbol space keycode 66 = Caps_Lock NoSymbol Caps_Lock NoSymbol Caps_Lock -- This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
What was/is in the .xmodmaprc? 2010/1/18 Ryan Daly : > On 01/18/2010 03:17 PM, Ryan Daly wrote: >> I was able to start Xorg w/ 'startx' as root. I'm writing trace files >> out, so as soon as I get it to exit on me, I'll look through and see >> what's left. > > One bad thing... The strace files started taking up so much room that I > needed to stop the session I was running. > > But, I noticed something while I was running as "root." I was up for > about 3 hours without any trouble. I noticed while I was logged in that > my alt, shift, and ctrl keys weren't working. That prompted me to start > poking around and I found that I had a $HOME/.xmodmaprc. I'm wondering > if this could have any impact on things. Could it be possible that > something was mapped in such a way that when a particular key sequence > was hit it caused my session to exit? I know Gnome maps keys on its > own. Maybe I was confusing things by having $HOME/.xmodmaprc in place. > > I have since removed $HOME/.xmodmaprc and restarted my X session, but > I'm running as myself. I'm still unable to strace this because of the > earlier permissions issue that was posted. I'd still like to hear > thoughts regarding this, though. Thanks. > > > This message and any files transmitted within are intended > solely for the addressee or its representative and may > contain company sensitive information. If you are not the > intended recipient, notify the sender immediately and delete > this message. Publication, reproduction, forwarding, or > content disclosure is prohibited without the consent of the > original sender and may be unlawful. > > Concurrent Technologies Corporation and its Affiliates. > www.ctc.com 1-800-282-4392 > > ___ > 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
Re: Xorg crashes...
On 01/18/10 13:12, Ryan Daly wrote: > On 01/18/2010 03:17 PM, Ryan Daly wrote: >> I was able to start Xorg w/ 'startx' as root. I'm writing trace files >> out, so as soon as I get it to exit on me, I'll look through and see >> what's left. > > One bad thing... The strace files started taking up so much room that I > needed to stop the session I was running. > > But, I noticed something while I was running as "root." I was up for > about 3 hours without any trouble. I noticed while I was logged in that > my alt, shift, and ctrl keys weren't working. That prompted me to start > poking around and I found that I had a $HOME/.xmodmaprc. I'm wondering > if this could have any impact on things. Could it be possible that > something was mapped in such a way that when a particular key sequence > was hit it caused my session to exit? I know Gnome maps keys on its > own. Maybe I was confusing things by having $HOME/.xmodmaprc in place. > > I have since removed $HOME/.xmodmaprc and restarted my X session, but > I'm running as myself. I'm still unable to strace this because of the > earlier permissions issue that was posted. I'd still like to hear > thoughts regarding this, though. Thanks. > > could be... but then again you might just receive some error message on your screen once exiting out of the xserver. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/18/2010 03:17 PM, Ryan Daly wrote: > I was able to start Xorg w/ 'startx' as root. I'm writing trace files > out, so as soon as I get it to exit on me, I'll look through and see > what's left. One bad thing... The strace files started taking up so much room that I needed to stop the session I was running. But, I noticed something while I was running as "root." I was up for about 3 hours without any trouble. I noticed while I was logged in that my alt, shift, and ctrl keys weren't working. That prompted me to start poking around and I found that I had a $HOME/.xmodmaprc. I'm wondering if this could have any impact on things. Could it be possible that something was mapped in such a way that when a particular key sequence was hit it caused my session to exit? I know Gnome maps keys on its own. Maybe I was confusing things by having $HOME/.xmodmaprc in place. I have since removed $HOME/.xmodmaprc and restarted my X session, but I'm running as myself. I'm still unable to strace this because of the earlier permissions issue that was posted. I'd still like to hear thoughts regarding this, though. Thanks. This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/11/2010 09:16 AM, Tom Cowell wrote: > Yes, that's what I meant. I suppose the action of strace (and > valgrind, probably) will slow things down, so maybe the "timeout" > messages can be taken at face value, and maybe there is a timeout that > can be increased so that the strace/valgrind of startx as root can be > made to work. > > I'll look in man pages and let you know if I find anything. > I was able to start Xorg w/ 'startx' as root. I'm writing trace files out, so as soon as I get it to exit on me, I'll look through and see what's left. This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
MuTouch touchscreen drivers - Inverted Y axis
Hi, I was using the MuTouch driver with Xorg 6.9 and everything was working perfectly. Then I updated Xorg to version 1.6.1 and the MuTouch driver from git (2009-07-17) and the Y axis was suddently inverted. I also tried with MuTouch version 1.2.1 and I had the same result. Is this a bug with X, the MuTouch driver or my configuration file? I tried swapping the MinY and MaxY values and it worked, but I was wondering if this is the expected behaviour, or is it a bug? Thanks, Christopher Camden Relevant xorg.conf part: Section "InputDevice" Identifier "touchscreen_serial" Driver "mutouch" Option "Device" "/dev/ttyS1" Option "BaudRate" "2400" Option "InputFashion" "Touchpanel" Option "MaxX" "16350" Option "MaxY" "16350" Option "MinX" "0" Option "MinY" "0" Option "Name" "MUTOUCH:TOUCHSCREEN" Option "ReportingMode" "Scaled" Option "SendCoreEvents" "on" Option "Type" "Finger" Option "Screen" "0" EndSection Relevant Xorg.0.log part: (II) LoadModule: "mutouch" (II) Loading /lib/xorg/modules/input//mutouch_drv.so (II) Module mutouch: vendor="X.Org Foundation" compiled for 1.6.1, module version = 1.2.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 [...] (**) MicroTouch FINGER input device: /dev/ttyS1 (**) Option "SendCoreEvents" "on" (**) Option "CorePointer" (**) FINGER: always reports core events (**) Microtouch X device name: FINGER (**) Microtouch associated screen: 0 (**) Option "MaxX" "16350" (**) Microtouch maximum x position: 16350 (**) Option "MinX" "0" (**) Microtouch minimum x position: 0 (**) Option "MaxY" "16350" (**) Microtouch maximum y position: 16350 (**) Option "MinY" "0" (**) Microtouch minimum y position: 0 (**) Microtouch ThruGlass frequency is: 0 (**) Microtouch device will work in Landscape mode (II) XINPUT: Adding extended input device "FINGER" (type: MicroTouch Finger) (**) Option "Device" "/dev/ttyS1" (**) Option "BaudRate" "2400" (**) Option "StopBits" "1" (**) Option "DataBits" "8" (**) Option "Parity" "None" (**) Option "Vmin" "10" (**) Option "Vtime" "1" (**) Option "FlowControl" "None" (--) MicroTouch touchscreen is a , connected through a serial port. (--) MicroTouch controller firmware revision is 10.11. (--) MicroTouch status of errors: z. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: I18n text input
Russell Shaw wrote: > For functions XkbLookupKeySym(), XLookupString(), XKeycodeToKeysym(), > XKeysymToString etc, how can i tell if the keysym is a graphic printable > character like "a", or a control character such as "Left" (XK_Left) ? > > I need to tell automatically if it's a normal unicode character that can be > printed in an entry box for any written language. For languages other than English, keyboard input isn't as simple as one keypress => one character. Many Western languages use "dead" accents (i.e. pressing an accent key causes the next character to be accented) or compose processing (e.g. Compose,o,/ => ø), and East-Asian languages typically require far more complex input methods. > Do these functions return UTF-8 unicode? XLookupString() uses ISO-8859-1. XmbLookupString() and XwcLookupString() return strings in a locale-specific encoding. If X_HAVE_UTF8_STRING is defined, Xutf8LookupString() returns a UTF-8 string. All three functions require an input context (see XOpenIM() and XCreateIC() for a starting point, but you probably aren't going to work it out from manual pages alone). Unless you're planning on spending the next few months learning how text entry works for languages other than English, I'd recommend using a GUI toolkit rather than trying to do it using bare Xlib. Or at least steal the code from such a toolkit. -- Glynn Clements ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Intel, xrandr and performance.
On Monday 18 January 2010, Paul Menzel wrote: > I have no clue. But does KDE 4 use more desktop effects? Reading your > message I would suggest that the KDE upgrade is at fault here. Or did > you also upgrade the Intel graphics driver? > > Install a different DE or try with KDE 3 again to test the video and > OpenGL stuff. > > Depending of your findings you should either contact the KDE guys or the > Intel [1] guys afterward and leave the corresponding URL in a reply to > this thread. > KDE 4 has a lot of desktop effects and defaults to using a OpenGL backend for the effects. For Intel chipsets I would personally recommend using the XRender backend. I use this at work and have been pleasantly surprised with how well the Intel driver and chipset handles it. You can change backend under System Settings -> Desktop -> Desktop Effects -> Advanced. You can also disable them for a KDE 3.5 like experience. `Allan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
I18n text input
Hi, For functions XkbLookupKeySym(), XLookupString(), XKeycodeToKeysym(), XKeysymToString etc, how can i tell if the keysym is a graphic printable character like "a", or a control character such as "Left" (XK_Left) ? I need to tell automatically if it's a normal unicode character that can be printed in an entry box for any written language. Do these functions return UTF-8 unicode? ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Intel, xrandr and performance.
Am Sonntag, den 10.01.2010, 20:03 +0100 schrieb Łukasz Maśko: > My laptop has an Intel 945GM graphics chip. Right now I'm using Intel driver > 2.9.1. It works pretty well, but... > > If I turn on my secondary display with xrandr (it is an LCD screen connected > via DVI, I'm setting it as a cloned display), graphics performs much slower. > It concerns video and OpenGL (desktop effects inder KDE4). About a month > ago, before I switched to KDE4, under KDE3 everything was working OK using > the same hardware configuration. > > Is it just a general case, or I have something not correctly configured? I have no clue. But does KDE 4 use more desktop effects? Reading your message I would suggest that the KDE upgrade is at fault here. Or did you also upgrade the Intel graphics driver? Install a different DE or try with KDE 3 again to test the video and OpenGL stuff. Depending of your findings you should either contact the KDE guys or the Intel [1] guys afterward and leave the corresponding URL in a reply to this thread. Thanks, Paul [1] http://intellinuxgraphics.org/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
