--> anholt (~anholt@forest-34-86.lclark.edu) has joined #dri-devel --- ChanServ gives voice to anholt --> jor (foobar@adsl219194.adsl.utwente.nl) has joined #dri-devel --> mczak (~chatzilla@dclient217-162-140-78.hispeed.ch) has joined #dri-devel --> maximo (~maximo@200.196.24.8) has joined #dri-devel --> andreas_s (~andreas_s@pD902E0F4.dip0.t-ipconnect.de) has joined #dri-devel --> fxkuehl (~fxkuehl@D48d7.pppool.de) has joined #dri-devel Hi all, is the dri-devel list a bit slow today? There was unusually low trafic, not even an IRC reminder. fxkuehl: That doesn't seem good. I haven't seen anything fxkuehl: I wonder if there's another round of worms bogging things down. :( idr: I got four from the same address today (of course all with different From: header). fxkuehl: How's the config work going? idr: I havn't been working on in last week. I consider it largely done as far as a merge is concerned. idr: IMO further features like support in more drivers and more options can be done once the infrastructure is merged into the trunk. idr: I also hope that other developers will do some of that work. I understand my part as providing the tool for it. fxkuehl: Right. As I mentioned last week I will be away for 2 weeks starting on wednesday. I'm planning to merge when I get back unless serious issues show up in the mean time. fxkuehl: Which drivers have you already modified? Radeon, R200, and MGA, right? fxkuehl: That sounds like a good plan. idr: and r128. All drivers that use the common vblank code. fxkuehl: Okay. <-- jor has quit ("restart X") idr: I just noticed that there is a wiki on dri.freedesktop.org. That's a real nice feature for keeping documentation up-to-date. I should probably make my troubleshooting page a wiki fxkuehl: wiki? * idr blushes at his ignorance. idr: :) It's a web service where all or selected users can edit documentation in their web-browser. Often there is a version management in the background. Editing is not in HTML but a simple plain-text markup that is rendered as HTML when viewed. <-- bkw has quit ("Real men don't do backups, real men cry.") fxkuehl: That sounds pretty cool. So, are we "officially" moved over to dri.freedesktop.org now? idr: not yet. We need to bring the repo over one more time, but it sounds like people are excited to have it happen I'll go ahead and do that noe now anholt, mharris: I sent mharris my ssh info yesterday. How long will it take until I get an ssh account? fxkuehl: until we kick mharris and he wakes up? :) I just registered as a web/tiki user on dri.freedesktop.org. It sent me a wrong link for the first login: http://pdx.freedesktop.org/tiki-login_validate.php?... * anholt just remembers that he can do it, too. I must be dri.free... so you can send me username and ssh key ahh, crap, we didn't get that fixed? stick an extra /tiki/ at the beginning (eta@lclark.edu for your keys) i also have problems viewing the pages with mozilla firebird. Often I have to reload a page to see the content. The first time I only get the side bar. fxkuehl: saw that with moz (1.5b), too. you can see it when you scroll to the right or hit refresh anholt: actually exchanging the pdx for dri worked. anholt: pdx? Where is freedesktop.org hosted? idr: Portland State University (oregon) fxkuehl: I've reported it to keithp anholt: Holy crap! That's my alma mater! :) anholt: One more thing, the links for standard and secure login are broken. right, forgot to report that maximo: Hi, how's the savage work going? fxkuehl: try sshing to dri.freedesktop.org? Also, next week I'm going to be introducing my cousin (starting his 3rd year at Oregon State Univ.) to the magic of driver development. fxkuehl: i'm working on it right now :) idr: 3d driver development? :) To do that we're going to "port" the *OLD* 500TX driver to DRI. :) 500tx is a what? anholt: The GLINT before the MX. yeep at least to the nvidia tnt driver :) --> lurch (~lurchi@bachus.kawo1.RWTH-Aachen.DE) has joined #dri-devel anholt: works from my big box and notebook. Thanks! you're welcome --> jor (foobar@adsl219194.adsl.utwente.nl) has joined #dri-devel hi everybody have a question regarding using GL_YCbCr_MESA anholt: Check out http://www.cs.clemson.edu/~rmg/linux.html --- anholt has changed the topic to: DRI development discussion channel. Use #dri or #xfreee86 for end-user support questions. Weekly meetings held Mondays at 2100 UTC (2:00PM PDT) | Developers send your username and ssh dsa key to eta@lclark.edu for dri.freedesktop.org account idr: heheh wonder how it compares to the rage iic anholt: It should be *much* faster. The Delta does all the geometry setup. This is the mode the current gamma driver uses. hmm Part of this work may lead into making some updates to the gamma driver. Does anyone have *any* docs for any of the GLINT chips? Even the old leaked TI docs for the Permedia2 would be helpful. :) I have a radeon 9000 Mobility (Rv250 Lf), and a texture in YCbCr format is rendered as GRGB fxkuehl: maybe i'll make it work until the end of month. <-- lurch has quit (Nick collision from services.) bbiam --> lur_x (~lurchi@bachus.kawo1.RWTH-Aachen.DE) has joined #dri-devel maximo: That sounds cool. I'll be happy to test it. I was a bit busy lately so I didn't even try the Via/S3 driver with XFree4.2 on my notebook. But I'll definitely make the time to test your new driver. maximo: Exactly on what hardware are you working? I have a ProSavageDDR K4M266 (PCIID 5333:8d04). <-- strawman has quit ("Leaving") fxkuehl: actually my hardware is a savage4, i'll try to get another card but right now this is all i have. maximo: no problem. It's good if we can test it on a wide range of hardware. maximo: AFAIK the savage4 is the same core as mine, but with 4xAGP instead of 8x. fxkuehl: that's what i was thinking. :) lur_x: So, what's the problem? It's supposed to render as RGB. The point of the extension is to be able to specify a texture as YCbCr and have it automatically convert to RGB when you render it. fxkuehl: i'll also need a lot of help because i'm just begining and there is a lot of thing that i don't understand yet. maximo: Sorry, I'll be unavailable for two weeks of vacation. fxkuehl: Which chip do you have in your laptop? idr: ProSavageDDR K4M266 fxkuehl: I have a Savage/IX (or something similar) in my ThinkPad T21. fxkuehl: That's in a laptop? Interesting... idr: The texture data is interpreted as it were GRGB - so if I use a texture which has a Y level of 50% and Cb and Cr both 0, it is rendered as solid green instead of gray idr: It's an integrated athlon chipset. No color conversion is done by the hardware <-- andreas_s has quit ("Client Exiting") I'm searching for a Savage hardware history. Does someone have a link? fxkuehl: Oh! For some reason I was thinking that was the Via Pentium 4 chipset. lur_x: What does the output of the Mesa yuvsquare (in the tests directory) look like? I tried the Color_Matrix Extension too, and although this works, it seems to be done in sw idr: it's via, all right. fxkuehl: Yeah...just not for Pentium 4. :) idr: Where to download from? fxkuehl: no problem, i expect that people here help me too :) Found it: http://www.probo.com/timr/savage40.html#options and scroll down a bit. lur_x: Alas, only from Mesa CVS which, since it's still on SourceForge (right?), is painfully slow. :( I'm leaving, cu ... <-- fxkuehl has quit ("Client exiting") idr: Yes, have timeouts often * anholt receives the agp sis card so is the savage4 the same sort of thing as a savage mx/ix? lur_x: See http://mesa3d.sourceforge.net/cvs_anonymous.html anholt: I believe so. * anholt moves the new dri cvs into dri.freedesktop.org is anyone here able to wget http://cvs.sourceforge.net/cvstarballs/dri-cvsroot.tar.bz2 ? I get connection refused, but also for cvs okay. I guess we get to wait --> strawman (~strawman@stjh1-5693.nb.aliant.net) has joined #dri-devel <-- hfb has quit ("Client exiting") <-- maximo has quit ("Finalizando Cliente")