Direct Rendering Infrastructure

On Gwe, 2003-06-27 at 17:07, Maximo wrote:
> Hi,
> 
> I got the Savage-1_0_0-branch from CVS e tried to compile it and i got no 
> error but when I copied the drm modules do its place at /lib/modules/..... 
> e tried to load the module into memory i got this unresolved symbol error:
> 
> /lib/modules/2.4.21/kernel/drivers/char/drm/savage.o: unresolved symbol 
> pte_offset_kernel
> 
> Does anyone have any ideia to fix that? This error didn't happen when i 
> compiled the Savage-0_0_1-branch (The old one). Any help?

I've done some cleanup of the drm modules in the -ac tree, the ones they
included plain wont work

On Gwe, 2003-06-27 at 18:05, Maximo wrote:
> >I've done some cleanup of the drm modules in the -ac tree, the ones they
> >included plain wont work
> 
> 
> When your modifications will be available on Savage-1_0_0-branch?

I've no idea what people want to do about that. My cleaned up stuff wont work with
2.2 or older 2.4 for example

At 01:52 PM 27/6/2003, Alan Cox wrote:
>On Gwe, 2003-06-27 at 17:07, Maximo wrote:
> > Hi,
> >
> > I got the Savage-1_0_0-branch from CVS e tried to compile it and i got no
> > error but when I copied the drm modules do its place at /lib/modules/.....
> > e tried to load the module into memory i got this unresolved symbol error:
> >
> > /lib/modules/2.4.21/kernel/drivers/char/drm/savage.o: unresolved symbol
> > pte_offset_kernel
> >
> > Does anyone have any ideia to fix that? This error didn't happen when i
> > compiled the Savage-0_0_1-branch (The old one). Any help?
>
>I've done some cleanup of the drm modules in the -ac tree, the ones they
>included plain wont work


When your modifications will be available on Savage-1_0_0-branch?

bye

At 02:16 PM 27/6/2003, Alan Cox wrote:
> > When your modifications will be available on Savage-1_0_0-branch?
>
>I've no idea what people want to do about that. My cleaned up stuff wont 
>work with
>2.2 or older 2.4 for example

Could you send me a diff with your changes?

On Fri, Jun 27, 2003 at 02:05:03PM -0300, Maximo wrote:
> At 01:52 PM 27/6/2003, Alan Cox wrote:
> >On Gwe, 2003-06-27 at 17:07, Maximo wrote:
> >> Hi,
> >>
> >> I got the Savage-1_0_0-branch from CVS e tried to compile it and i got no
> >> error but when I copied the drm modules do its place at 
> >/lib/modules/.....
> >> e tried to load the module into memory i got this unresolved symbol 
> >error:
> >>
> >> /lib/modules/2.4.21/kernel/drivers/char/drm/savage.o: unresolved symbol
> >> pte_offset_kernel
> >>
> >> Does anyone have any ideia to fix that? This error didn't happen when i
> >> compiled the Savage-0_0_1-branch (The old one). Any help?
> >
> >I've done some cleanup of the drm modules in the -ac tree, the ones they
> >included plain wont work
> 
> 
> When your modifications will be available on Savage-1_0_0-branch?

The savage-1_0_0-branch wont work until the 3D driver is fixed up for
Mesa 4.x - it's still based on Mesa 3.4.

I think I've fixed up enough of the 2D driver to test this out now, and
the kernel driver works on kernel 2.4.9, but I've not tried on anything
later.

If Alan Cox has some patches for the kernel module, send 'em along and
I'll get them into this branch.

The next step is definately the 3D driver.

Alan.

On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
> The savage-1_0_0-branch wont work until the 3D driver is fixed up for
> Mesa 4.x - it's still based on Mesa 3.4.

Is there any good info on doing this since the CLE266 driver has the
same problem

> I think I've fixed up enough of the 2D driver to test this out now, and
> the kernel driver works on kernel 2.4.9, but I've not tried on anything
> later.

It'll kind of work providing certain things dont happen and your box is
uniprocessor.

> If Alan Cox has some patches for the kernel module, send 'em along and
> I'll get them into this branch.

I'll send some bits along this weekend if I get time

--- Alan Cox <alan@...> wrote:
> On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
> > The savage-1_0_0-branch wont work until the 3D driver is fixed up
> for
> > Mesa 4.x - it's still based on Mesa 3.4.
> 
> Is there any good info on doing this since the CLE266 driver has the
> same problem
> 

I'd like to know what's involved in this too.  The SiS DRI driver needs
to be updated as well.  If it is just a matter of re-arranging some
code, I could probably handle that.  I need to learn how the 3D side
works at some point, this might be a good oppurtunity.

Alex

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

On Fri, Jun 27, 2003 at 06:53:08PM +0100, Alan Cox wrote:
> On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
> > The savage-1_0_0-branch wont work until the 3D driver is fixed up for
> > Mesa 4.x - it's still based on Mesa 3.4.
> 
> Is there any good info on doing this since the CLE266 driver has the
> same problem

Not really. Keith Whitwell is the expert at converting drivers, he's
had to do that a few times. Otherwise it's take it a file at a time.

> > I think I've fixed up enough of the 2D driver to test this out now, and
> > the kernel driver works on kernel 2.4.9, but I've not tried on anything
> > later.
> 
> It'll kind of work providing certain things dont happen and your box is
> uniprocessor.
 
It's my T20 laptop, so unless someone wedged another processor in, I should
be ok. :) Just getting glxgears running would be good though.

> > If Alan Cox has some patches for the kernel module, send 'em along and
> > I'll get them into this branch.
> 
> I'll send some bits along this weekend if I get time

Great!

Alan.

Alex Deucher wrote:
> --- Alan Cox <alan@...> wrote:
> 
>>On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
>>
>>>The savage-1_0_0-branch wont work until the 3D driver is fixed up
>>
>>for
>>
>>>Mesa 4.x - it's still based on Mesa 3.4.
>>
>>Is there any good info on doing this since the CLE266 driver has the
>>same problem
>>
> 
> 
> I'd like to know what's involved in this too.  The SiS DRI driver needs
> to be updated as well.  If it is just a matter of re-arranging some
> code, I could probably handle that.  I need to learn how the 3D side
> works at some point, this might be a good oppurtunity.

The Mesa/docs/RELNOTES-* files describe changes from one version to 
next, including info for upgrading device drivers.  If you scan all 
the RELNOTES from 3.4 to 5.x you'll get the gist of things.

-Brian

Alan Cox wrote:
> On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
> 
>>The savage-1_0_0-branch wont work until the 3D driver is fixed up for
>>Mesa 4.x - it's still based on Mesa 3.4.
> 
> Is there any good info on doing this since the CLE266 driver has the
> same problem

And the SiS driver. :)  Our best bet will be to do all three (even if 
the SiS driver doesn't get any testing) at the same time.  I think the 
people that did the original 3.4-to-4.x conversion have long since 
forgotten what was done.  That was before I even joined the project! :)

and virge too possibly :)  Speaking of which if anyone wants a virge
board for testing/porting, I've got an old GX (and possibly a DX as
well) sitting around.

Alex

--- Ian Romanick <idr@...> wrote:
> Alan Cox wrote:
> > On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
> > 
> >>The savage-1_0_0-branch wont work until the 3D driver is fixed up
> for
> >>Mesa 4.x - it's still based on Mesa 3.4.
> > 
> > Is there any good info on doing this since the CLE266 driver has
> the
> > same problem
> 
> And the SiS driver. :)  Our best bet will be to do all three (even if
> 
> the SiS driver doesn't get any testing) at the same time.  I think
> the 
> people that did the original 3.4-to-4.x conversion have long since 
> forgotten what was done.  That was before I even joined the project!
> :)
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites
> including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@...
> https://lists.sourceforge.net/lists/listinfo/dri-devel


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

Speaking of virge, does anyone have any info on TV Out with virge 
cards?  I would like to work on this, I have a GX card sitting in a box 
somewhere I believe that I would like to use to set up a media center in 
my living room.

-James

Alex Deucher wrote:

>and virge too possibly :)  Speaking of which if anyone wants a virge
>board for testing/porting, I've got an old GX (and possibly a DX as
>well) sitting around.
>
>Alex
>
>--- Ian Romanick <idr@...> wrote:
>  
>
>>Alan Cox wrote:
>>    
>>
>>>On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
>>>
>>>      
>>>
>>>>The savage-1_0_0-branch wont work until the 3D driver is fixed up
>>>>        
>>>>
>>for
>>    
>>
>>>>Mesa 4.x - it's still based on Mesa 3.4.
>>>>        
>>>>
>>>Is there any good info on doing this since the CLE266 driver has
>>>      
>>>
>>the
>>    
>>
>>>same problem
>>>      
>>>
>>And the SiS driver. :)  Our best bet will be to do all three (even if
>>
>>the SiS driver doesn't get any testing) at the same time.  I think
>>the 
>>people that did the original 3.4-to-4.x conversion have long since 
>>forgotten what was done.  That was before I even joined the project!
>>:)
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email sponsored by: Free pre-built ASP.NET sites
>>including
>>Data Reports, E-commerce, Portals, and Forums are available now.
>>Download today and enter to win an XBOX or Visual Studio .NET.
>>
>>    
>>
>http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
>  
>
>>_______________________________________________
>>Dri-devel mailing list
>>Dri-devel@...
>>https://lists.sourceforge.net/lists/listinfo/dri-devel
>>    
>>
>
>
>__________________________________
>Do you Yahoo!?
>SBC Yahoo! DSL - Now only $29.95 per month!
>http://sbc.yahoo.com
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by: Free pre-built ASP.NET sites including
>Data Reports, E-commerce, Portals, and Forums are available now.
>Download today and enter to win an XBOX or Visual Studio .NET.
>http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
>_______________________________________________
>Dri-devel mailing list
>Dri-devel@...
>https://lists.sourceforge.net/lists/listinfo/dri-devel
>
>
>  
>

On Fri, Jun 27, 2003 at 04:58:52PM -0700, Ian Romanick wrote:
> Alan Cox wrote:
> >On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
> >
> >>The savage-1_0_0-branch wont work until the 3D driver is fixed up for
> >>Mesa 4.x - it's still based on Mesa 3.4.
> >
> >Is there any good info on doing this since the CLE266 driver has the
> >same problem
> 
> And the SiS driver. :)  Our best bet will be to do all three (even if 
> the SiS driver doesn't get any testing) at the same time.  I think the 
> people that did the original 3.4-to-4.x conversion have long since 
> forgotten what was done.  That was before I even joined the project! :)

Me and Leif did it for the Mach64 once and I already gave a roadmap to
how proceed more than once in this list. This is one [the most recent I
think] I could find:

  http://marc.theaimsgroup.com/?t=101850699700001&r=1&w=2

The FAQ has been re-organized since and the "Mesa Internals" notes can
be found on:

  http://dri.sourceforge.net/doc/faq/implementation.html#mesa-internals

Another thing which I didn't explain enough is how to base on an
existing driver. For exemplification I'll pretend the SIS is being
updated, and the updates are being based on the R128 driver. 
You basically need to have 4 reference trees in your work dir:

 (a)SIS from recent trunk                (c) R128 from ancient trunk      
     (Mesa 3.4)                               (Mesa 3.4)
          ||                                      |
	  \/                                      v
 (b)sis-0-0-?-branch          <=         (d) R128 from recent trunk

Then one mimics from (a)->(b) the changes one sees in (c)->(d), by
copying'n'pasting either from (a) or from (d) into (b), as appropriate.
Using a visual diff tool (such as xxdiff) helps considerably this task.

Care to notice that it's not necessary to have a deep understanding of
the code - heck, at the time I admitedly had none! It's more like a
visual puzzle. Actually is very similar to a jigsaw puzzle: it helps to
have the full picture but it's not needed, as long as one keeps
connecting the puzzle pieces one by one it's deemed to succeed.

I hope this helps any caring sole for these old drivers to be more
confident about this task.

José Fonseca