[Dri-devel] question re 810 vs 830 drivers
I've noticed the i830 drivers have a unified memory allocation scheme for 2d and 3d, is there any reason this couldnt be used on the i810? Is there any major reasons the i830 driver couldn't be usd on the i810 with the functionality it doesn't need turned off? I'm just wondering the i810/i830 drivers look very close and I persume were once unified and got separated somewhere for a reason.. just wondering was the reason because of something lowlevel that wasn't compatible or the author didn't want to break an old chipset he had no access to? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Love is in the air! wsmut8
Title: lovepond --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Amazing Offers
As Seen on NBC, CBS, CNN and even Oprah! The Health Discovery that Actually Reverses Aging while Burning Fat, without Dieting or Exercise! This Proven Discovery has even been reported on by the New England Journal of Medicine. Forget Aging and Dieting Forever! And it's Guaranteed! Click Here to Learn How you can Receive a Full Month's Supply Absolutely FREE! Would you like to lose weight while you sleep? No dieting! No hunger pains! No Cravings! No strenuous exercise! Change Your Life Forever! 1. Body Fat Loss..82% improvement. 2. Wrinkle Reduction.61% improvement. 3. Energy Level.84% improvement. 4. Muscle Strength88% improvement. 5. Sexual Potency.75% improvement. 6. Emotional Stability.67% improvement. 7. Memory.62% improvement. Get Your FREE 1 Month Supply TODAY! You are receiving this message as a member of the Opt-In America List. To remove your email address please click hereWe honor all remove requests. lqhwn dr gkgsnn j sjqlb
[Dri-devel] Small Doxygen tutorial (Was: DRI/Mesa Doxygen documentation)
On Wed, Mar 26, 2003 at 12:55:13AM +, José Fonseca wrote:
[...]
> I'd also want to take this opportunity to request that everybody who
> writes new code to follow a few simple conventions - this will enable
> automatic documentation extraction by the Doxygen tool as above -, but
> I'll do that in a seperate email tomorrow, together with a brief
> tutorial.
Hmm.. time does fly. Anyway, here is the promised brief Doxygen
tutorial.
Special comments blocks are marked with a double asterisk as /** ... */,
or /**< ... */ if they follow the member. Special tags within the
special comments are marked with a slash '\', of which the most
important is '\brief'. The minimum ammount of documentation for all
non-trivial code is a special comment with just a 'brief' tag:
/** \brief The structure of the universe */
struct Universe {
unsigned long nAtoms; /**< \brief Number of atoms */
struct Atom *atoms; /**< \brief The state of each atom */
} ;
/** \brief Is Earth flat? */
void isEarthFlat(void) {
return getCentury() < 16;
}
Also, all files should start with a block like this:
/**
* \file internet.c
* \brief Implementation of the internet.
*
* \author Al Gore.
*/
This minimum ammount of documentation will mark these
structures/functions/files to be extracted by Doxygen and therefore
appearing in the generated documentation.
If you have more detailed documentation to give, or want to document a
certain parameter of the function return value you can do it like:
/**
* \brief Work simulation.
*
* This function simulates a working day using a highly sofisticated
* algorithm.
*
* \param n number of working hours.
*
* \return one on a productive day, zero otherwise.
*/
int work(int t) {
int i;
if (deadLine != gettimeofday()) {
while(!workDone) {
workVeryHard();
}
return 1;
} else {
checkEMail();
browseInternet();
for(i = 2; i < t - 1; i++) {
checkEMail();
tryToWork();
checkEMail();
usleep(aWhile*1000);
}
checkEMail();
pretendToWork();
return 0;
}
}
With many functions or structure fields is useful to group them together. This
can be done using the '\name' and {@ @} tags:
/** \brief
struct WarAnalysisRec {
/** \name Economic factors */
/[EMAIL PROTECTED]/
double priceOil; /**< \brief Price of oil per gallon */
double weapons; /**< \brief Estimated expenditure with
weapons */
/[EMAIL PROTECTED]/
/** \name Social factors */
/[EMAIL PROTECTED]/
unsigned char costHumanLife; /**< \brief Cost of human life */
/[EMAIL PROTECTED]/
void *privData; /**< \brief Private data pointer to an
opaque structure. */
} ;
Note that this grouping can't be nested.
There are more nice things that can be done, but these are the basic and
that give the most bang per buck. To know more info read the Doxygen
manual: http://www.stack.nl/~dimitri/doxygen/manual.html .
Those of you which already had some experience with Doxygen will notice
that some of thing present here don't necessarily have to be done this
way - Doxygen is a very flexible tool to suit different purposes - but
these are more or less the convetions used so far.
/**/
/** \name Read - Important */
/**/
/[EMAIL PROTECTED]/
I really ask for the Doxygen markup being used in _every_ new piece of
code in the DRI/Mesa project, regardless of how complete is the
surrounding documentation. Let's assume that _all_ code will be
documented so whatever can be done now is less work to be done later.
Yes, there _is_ a real benefit in having all the code documented.
Doxygen allows to produce documentation cross-referenced with the source
code, making a wonderfull source browsing tool for someone wanting to
study the code. Specifications as the ones found on
http://dri.sf.net/doc are good for an initial draft but they require
constant and time-consuming maintaince, and eventually get obsolete.
Code documentation is not only easier to maintain - by updating
simultaneously with the code -, as also benefits from the same
versioning as the code.
/[EMAIL PROTECTED]/
I hope I have give a good taste of source code documenting with Doxygen,
and made a good case for support for using it.
José Fonseca
---
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] fw: you need D *E *B *T help, then let us help o kmy
Title: (:**get out today**:) G$T D$BT FR$$ TODAY G E T O U T O F D E B T T O D A Y STOP CREDITOR HARASSMENT REDUCE, CONSOLIDATE, ELIMINATE ALL YOUR BALANCES UP TO 70% LESS THAN WHAT YOU PAY NOW EX. REDUCE MONTHLY PAYMENT FROM $500 TO $150 FIND OUT HOW TODAY **LIMITED TIME OFFER APPLY TODAY** For removal util-software.net these mailings please follow this link x dxvc uysa plvlxxy xlx ws
Re: [Dri-devel] radeon_vtxfmt.c and alpha-errors
It works (as expected).
to a) For ..._FPALPHA its then as in the r200-driver.
to b) Who know's what should be done if lighting is
enabled but (ctx->Light.ColorMaterialEnabled) isnt set?
At least your patch which enables .._PKCOLOR
didnt affect the programs I tried.
Later I tried to enable .._FPALPHA depending on
(ctx->Color.BlendEnabled) and it worked well for
some programs, but didnt work for another testprogram
with a rotating cube:
1.)when enabling lighting (pressing "l"), then
blending (b), it looked bad: texture-corruption, switching
back no non-blending and the texture was OK, switching to
blending: texture-corruption, ...
2.)But after restarting the program:
when enabling blending before lighting, it looks good
in "blending-mode".
When switching back to non-blending: texture-corruption, but
a different manner than in the 1.st case.
its strange..
Disabling lighting temporarly and the texture looks ok,
but you CANT "switch" between the 1) and 2) case by
temporarily disabling lighting, switch blending and
reenabling lighting.
Only a restart of the testprogram can do this.
so ..FPALPHA should just be enabled with FPCOLOR like in your patch.
best regards,
Andreas
Am 2003.04.01 10:50:18 +0200 schrieb(en) Keith Whitwell:
Andreas,
Looking at the code, the FPCOLOR/FPALPHA elements are only turned
on when colormaterial is used -- in all other cases we use a ubyte
'PKCOLOR' representation.
If we're using FPCOLOR, I don't think that it would be so bad to
always turn on FPALPHA too, as it seems like the current tests are
missing a case for you.
So, I propose the attached patch, which
a) always includes alpha in color material modes
b) includes a packed color even if lighting is turned on.
In other words, this will always send a 4-component color to
hardware.
Keith
? Am
? diff
Index: radeon_vtxfmt.c
===
RCS file:
/cvsroot/dri/xc/xc/lib/GL/mesa/src/drv/radeon/radeon_vtxfmt.c,v
retrieving revision 1.16
diff -u -r1.16 radeon_vtxfmt.c
--- radeon_vtxfmt.c 31 Mar 2003 21:46:29 - 1.16
+++ radeon_vtxfmt.c 1 Apr 2003 08:47:53 -
@@ -566,11 +566,11 @@
* directly.
*/
if (ctx->Light.ColorMaterialEnabled) {
- ind |= RADEON_CP_VC_FRMT_FPCOLOR;
- if (ctx->Color.AlphaEnabled) {
- ind |= RADEON_CP_VC_FRMT_FPALPHA;
- }
+ ind |= (RADEON_CP_VC_FRMT_FPCOLOR |
+ RADEON_CP_VC_FRMT_FPALPHA);
}
+ else
+ ind |= RADEON_CP_VC_FRMT_PKCOLOR; /* for alpha? */
}
else {
/* TODO: make this data driven?
---
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] iqxpned qfuuc Please don't take the risk
B4BwcxcF6nh8210J68eSH4Wsw7foC2fYxklwsrgophjnpwyyohknjaksfxm Norton SystemWorks 2003 Software Suite Professional Edition 90% Off $300 Combined Retail Value! Five Feature-Packed Utilities; One Great Price! Your computer needs Systemworks Don't wait until it is too late! Includes 5 Powerful Programs *Norton AntiVirus 2003 *Norton Ghost 2003 *GoBack 3 Personal Edition *Norton Utilities 2003 *Norton CleanSweep 2003 - Your Price for this entire package: $39.99! For more information about this limited-time amazing package or to place your order http://dealshowroom.com/nsw15.htm Opt-Out Instructions: We are strongly against sending unsolicited emails to those who do not wish to receive our special mailings. If you wish to "opt" out: http://dealshowroom.com/goodbye.html G1mLqOSTu0XOs6VlC1GCMPQ826PnVxTC1L4 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] radeon_vtxfmt.c and alpha-errors
Andreas,
Looking at the code, the FPCOLOR/FPALPHA elements are only turned on when
colormaterial is used -- in all other cases we use a ubyte 'PKCOLOR'
representation.
If we're using FPCOLOR, I don't think that it would be so bad to always turn
on FPALPHA too, as it seems like the current tests are missing a case for you.
So, I propose the attached patch, which
a) always includes alpha in color material modes
b) includes a packed color even if lighting is turned on.
In other words, this will always send a 4-component color to hardware.
Keith
? Am
? diff
Index: radeon_vtxfmt.c
===
RCS file: /cvsroot/dri/xc/xc/lib/GL/mesa/src/drv/radeon/radeon_vtxfmt.c,v
retrieving revision 1.16
diff -u -r1.16 radeon_vtxfmt.c
--- radeon_vtxfmt.c 31 Mar 2003 21:46:29 - 1.16
+++ radeon_vtxfmt.c 1 Apr 2003 08:47:53 -
@@ -566,11 +566,11 @@
* directly.
*/
if (ctx->Light.ColorMaterialEnabled) {
-ind |= RADEON_CP_VC_FRMT_FPCOLOR;
- if (ctx->Color.AlphaEnabled) {
- ind |= RADEON_CP_VC_FRMT_FPALPHA;
- }
+ind |= (RADEON_CP_VC_FRMT_FPCOLOR |
+RADEON_CP_VC_FRMT_FPALPHA);
}
+ else
+ind |= RADEON_CP_VC_FRMT_PKCOLOR; /* for alpha? */
}
else {
/* TODO: make this data driven?
