Peter Hutterer wrote:
>> I just wasted quite some time to get master to actually start.
>> Unresolved
>> symbols all over the place, both with intel and with vesa. Vesa had
>> xf86InterpretEDID, intel had three or four different ones
>> (miPolyRectangle
>> was one of them IIRC). Rebuilding with and
On Thu, Dec 11, 2008 at 11:12:38PM +1000, Peter Hutterer wrote:
> I just wasted quite some time to get master to actually start. Unresolved
> symbols all over the place, both with intel and with vesa. Vesa had
> xf86InterpretEDID, intel had three or four different ones (miPolyRectangle
> was one of
> And that is no problem at all, until you want to throw away the glyph that
> was there before and write a new glyph in its place. And then you need to
> know what the original background behind the old glyph was, but the server
> does not have that information, and so it has to be kept in the
> a
From: Beso
Date: 2008/12/12
Subject: Re: Cannot get DRI to work
To: Hendrik Friedel
i have some observations:
1. have you compile the libdrm modules for the kernel you're using?!
2. try using the mtrr registers to map the memory. it's somehow faster
than without it
Option"mtrr" "on"
2008/12/12 Hendrik Friedel :
> Hello Beso,
>
> Thanks for your strong support.
> I'll try to answer your points:
> 1) Sorry, but I don't know when the libdrm modules are compiled. I've not
> compiled a new kernel on this installation, so if the modules are compiled
> with the kernel, then it should
Yet more evidence that we should teach valgrind about gem, xserver
memory maps, et al. Even without filtering out gem events, I was still
able to catch dozens of memory leaks. It would definitely help with some
of the mesa crashers I've been trying to figure out.
- Ben
On Fri, 2008-12-12 at 15:1
On Fri, 2008-12-12 at 14:11 -0500, Dr. Michael J. Chudobiak wrote:
> Should I be able to get my HP lp2475w monitor to work with DisplayPort
> on Fedora 10 using the intel driver on a HP DC7900? Nothing seems to
> work at all... I don't think the DisplayPort is even recognized.
For G45/GM45, the
On Fri, Dec 12, 2008 at 2:57 PM, Hendrik Friedel wrote:
> Hello,
>
> No, it's not. If I load it I get this error:
> fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg,
> GERMANY' taints kernel.
> [fglrx] Maximum main memory to use for locked dma buffers: 927 MBytes.
> [fglr
Hello,
No, it's not. If I load it I get this error:
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg,
GERMANY' taints kernel.
[fglrx] Maximum main memory to use for locked dma buffers: 927 MBytes.
[fglrx] ASYNCIO init succeed!
[fglrx] PAT is enabled successfully!
[fglrx:f
"Richard Schwarting" writes:
> Hey. The patches cured XAA slowness for me and obviate the need for
> the "UseBIOS" "NO" option for both EXA and XAA for me. Hurrah.
>
> I mentioned before that after suspending in Fedora, resuming gives me
> a blank screen. If I do any VT switches, than light st
On Fri, Dec 12, 2008 at 2:11 PM, Hendrik Friedel wrote:
> Hello,
>
> I'm having trouble to get DRI to work:
>
> LIBGL_DEBUG=verbose glxinfo | grep direct
> libGL error: XF86DRIQueryDirectRenderingCapable returned false
> direct rendering: No (If you want to find out why, try setting
> LIBGL_DEBUG=
Hi
Just wanted to raise the awareness of this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=19048
which is the only one keeping me from uploading it to the ubuntu devel
release before alpha2 next week ;)
t
___
xorg mailing list
xorg@li
Dr. Michael J. Chudobiak wrote:
> Should I be able to get my HP lp2475w monitor to work with DisplayPort
> on Fedora 10 using the intel driver on a HP DC7900? Nothing seems to
> work at all... I don't think the DisplayPort is even recognized.
>
> I have xorg-x11-drv-i810-2.5.0-4.fc10.x86_64.
X
Should I be able to get my HP lp2475w monitor to work with DisplayPort
on Fedora 10 using the intel driver on a HP DC7900? Nothing seems to
work at all... I don't think the DisplayPort is even recognized.
I have xorg-x11-drv-i810-2.5.0-4.fc10.x86_64.
Suggestions appreciated...
- Mike
___
Hello,
I'm having trouble to get DRI to work:
LIBGL_DEBUG=verbose glxinfo | grep direct
libGL error: XF86DRIQueryDirectRenderingCapable returned false
direct rendering: No (If you want to find out why, try setting
LIBGL_DEBUG=verbose)
I think the problem is here:
On Fri, Dec 12, 2008 at 5:53 PM, Gene Heskett wrote:
> On Friday 12 December 2008, Matthias Hopf wrote:
>>Announcing the 1.2.4 of the xf86-video-radeonhd driver.
>>
> I still don't have drm, so glxgears is only marginally faster (850 fps vs 800)
> than before on an RV610 (Diamond HD2400-Pro), and
On Friday 12 December 2008, Gene Heskett wrote:
>On Friday 12 December 2008, Matthias Hopf wrote:
>>Announcing the 1.2.4 of the xf86-video-radeonhd driver.
>>
>>RadeonHD is the X.org X11 driver for AMD GPG (ATI) r5xx/r6xx chipsets.
>>The development is driven by Novell at the time of writing, toget
> And that is no problem at all, until you want to throw away the glyph that
> was there before and write a new glyph in its place.
How? How do you 'remove' a glyph that was there before? There's no
'remove this pixmap' operation.
___
xorg mailing list
On Thu, 11 Dec 2008 14:23:51 -, Clemens Eisserer
wrote:
>> From the plain X Server POV, antialiasing is always going to be hard,
>> because to do it you need to know the background color or pixmap, and
>> the
>> Xserver does not keep track of how you had earlier set it, so it is up
>>
Announcing the 1.2.4 of the xf86-video-radeonhd driver.
RadeonHD is the X.org X11 driver for AMD GPG (ATI) r5xx/r6xx chipsets.
The development is driven by Novell at the time of writing, together
with a community of open source developers around this driver.
AMD provides free documentation for the
2008/12/12 Cliff Lawson
> So I used GIT to get a libdrm that did include the linux-source part of the
> tree but when I built it the i915.ko did not build and looking at the
> Makefile it would appear to be because OS_HAS_GEM was not defined. It was a
> search for the solution to that which broug
Hi,
We're trying to get an Ubuntu 8.04.1 system running based on the Intel
Atom based motherboard D945GCLF. This will use the VLC plugin to Firefox
to play mpeg files which, with the player configured to output via X11
and having DRI enabled seems to do a fine job. HOWEVER we also want to
possi
Version 1.2.99.3 improvements over 1.2.99.1:
- Panning support
- Output primary support
Version 1.2.99.1 improvements over 1.2.3:
- Transformation support
- GetScreenResourcesCurrent support
http://xorg.freedesktop.org/releases/individual/lib/libXrandr-1.2.99.3.tar.gz
MD5: a7c375e8f914b86a6ce
Version 1.2.99.3 improvements over 1.2.99.1:
- Panning support
- Output primary support
Version 1.2.99.1 improvements over 1.2.2:
- Transformation support
- GetScreenResourcesCurrent support
http://xorg.freedesktop.org/releases/individual/proto/randrproto-1.2.99.3.tar.gz
MD5: bbf7f8d31aeeef7e
On Thu, Dec 11, 2008 at 12:23:56PM -0800, Eric Anholt wrote:
> On Tue, 2008-11-18 at 09:43 +1100, garrone wrote:
> > Using the intel driver on a GM45 device, with monitors
> > connected to the TMDS1/2 outputs, it was found that
> > the xserver was refusing to accept the option
> > option "Moni
On Thu, Dec 11, 2008 at 08:13:12PM +1000, Dave Airlie wrote:
> On Thu, Dec 11, 2008 at 4:56 PM, garrone wrote:
> >
> > Hi,
> > I am getting freezes in direct rendering. Sometimes glxgears works,
> > but eventually the freeze occurs at program exit, or upon xrandr operation.
> >
> > The freeze occ
26 matches
Mail list logo
