Ben Gamari wrote:
> What trees are you pulling from. Pulling from drm/modesetting-gem and
> mesa/drm-gem I'm getting some pretty obvious build errors (e.g. struct
> drm_gem_open never defined).
That's exactly what I am doing. Upto now I did not experience any of
these errors.
Cheers, Johannes
--
What trees are you pulling from. Pulling from drm/modesetting-gem and
mesa/drm-gem I'm getting some pretty obvious build errors (e.g. struct
drm_gem_open never defined). Thanks,
- Ben
On Fri, 2008-07-11 at 18:18 +0100, Johannes Engel wrote:
> Ben Gamari wrote:
> > On the note of GEM, would it be
Ben Gamari wrote:
> On the note of GEM, would it be worth pulling down the GEM trees to play
> around with and submit bugs against? Is the code in a state at all
> resembling stable (can you run a moderately standard X session for more
> than 10 seconds)?
As far as I can tell this is working nearly
On the note of GEM, would it be worth pulling down the GEM trees to play
around with and submit bugs against? Is the code in a state at all
resembling stable (can you run a moderately standard X session for more
than 10 seconds)? I'd be glad to start reporting if so. Thanks,
- Ben
On Wed, 2008-0
On Wed, 2008-07-09 at 01:52 +0300, Daniel Stone wrote:
>
> I'm sure the developers working on modesetting, the developers working
> on GEM, and the developers working on DRI2 (three independent sets of
> people) would more than appreciate patches, or even specific bug reports
> they can fix.
http
On Wed, 2008-07-09 at 00:31 +0300, Maxim Levitsky wrote:
> And lastly, just for a thought, maybe it is better to do one thing at
> time, for example stabilize kernel modesetting, put it in kernel, then
> release gem driver and stabilize it, and then add dri2 to it?
Yes, but everything depends o
Hi,
On Wed, Jul 09, 2008 at 12:31:22AM +0300, Maxim Levitsky wrote:
> Last time I checked modesetting,
This works.
> intel-batchbuffer,
This works.
> dri2,
This works.
> And lastly, just for a thought, maybe it is better to do one thing at
> time, for example stabilize kernel modesetting, p
>
> You may consider this offtopic, but I wondering
> about status of graphical development.
Yes.
> And lastly, just for a thought, maybe it is better to do one thing at
> time, for example stabilize kernel modesetting, put it in kernel, then
> release gem driver and stabilize it, and then ad
On 03/15/2006 04:01:30 AM, Mike Mestnik wrote:
--- Pawel Salek <[EMAIL PROTECTED]> wrote:
> [snip]
Was working fine for me, until trying to use a newer snapshot. I
still need to patch drm_pciids.txt and copy over the /scripts dir
before ./install.sh
1. you do not need to copy over /scripts
--- Pawel Salek <[EMAIL PROTECTED]> wrote:
> Hi,
>
> (Q1) Can anybody summarize shortly what's the status of X600 (PCIID:
> 5B62, PCIE RV370 type card) support? I see its PCIID is still absent
> in
> shared-core/drm_pciids.txt in spite of few success reports:
>
> http://sourceforge.net/mai
On 03/01/2006 10:49:26 PM, Benjamin Herrenschmidt wrote:
There are more fixes comming into the DDX everyday or so too :) So if
it doesn't work, you may want to lurk at the CVS commit list and
retry regulary.
SUCCESS!
20060306 snapshot work just fine *after* modifying drm_pciids.h file.
Equi
> For Q1, the status is that it should work, but apparently it locks up
> for some unknown reason for some people. There was a significant fix for
> potential lockup problems in the radeon ddx driver in xorg modular cvs,
> which may or not help you. You should try the snapshots, you can try
>
Pawel Salek wrote:
Hi,
(Q1) Can anybody summarize shortly what's the status of X600 (PCIID:
5B62, PCIE RV370 type card) support? I see its PCIID is still absent in
shared-core/drm_pciids.txt in spite of few success reports:
http://sourceforge.net/mailarchive/message.php?msg_id=14645441 (BSD)
On Fri, 2006-01-27 at 08:47 +0100, Helge Hafting wrote:
> Kristoffer wrote:
>
> > I'm thinking of trying the radeon driver again, but i'm wondering
> > wether or not it will ever catch up with the fglrx driver on speed?
>
> You worry about speed, I wonder if it ever will catch up with software
Kristoffer wrote:
I'm thinking of trying the radeon driver again, but i'm wondering
wether or not it will ever catch up with the fglrx driver on speed?
You worry about speed, I wonder if it ever will catch up with software
rendering on stability. Graphichs acceleration, (and the occational
On Wed, 25 Jan 2006 17:28:17 -0500
Adam K Kirchhoff <[EMAIL PROTECTED]> wrote:
> On Wednesday 25 January 2006 19:01, Aapo Tahkola wrote:
> > On Wed, 25 Jan 2006 20:29:05 +0100
> >
> > khaqq <[EMAIL PROTECTED]> wrote:
> > > On Wed, 25 Jan 2006 11:51:17 +0100
> > >
> > > Kristoffer <[EMAIL PROTECTED
On Wednesday 25 January 2006 19:01, Aapo Tahkola wrote:
> On Wed, 25 Jan 2006 20:29:05 +0100
>
> khaqq <[EMAIL PROTECTED]> wrote:
> > On Wed, 25 Jan 2006 11:51:17 +0100
> >
> > Kristoffer <[EMAIL PROTECTED]> wrote:
> > > I'm thinking of trying the radeon driver again, but i'm wondering
> > > wether
On Wed, 25 Jan 2006 20:29:05 +0100
khaqq <[EMAIL PROTECTED]> wrote:
> On Wed, 25 Jan 2006 11:51:17 +0100
> Kristoffer <[EMAIL PROTECTED]> wrote:
>
> > I'm thinking of trying the radeon driver again, but i'm wondering wether
> > or not it will ever catch up with the fglrx driver on speed? what's
On Wed, 25 Jan 2006 11:51:17 +0100
Kristoffer <[EMAIL PROTECTED]> wrote:
> I'm thinking of trying the radeon driver again, but i'm wondering wether
> or not it will ever catch up with the fglrx driver on speed? what's the
> status of this, or goal? and what's the status on 9800 pro dual monito
I played with the latest CVS version some last week and managed to get X
to at least start with DRI enabled on the radeon driver. It doesn't
start any applications, and if I leave it alone long enough it goes to a
black screen and soft-locks; killing X hard-locks. Attached is the log,
or at l
Alex Deucher wrote:
On 12/24/05, Dave Jones <[EMAIL PROTECTED]> wrote:
On Fri, Dec 23, 2005 at 11:20:34PM +, Dave Airlie wrote:
>
> > Anyhow, I was wanting to volunteer my services and my Radeon Xpress 200M
for development work on this project. I have some kernel hacking/driver developmen
On 12/24/05, Dave Jones <[EMAIL PROTECTED]> wrote:
> On Fri, Dec 23, 2005 at 11:20:34PM +, Dave Airlie wrote:
> >
> > > Anyhow, I was wanting to volunteer my services and my Radeon Xpress 200M
> for development work on this project. I have some kernel hacking/driver
> development experienc
On Fri, Dec 23, 2005 at 11:20:34PM +, Dave Airlie wrote:
>
> > Anyhow, I was wanting to volunteer my services and my Radeon Xpress 200M
> > for development work on this project. I have some kernel hacking/driver
> > development experience, but that was on a device with open specificatio
> Anyhow, I was wanting to volunteer my services and my Radeon Xpress 200M for
> development work on this project. I have some kernel hacking/driver
> development experience, but that was on a device with open specifications, so
> I wanted to ask the following questions:
> 1) What do we curren
> I'm following DRI devel the mailing lists and have not seen anything on
> the Mach64 driver lately, especially on the security issues. Any
> progress? Is Mach64 in Xorg-6.8.1? I'm running Debian with XFree86-4.3.0
> and self compiled xlibmesa-dri xserver-xfree86 packages. Unless the
> switch to
On Fre, 2004-10-29 at 12:47 -0700, Ian Romanick wrote:
> The problem, which exists with most (all?) DRM drivers, is that data
> types are used in the kernel/user interface that have different sizes on
> LP32 and LP64. If your kernel is 64-bit, you will have problems with
> 32-bit applications.
Thomas Zehetbauer wrote:
Hi again,
I have now changed Kconfig and successfully compiled, loaded and used
DRI with a Matrox Millenium G550 on a dual Opteron system. I guess this
is a pretty good test and I wonder if the problem has already been fixed
or if it was limited to specific hard- or softwar
[responding from my personal account to avoid the subscriber-only filter]
On Tue, Mar 09, 2004 at 10:40:28PM +, Keith Whitwell wrote:
> Andy Isaacson wrote:
> > [perhaps DRI / fd.o should consider BitKeeper]
>
> For DRI at least, it's been discussed & rejected.
My apologies for bringing up a
On Tue, 2004-03-09 at 23:40, Keith Whitwell wrote:
> Andy Isaacson wrote:
> >
> > I feel a little bit like a shill here, but I figure I should throw out
> > my two cents. First, a disclaimer: I work for BitMover but I do not set
> > company policy; if you need to get The Official Word on things
On Mon, Mar 08, 2004 at 12:29:05PM -0800, Keith Packard wrote:
> Stablizing the tree and getting something shipping that people can
> distribute is the first priority. I'm sure lots of people would like to
> see Mesa/DRI development more closely tied to X driver development so that
> there wasn
Andy Isaacson wrote:
On Mon, Mar 08, 2004 at 12:29:05PM -0800, Keith Packard wrote:
Stablizing the tree and getting something shipping that people can
distribute is the first priority. I'm sure lots of people would like to
see Mesa/DRI development more closely tied to X driver development so th
Around 19 o'clock on Mar 8, Keith Whitwell wrote:
> I don't have any in-principle objections to this, though I'd like to get
> more of a feel for the "new X.org" before committing to anything.
That seems sensible. I don't think there's any particular urgency here,
nothing related to DRI will li
Mike A. Harris wrote:
On Mon, 1 Mar 2004, Alan Cox wrote:
On Llu, 2004-03-01 at 16:28, Michel DÃnzer wrote:
For my part, I'd certainly prefer staying clear of the silly new
license. In the long run, I'd vote for moving the DRI X server code to a
freedesktop.org X server tree and the libGL code t
On Mon, 1 Mar 2004, Alan Cox wrote:
>On Llu, 2004-03-01 at 16:28, Michel DÃnzer wrote:
>> For my part, I'd certainly prefer staying clear of the silly new
>> license. In the long run, I'd vote for moving the DRI X server code to a
>> freedesktop.org X server tree and the libGL code to Mesa or its
On Sat, 2002-06-08 at 06:44, John Karcz wrote:
> I've got a Tiger S2460 and a Radeon, and suffer from this bug.
> I'd love to help nail it.
>
> I built XFree86 last weekend from CVS head, and got it running.
> But, direct rendering isn't working. (I'm using the same
> XF86Config-4 as for my XFr
I've got a Tiger S2460 and a Radeon, and suffer from this bug.
I'd love to help nail it.
I built XFree86 last weekend from CVS head, and got it running.
But, direct rendering isn't working. (I'm using the same
XF86Config-4 as for my XFree86 4.2 server, for which direct
rendering is working fine.
36 matches
Mail list logo
