On Thursday 05 June 2008 12:47:07 am Dave Airlie wrote:
> > Gallium might ultimately wind up in its own repository as a stand-alone
> > project. Afterall, Gallium drivers could be used by APIs other than
> > OpenGL.
>
> The question is mainly from a distro point of view what do we need to ship
> a
http://bugs.freedesktop.org/show_bug.cgi?id=16194
WuNian <[EMAIL PROTECTED]> changed:
What|Removed |Added
Summary|[mesa_7_0_branch] Fog not |[mesa_7_0_branch i915] Fog
>
> Gallium might ultimately wind up in its own repository as a stand-alone
> project. Afterall, Gallium drivers could be used by APIs other than OpenGL.
The question is mainly from a distro point of view what do we need to ship
a gallium driver. The current method would mean we need a Mesa t
Dave Airlie wrote:
> Stephane wrote:
>> Hi Brian,
>>
>> It seems like people are mostly concerned about gallium stability
>> right now. How stable wioll the interfaces be in the future ? Maybe if
>> you could tell us, that'd help others jump in.
The gallium interfaces won't change radically, but
>
> Hi Brian,
>
> It seems like people are mostly concerned about gallium stability
> right now. How stable wioll the interfaces be in the future ? Maybe if
> you could tell us, that'd help others jump in.
Even when it might make it to master, is it planned to land in master..
I would assume Me
>
> If the new driver won't be an incremental change to the existing radeon
> drivers, I'd recommend basing it on Gallium.
>
Hi Brian,
It seems like people are mostly concerned about gallium stability
right now. How stable wioll the interfaces be in the future ? Maybe if
you could tell us, that'd
On Wed, 04 Jun 2008 14:57:00 -0600
Brian Paul <[EMAIL PROTECTED]> wrote:
> Corbin Simpson wrote:
> > Matthias Hopf wrote:
> >> I'm in the process of skimming through the 3D programming documentation
> >> of the r6xx chips. AMD announced on XDC 2008 to make it public, so it
> >> will show up pretty
On Wed, 4 Jun 2008 20:59:39 +0200
Matthias Hopf <[EMAIL PROTECTED]> wrote:
> I'm in the process of skimming through the 3D programming documentation
> of the r6xx chips. AMD announced on XDC 2008 to make it public, so it
> will show up pretty soon. It's one massive beast, more than 650 pages...
>
>>Brian Paul wrote :
>>If the new driver won't be an incremental change to the existing
radeon
drivers, I'd recommend basing it on Gallium.
The driver will be an incremental change. The 6xx family is conceptually
different inside and there is a learning curve, but the basic
programming model is l
Corbin Simpson wrote:
> Matthias Hopf wrote:
>> I'm in the process of skimming through the 3D programming documentation
>> of the r6xx chips. AMD announced on XDC 2008 to make it public, so it
>> will show up pretty soon. It's one massive beast, more than 650 pages...
>>
>> Obviously, the first ste
On Wed, Jun 04, 2008 at 12:30:20PM -0700, Corbin Simpson wrote:
>
> On the DRM side, Alex has added the r6xx microcode to the DRM, and it
> doesn't seem like it should be too much work to get it going, but again
> I have no idea what I'm talking about.
Uploading microcode is a pretty trivial job
Matthias Hopf wrote:
> I'm in the process of skimming through the 3D programming documentation
> of the r6xx chips. AMD announced on XDC 2008 to make it public, so it
> will show up pretty soon. It's one massive beast, more than 650 pages...
>
> Obviously, the first step to get 3D working on r6xx
I'm in the process of skimming through the 3D programming documentation
of the r6xx chips. AMD announced on XDC 2008 to make it public, so it
will show up pretty soon. It's one massive beast, more than 650 pages...
Obviously, the first step to get 3D working on r6xx is to update the
radeon DRM to
http://bugs.freedesktop.org/show_bug.cgi?id=16227
Johannes Engel <[EMAIL PROTECTED]> changed:
What|Removed |Added
Status|NEW |RESOLVED
Res
http://bugs.freedesktop.org/show_bug.cgi?id=16227
--- Comment #3 from [EMAIL PROTECTED] 2008-06-04 11:07:47 PST ---
Works for me, did the same just today. Did you recompile intel DDX driver, too?
It should say "checking for DRI_MM... yes" while configuring.
--
Configure bugmail: http://bug
http://bugs.freedesktop.org/show_bug.cgi?id=16227
--- Comment #2 from Johannes Engel <[EMAIL PROTECTED]> 2008-06-04 05:58:55 PST
---
I guess you mean --enable-ttm-api which I used. Do I need a special drm branch,
too?
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=ema
http://bugs.freedesktop.org/show_bug.cgi?id=16227
--- Comment #1 from Dave Airlie <[EMAIL PROTECTED]> 2008-06-04 04:43:04 PST ---
Mesa doesn't enable TTM by default now...
you need to pass --enable-ttm to the configure script.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cg
http://bugs.freedesktop.org/show_bug.cgi?id=16227
Summary: TTM fails to initialize
Product: Mesa
Version: CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Compo
http://bugs.freedesktop.org/show_bug.cgi?id=16221
haihao <[EMAIL PROTECTED]> changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
19 matches
Mail list logo
