Am Dienstag, 28. Januar 2003 08:22 schrieb D. Hageman:
> On Mon, 27 Jan 2003, Philip Brown wrote:
> > I am trying to point out that none of
[-]
> > On the other hand,
> > "DRI is meant to integrate with XFree86. XFree86 has a standard
> > configuration file format. We should follow the
> > '
On Tue, Jan 28, 2003 at 01:22:55AM -0600, D. Hageman wrote:
> ...
> 2) The XF86Config file format does what it does very well. It isn't
> necessarily what we are looking for. It also isn't exactly a library that
> one can just use. It is a very custom built parser for a very specific
> purpos
On Mon, 27 Jan 2003, Philip Brown wrote:
> On Tue, Jan 28, 2003 at 07:22:33AM +0100, Sven Luther wrote:
> >
> > Another disadvantage is that parsing is so damn slow.
>
> Yeah, tell me about it.
>
> The place where I work had to buy some auxiliary processing boxes to
> augment the webservers. Bl
On Tue, 28 Jan 2003, Sven Luther wrote:
> On Mon, Jan 27, 2003 at 06:04:19PM -0600, D. Hageman wrote:
> >
> > I think you misunderstand. We aren't replacing the XF86Config file here.
> > This is for DRI specific driver settings with capabilities extending to
> > having special options for ind
On Mon, 27 Jan 2003, Philip Brown wrote:
>
> I am trying to point out that none of
>
> "XML is cool",
> "XML is a hot trend right now"
> "I havent had as much XML experience as I'd like"
>
> are valid reasons for selecting XML as the basis for a file format.
I concur completely and I don't t
On Tue, Jan 28, 2003 at 07:22:33AM +0100, Sven Luther wrote:
>
> Another disadvantage is that parsing is so damn slow.
Yeah, tell me about it.
The place where I work had to buy some auxiliary processing boxes to
augment the webservers. Black box "appliance" like things.
SSL processing engines?
On Mon, Jan 27, 2003 at 06:04:19PM -0600, D. Hageman wrote:
>
> I think you misunderstand. We aren't replacing the XF86Config file here.
> This is for DRI specific driver settings with capabilities extending to
> having special options for individual programs if need be.
>
> Now if I am mis
On Mon, Jan 27, 2003 at 10:37:06PM -0600, D. Hageman wrote:
> On Mon, 27 Jan 2003, Philip Brown wrote:
> > If you want to get experience/resume padding doing XML coding, please do it
> > elsewhere.
>
> Please don't make this a personal attack. Public forums are not an
> appropriate place for suc
Ian Romanick wrote:
Keith Whitwell wrote:
Ian Romanick wrote:
CVSROOT:/cvsroot/dri
Module name:xc
Repository:xc/xc/lib/GL/mesa/src/drv/mga/
Changes by:idr@sc8-pr-cvs1.03/01/27 15:47:14
Log message:
Major re-write of the texture upload code. Added support to G400 for
2
On Tue, 28 Jan 2003, Arkadi Shishlov wrote:
> On Mon, Jan 27, 2003 at 03:19:22PM -0800, Philip Brown wrote:
> > On Mon, Jan 27, 2003 at 11:18:43PM +0100, Felix K?hling wrote:
> > > If anyone has serious objections to XML, please let us know (mail to
> > > dri-devel will suffice ;-).
> >
> > I obj
On Mon, 27 Jan 2003, Philip Brown wrote:
> > Your argument is bogus. You can't claim that every XML file format leads
> > to unreadable files. Now, if you have a good *technical* reasons why we
> > shouldn't use XML - I would love to hear them.
>
> Looks like you dont understand.
>
> "tech
On Mon, Jan 27, 2003 at 06:04:19PM -0600, D. Hageman wrote:
>
> I think you misunderstand. We aren't replacing the XF86Config file here.
> This is for DRI specific driver settings with capabilities extending to
> having special options for individual programs if need be.
>
> Now if I am mis
Well, I did a thorough search of my xchat logs and put all the days I had
that were missing on http://dri.sf.net/IRC-logs/
There are still a couple days missing and there are few days that are
incomplete, so if anyone has a more complete log go ahead and replace
mine, they are all group writeab
I think you misunderstand. We aren't replacing the XF86Config file here.
This is for DRI specific driver settings with capabilities extending to
having special options for individual programs if need be.
Now if I am mistaken and you did understand ...
Your argument is bogus. You can't cla
On Mon, Jan 27, 2003 at 03:19:22PM -0800, Philip Brown wrote:
> On Mon, Jan 27, 2003 at 11:18:43PM +0100, Felix K?hling wrote:
> > If anyone has serious objections to XML, please let us know (mail to
> > dri-devel will suffice ;-).
>
> I object. Using xml inevitably leads to files that are complet
Keith Whitwell wrote:
Ian Romanick wrote:
CVSROOT:/cvsroot/dri
Module name:xc
Repository:xc/xc/lib/GL/mesa/src/drv/mga/
Changes by:idr@sc8-pr-cvs1.03/01/27 15:47:14
Log message:
Major re-write of the texture upload code. Added support to G400 for
2048x2048 textures and
Ian Romanick wrote:
CVSROOT: /cvsroot/dri
Module name: xc
Repository: xc/xc/lib/GL/mesa/src/drv/mga/
Changes by: idr@sc8-pr-cvs1. 03/01/27 15:47:14
Log message:
Major re-write of the texture upload code. Added support to G400 for
2048x2048 textures and use of all 12 mipmap levels.
Cool --
On Mon, Jan 27, 2003 at 11:18:43PM +0100, Felix Kühling wrote:
> If anyone has serious objections to XML, please let us know (mail to
> dri-devel will suffice ;-).
I object. Using xml inevitably leads to files that are completely
human-unreadable, except perhaps to the original developers.
Please
Hi,
If the -m32 is really necessary (are you on a 64-bit architecture?), try
putting it in DefaultGcc2i386Opt or DefaultGcc2i386Opt, otherwise you
can drop it completely. I think what's happening now is that imake looks
for a binary called "cpp -m32". Same goes for "gcc -m32".
Felix
On Mon, 27 J
Hello list,
We've been discussing general issues regarding the new DRI configuration
system recently on IRC. The most user-visible issue is the configuration
file format (until there is a GUI tool ;-).
In any case we need a more structured (nested) format than win.ini since
we want to be able to
Philip Brown wrote:
On Mon, Jan 27, 2003 at 12:24:34PM -0800, Ian Romanick wrote:
This is just a friendly reminder that the weeking dri-devel IRC meeting
will be starting in the #dri-devel channel on irc.openprojects.net at
2100 UTC (or 4:00PM EST or 1:00PST, if you prefer).
seeing as how DNS
the link is there, has to be something else.
Gregor Riepl wrote:
>
> I assume that's because there's no softlink
> /lib/cpp -> /usr/bin/cpp
> I don't know where this stupid requirement comes from, but I've noticed that
> quite a few programs expect the C preprocessor in /lib instead of /usr/bin..
This is just a friendly reminder that the weeking dri-devel IRC meeting
will be starting in the #dri-devel channel on irc.openprojects.net at
2100 UTC (or 4:00PM EST or 1:00PST, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
I'm having inter
Hi Szymon!
Monday 27, at 03:49:10 PM you wrote:
> Dnia pon 27. stycznia 2003 14:41, Konstantin Lepikhov napisa?:
>
> > possibly you compile kernel modules with gcc differ from gcc that compiled
> > XFree86 server?
>
> Hmm.. I don't know with what gcc are those debs compiled but since they are
I assume that's because there's no softlink
/lib/cpp -> /usr/bin/cpp
I don't know where this stupid requirement comes from, but I've noticed that
quite a few programs expect the C preprocessor in /lib instead of /usr/bin...
Hope this helps.
On Monday 27 January 2003 08:02, Chris Ison wrote:
> I'
Ian Romanick wrote:
Just to let you all know, I'm doing a merge from the trunk to the
texmem-0-0-1 branch. I've tagged the branch with
texmem-0-0-1-20030123-trunk-premerge. After the merge is done I will
tag it with texmem-0-0-1-20030123-trunk-merge. I'll send a message to
the list as well.
Dnia pon 27. stycznia 2003 14:41, Konstantin Lepikhov napisał:
> possibly you compile kernel modules with gcc differ from gcc that compiled
> XFree86 server?
Hmm.. I don't know with what gcc are those debs compiled but since they are
for sid and now the default gcc in sid is 3.2 so they should b
Hi Szymon!
Monday 27, at 01:24:30 PM you wrote:
> i've recently instaled x4.2.99 from http://penguinppc.org/~daniels/ on my
> debian sid box but dri don't work. I didn't noticed it on x4.2.1
>
> After instalation it started to complain about to old kernel module so i've
> installed a newer one
i've recently instaled x4.2.99 from http://penguinppc.org/~daniels/ on my
debian sid box but dri don't work. I didn't noticed it on x4.2.1
After instalation it started to complain about to old kernel module so i've
installed a newer one
[drm] AGP 0.99 on AMD Irongate @ 0xe800 64MB
[drm] Init
On Mon, Jan 27, 2003 at 02:40:00AM +0100, Bernhard Kaindl wrote:
> > TDFX didn't required any AGP support, so there's work to be done there.
> Seems so, the x86_64 developers should be able to give some more info,
> e.g. I've read in arch/x86_64/kernel/pci-gart.c that the AMD Hammer has
> an IO
30 matches
Mail list logo
