Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=716
--- Additional Comments From [EMAIL PROTECTED] 2003-20-09 23:45 ---
I would investigate th
Brian,
I'm interested seeing the savage driver working on XFfree86 4.3.0 with mesa
5.0.x, you are using a savage driver that is supposed to work on xfree86
4.2.0 and i'm working on the same driver but trying to make it works on
xfree86 4.3.0
bye.
At 08:28 PM 20/9/2003, Brian Penix wrote:
I hav
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=717
--- Additional Comments From [EMAIL PROTECTED] 2003-20-09 22:34 ---
> That's the symptom,
On Gwe, 2003-09-12 at 19:53, Maximo wrote:
> As i know CLE266 works only on Xfree86 4.2.0, what i'm doing is make
> it work on xfree86 4.3.0
I promised folks I'd get around to putting up the XFree 4.3.0 port of
the DRI stuff (or what works so far). Don't get too excited as it works
if 1. 2D accel
you might compare it to Tim's old 2D driver (shipped with 4.3.0) and
see what's changed...assuming his driver works for you in 2D.
Alex
--- Rafael Maximo <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I decided to focus on 2D problem first but i don't know how
> I can
> debug the 2D driver an
I have been following with interest your trials and tribulations with the
Savage 3D driver. I too am working on it and may have some info for you. I
have all the driver functions working here but only in XFree86 4.2.0. (mesa
3.4.2) I am currently looking for info on the changes to T&L and SWRAST
I've uploaded updated Mesa source documentation to
http://dri.sourceforge.net/doc/mesa/ and...
On Tue, Sep 16, 2003 at 03:31:54PM +0100, José Fonseca wrote:
> On certain pages where code symbol names are used, such as
> http://dri.sourceforge.net/cgi-bin/moin.cgi/DriMemoryManagerDesign , the
> hyp
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=717
--- Additional Comments From [EMAIL PROTECTED] 2003-20-09 15:23 ---
> On the contrary, whe
I already sent this message, but i think something happened
because i didn't receivea copy from the list, that's why i'm sending again.
-begin-
Hi,
I decided to focus on 2D problem first but i don't know how I can
debug the 2D driver and found where is the problem. I wo
On Sat, Sep 20, 2003 at 08:58:23AM -0700, Alex Deucher wrote:
> If you are getting version mismatch errors with the sanpshots, you need
> a newer version of the xfree86 server. DRI just merged in the changes
> from the Xfree86 tree and a newer XFree86 binary is needed. you can
> either build it y
On Fri, 19 Sep 2003 12:20:53 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 18, 2003 at 06:52:23PM +0200, Alexander Stohr wrote:
> > i want to propose to integrate a link
> > to the new WIKI pages to the Help & FAQ
> > section of the DRI homepage.
>
> I've added a link to the Wiki n
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=717
--- Additional Comments From [EMAIL PROTECTED] 2003-20-09 12:45 ---
Created an attachment
If you are getting version mismatch errors with the sanpshots, you need
a newer version of the xfree86 server. DRI just merged in the changes
from the Xfree86 tree and a newer XFree86 binary is needed. you can
either build it yourself from CVS, or download the gcc 3.x one I've
provided here:
http
On Sat, 2003-09-20 at 17:27, José Fonseca wrote:
>
> PS: The command to fix that would be (assuming one has sed version 4.0
> or greater):
>
> find . -name Repository | xargs sed -i -e 's:^xc/::'
^^
's:^xc/xc:xc:' would be idempotent.
--
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=716
--- Additional Comments From [EMAIL PROTECTED] 2003-20-09 11:31 ---
It happens everytime (
On Sat, Sep 20, 2003 at 02:41:20PM +0200, Michel Dänzer wrote:
> On Fri, 2003-09-19 at 12:13, José Fonseca wrote:
> >
> > BTW, a pet peeve of mine is the double 'xc/xc' in the main CVS module.
> > If viable, when transitioning leave only one 'xc', and take way the
> > orfan 'xc/t' dir too.
>
> Th
> Now I am reading intel northbridge 440BX spec(look page 88:Memory
> System Address Space) And i have a box with 440BX
> I look /proc/iomem,i find that Framebuffer's size is 16MB(i open vesa
> before kernel using vga=788) And the local Graphics Memory's size is
> 64MB(through PMBASE Reg (24h) ;De
On Fri, 2003-09-19 at 12:13, José Fonseca wrote:
>
> BTW, a pet peeve of mine is the double 'xc/xc' in the main CVS module.
> If viable, when transitioning leave only one 'xc', and take way the
> orfan 'xc/t' dir too.
This could be done by moving the repository files accordingly, but the
CVS/Repo
Hi,
I decided to focus on 2D problem first but i don't know how I can
debug the 2D driver and found where is the problem. I would appreciate any
information or docs about debugging this kind of problem.
I'm using the 2D driver on savage_1-0-0_branch and i didn't change
anything
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=716
[EMAIL PROTECTED] changed:
What|Removed |Added
---
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=717
[EMAIL PROTECTED] changed:
What|Removed |Added
---
21 matches
Mail list logo
