Re: DRI build fails with new glxext.h

2004-07-28 Thread Brian Paul
Felix Kühling wrote: Hi, the new glxext.h declares GLX_OML_sync_control stuff only if the C standard is set to c99. Mesa's linux-dri-x86 target sets -std=c99. DRI CVS does not, so the build fails. Replacing -ansi with -std=c99 in host.def fixes it for me. I suspect X.Org is affected too. I'm about

Re: [Linux-fbdev-devel] OLS and console rearchitecture

2004-07-28 Thread Jon Smirl
I asked this at OLS and no one knew of an open source x86 Open Firmware emulator. 99% of the time it is people wanting to use cheap x86 cards in Open Firmware systems to avoid having to pay $$ for those added valued ROMs. --- Ian Romanick <[EMAIL PROTECTED]> wrote: > Alan Cox wrote: > > > On Me

Re: [Linux-fbdev-devel] OLS and console rearchitecture

2004-07-28 Thread Ian Romanick
Alan Cox wrote: On Mer, 2004-07-28 at 22:31, Kronos wrote: Btw, how do we POST non-x86 (eg. ppc) video boards? I don't think that there's x86 code in their ROM... Same way X does - x86emu I think he meant using OpenFirmware video cards on x86 boxes. Does x86emu take care of that? In any case, th

DRI build fails with new glxext.h

2004-07-28 Thread Felix Kühling
Hi, the new glxext.h declares GLX_OML_sync_control stuff only if the C standard is set to c99. Mesa's linux-dri-x86 target sets -std=c99. DRI CVS does not, so the build fails. Replacing -ansi with -std=c99 in host.def fixes it for me. I suspect X.Org is affected too. The second problem is in the

Update on video memory manager work

2004-07-28 Thread Ian Romanick
Since there was so much interest at DDC, I wanted to give a brief update of my memory manager work. I have about 95% of the baseline functionality (i.e., what's required to just replace the existing texture manager) done. When I was at DDC, I was still hitting a few assertion failures, but, a

Re: [Linux-fbdev-devel] OLS and console rearchitecture

2004-07-28 Thread Jon Smirl
--- Alan Cox <[EMAIL PROTECTED]> wrote: > > sysfs? I sent a patch a while ago but didn't get much feedback. > > How do you atomically tie sysfs objects to fbdev and X permissions > models ? I think the plan here is for ROM export to be implemented by the PCI driver not the video ones since other

Re: [Linux-fbdev-devel] OLS and console rearchitecture

2004-07-28 Thread Alan Cox
On Mer, 2004-07-28 at 22:31, Kronos wrote: > There was a thread on acpi-devel about POSTing VGA ROM after resume: > > http://marc.theaimsgroup.com/?l=acpi4linux&m=109023076427394&w=2 > > The code does a real mode switch in kernel and execute the ROM. Ok, doing > that in userspace is more elegant,

Re: [Linux-fbdev-devel] OLS and console rearchitecture

2004-07-28 Thread Kronos
Hi Jon Il Wed, Jul 28, 2004 at 11:53:46AM -0700, Jon Smirl ha scritto: > 3) Secondary card reset - Handled by an initial hotplug event. We need > a volunteer to write clean vm86 and emu86 apps for running the ROM > initialization. There was a thread on acpi-devel about POSTing VGA ROM after resu

Re: OLS and console rearchitecture

2004-07-28 Thread Alan Cox
On Mer, 2004-07-28 at 19:53, Jon Smirl wrote: > First a basic definition. There are two consoles, the kernel one > (printk, kdbg, OOPs, etc) and user one (normal console logins). There > is no requirement that these consoles be handled with the same code > even though they are today. Not sure that

OLS and console rearchitecture

2004-07-28 Thread Jon Smirl
After talking to many people at OLS this seems to be the consensus for rearchitecting fbdev/DRM. It has been proposed that this design be a five year goal but there is still disagreement about the exact path to get there. This is a first pass for the fbdev/DRM people. I will incorporate comments a

Re: Hang w/ S3TC enabled DRI drivers

2004-07-28 Thread Roberto Sanchez
Roland Scheidegger wrote: Roberto Sanchez wrote: I have followed the instructions provided by Roland Scheidegger: http://homepage.hispeed.ch/rscheidegger/dri_experimental/s3tc_index.html I was able to get DRI, Mesa, and DRM to compile and run. I then applied Roland's patches and recompiled, and

Re: Hang w/ S3TC enabled DRI drivers

2004-07-28 Thread Roland Scheidegger
Roberto Sanchez wrote: I have followed the instructions provided by Roland Scheidegger: http://homepage.hispeed.ch/rscheidegger/dri_experimental/s3tc_index.html I was able to get DRI, Mesa, and DRM to compile and run. I then applied Roland's patches and recompiled, and again everything worked. T

Re: G400 on AMD64 does not work

2004-07-28 Thread Alan Cox
On Mer, 2004-07-28 at 07:57, Ian Romanick wrote: > Kenan Esau wrote: > > I am sorry if I am asking FAQs. But I just want to know if someone is > > working on this and if I can help debugging this problem. > > > > If you think there is no problem this would be also interesting for me. > > I don't

[Bug 930] glxgears segfault only when resolution > 1024x768

2004-07-28 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://freedesktop.org/bugzilla/show_bug.cgi?id=930 --- Additional Comments From [EMAIL PROTECTED] 2004-07-28 02:32 --- Occurs with lat

[Bug 930] glxgears segfault only when resolution > 1024x768

2004-07-28 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://freedesktop.org/bugzilla/show_bug.cgi?id=930 --- Additional Comments From [EMAIL PROTECTED] 2004-07-28 02:20 --- Created an atta

Re: G400 on AMD64 does not work

2004-07-28 Thread Ian Romanick
Kenan Esau wrote: I am sorry if I am asking FAQs. But I just want to know if someone is working on this and if I can help debugging this problem. If you think there is no problem this would be also interesting for me. I don't know of any DRI developers that have access to AMD64 hardware. -