[Dri-devel] Free Report on Gasoline

2003-03-06 Thread abelica
Title: Untitled Document <%rand%> <%rand%>

[Dri-devel] Initializing a Radeon

2003-03-06 Thread Jon Smirl
Does anyone have the code necessary to initialize a Radeon? I mean the actual code, not the call C000:3 in real mode method. I tried vbios.vm86 but it's bios emulation is not complete enough to run the VBIOS reset code. Having the system BIOS not initialize secondary video adapters is a real pain.

[Dri-devel] In 60 seconds we'll start shopping for you vp

2003-03-06 Thread Leta Browning
Byld-devel Did you know that, Interest Rates are at their lowest point in 40 years! We help you find the best rate for your situation by matching your needs with hundreds of lenders! Home Improvement, Refinance, Second Mortgage, Home Equity Loans, and much, much more! You're eligible even with l

Re: [Dri-devel] Savage Update

2003-03-06 Thread Andreas Karrenbauer
José Fonseca wrote: After that we need to define the macros for MMIO in DRM and write some utility functions for stuff like "wait for card is idle". Both these things can be based on what is done on the existing DDX driver. Hi Jose, don't we allready have this macros for MMIO? At the end of sa

Re: [Dri-devel] C++ Framework Concern

2003-03-06 Thread Morten Hustveit
On Thursday 06 March 2003 18:23, Benjamin Herrenschmidt wrote: > I tend to understand why Apple dumped the constructor approach as much > as possible and added a separate init() method to all their classes Isn't that a bit radical? Why not go with the Qt approach, and add a "bool isOpen()" to cl

Re: [Dri-devel] Final new code in texmem-0-0-1 branch

2003-03-06 Thread Ian Romanick
Andreas Stenglein wrote: will a radeon.o kernelmodule from dri-trunk/2.4.21-pre--ac_kernel/drm-filp-0-1-branch work with the texmem-0-0-1 branch or do I have to use the one from texmem-0-0-1 branch? It should. If it doesn't, then it's a bug and I'd like to hear about it. :) ---

Re: [Dri-devel] Rage128 and DRI lock

2003-03-06 Thread Willy Gardiol
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have done some debugging, so i try to tell you what i discovered, hoping some of you can help me. I have noticed that after some delay the hdd led was flashing, so i waited before rebooting. Doing so, after the hard reboot, i can find some log writ

[Dri-devel] Fwd: FDA Medications

2003-03-06 Thread Zane Russo
This is a multi-part message in MIME format. --C4F_6ECF_CA7D.16EA12731C Content-Type: text/html Content-Transfer-Encoding: quoted-printable AD 3 IT'S NEVER BEEN EASIER TO GET THE DRUGS YOU NEED MEDICATIONS PRESCRIBED ONLINE DELI

Re: [Dri-devel] dri driver features page

2003-03-06 Thread Nicholas Leippe
On Thursday 06 March 2003 08:26 am, Suzy Deffeyes wrote: > Who is the audience for the table? Is it the end user checking to see if a > feature is available and/or has some form of HW acceleration? Or is the > audience the DRI developer, looking to see what pieces need implementing? > That might

Re: [Dri-devel] Re: future of DRI? -> why no one plays with Glide3.

2003-03-06 Thread Allen Akin
On Thu, Mar 06, 2003 at 05:06:41PM +, Alan Cox wrote: | Maybe it will be easier now MS have resigned, although that puts them in a | nice position to avoid declaring patent interests and destroy OpenGL by | submarine patenting games Microsoft caught a lot of flak over their intellectual-proper

Re: [Dri-devel] C++ Framework Concern

2003-03-06 Thread Benjamin Herrenschmidt
On Thu, 2003-03-06 at 16:41, Linus Torvalds wrote: > On Thu, 6 Mar 2003, Ian Molton wrote: > > > > foo=malloc(sizeof(thing)) > > if(!foo) > >... > > Well, the advantage of "new" is that it will run all the constructors etc > automatically, so it's potentially a simpler allocation than C. >

Re: [Dri-devel] C++ Framework Concern

2003-03-06 Thread José Fonseca
On Thu, Mar 06, 2003 at 03:25:41PM +, José Fonseca wrote: > David, I don't know exactly if that was your point, but of all ways > presented here to avoid catching exceptions with the 'new' operator, > using 'set_new_hander' seems the best. It doesn't requires any include > for every source file

Re: [Dri-devel] Re: future of DRI? -> why no one plays with Glide3.

2003-03-06 Thread Alan Cox
On Thu, 2003-03-06 at 15:49, Suzy Deffeyes wrote: > I sure hope the new rules from the Bylaws Working Group make life easier for > someone. ;-). Maybe it will be easier now MS have resigned, although that puts them in a nice position to avoid declaring patent interests and destroy OpenGL by submar

Re: [Dri-devel] Re: future of DRI? -> why no one plays with Glide3.

2003-03-06 Thread Suzy Deffeyes
> | This is encouraging to hear. Have you heard any rumblings about where > | the common code base would come from? > > I was thinking more about the intellectual-property issues than the > shared-code issues. There has been some encouraging efforts by ARB members to share source recently. nVid

Re: [Dri-devel] C++ Framework Concern

2003-03-06 Thread Linus Torvalds
On Thu, 6 Mar 2003, Ian Molton wrote: > > foo=malloc(sizeof(thing)) > if(!foo) >... Well, the advantage of "new" is that it will run all the constructors etc automatically, so it's potentially a simpler allocation than C. If your point is that it's certainly no more complex than the C sequ

Re: [Dri-devel] dri driver features page

2003-03-06 Thread Suzy Deffeyes
> I was thinking it would be nice to color code it even more and add a legend > to distinguish at least the following states: > >++ > given a | the chip has hw support | > feature: +--+-+ >| Y | N

Re: [Dri-devel] C++ Framework Concern

2003-03-06 Thread José Fonseca
On Thu, Mar 06, 2003 at 06:25:32AM -0600, David D. Hagood wrote: > Linus Torvalds wrote: > > >Also note that if you don't allow exceptions (which I would _strongly_ > >encourage), you can't really use "new" - unless you think it's ok to > >SIGSEGV under low-mem circumstances. Which it might be,

[Dri-devel] Fwd: PRANK-A-MATE

2003-03-06 Thread George
Title: Jokeline Gold - The ultimate prank call! The Ultimate Prank Call  Instructions 1 Call 09067 380 080 2 Choose the prank (Eg. Tax inspector) 3 Enter your victims telephone number4 Listen in and hear your victims reaction!    Full Explanation:Jokeline Gold allows you to play lots of different

Re: [Dri-devel] C++ Framework Concern

2003-03-06 Thread Ian Molton
On Thu, 06 Mar 2003 06:25:32 -0600 "David D. Hagood" <[EMAIL PROTECTED]> wrote: > > I don't find it very onerous in my coding to say > foo = new thing; > if (!foo) > ... hmm. foo=malloc(sizeof(thing)) if(!foo) ... :-) --- This SF.net

Re: [Dri-devel] C++ Framework Concern

2003-03-06 Thread David D. Hagood
Linus Torvalds wrote: Also note that if you don't allow exceptions (which I would _strongly_ encourage), you can't really use "new" - unless you think it's ok to SIGSEGV under low-mem circumstances. Which it might be, of course, in some situations. I do embedded C++ using GCC for a living - op

[Dri-devel] Rage128 and DRI lock

2003-03-06 Thread Willy Gardiol
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, i have compiled&installed XFree86 4.3.0 (gcc 3.2.1, kernel 2.4.20) It works quite well with DRI disabled, it works well with DRI enabled using old kernel modules (eg: an old dri snapshot or the gatos for x 4.2.0 ones) but it lock if i use the ke