[Dri-devel] DRM patch for i810/i830 memory allocation (fwd)

2002-07-09 Thread Mike A. Harris
Please apply this to the DRI codebase. Also forwarding it to XFree86. -- Mike A. Harris Shipping/mailing address: OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie, XFree86 maintainer Ontario, Canada, P6C 5B3 Red Hat Inc.

[Dri-devel] xf86drm.c patch to help FreeBSD's linux compatibility

2002-07-09 Thread Eric Anholt
Currently running Linux GL programs on FreeBSD doesn't work for most people because xf86drm.c checks to see if the dri device has the major number expected. When using linux *_dri.so's (which use this code) they find the FreeBSD dri device, which has a different number, so it either fails if

Re: [Dri-devel] xf86drm.c patch to help FreeBSD's linux compatibility, linux's devfs support.

2002-07-09 Thread Mike Mestnik
--- Eric Anholt [EMAIL PROTECTED] wrote: Currently running Linux GL programs on FreeBSD doesn't work for most people because xf86drm.c checks to see if the dri device has the major number expected. When using linux *_dri.so's (which use this code) they find the FreeBSD dri device, which has

[Dri-devel] IRC Meetings ML notification

2002-07-09 Thread José Fonseca
First I would like to apoligize for missing the last two IRC meetings. There was no noble reason whatsoever - I completely forgot it. Although this is no excuse, I would like to request that a notification message is always sent to this mailing list - as it was often done -, even if it's sent

Re: [Dri-devel] S3 VIRGE DRI

2002-07-09 Thread Massimiliano Lingua
On Mon, 2002-07-08 at 18:36, David Willmore wrote: Log bits: (--) PCI:*(1:0:0) S3 ViRGE/MX rev 6, Mem @ 0x4000/26 (II) LoadModule: s3virge (II) Loading /usr/X11R6/lib/modules/drivers/s3virge_drv.o (II) Module s3virge: vendor=The XFree86 Project compiled for 4.2.0, module version

RE: [Dri-devel] xf86drm.c patch to help FreeBSD's linux compatibility, linux's devfs support.

2002-07-09 Thread Alexander Stohr
I'm planing on having DRISUP_BOTH, DRISUP_BSD, DRISUP_LINUX, DRISUP_NONE defined for the 3rd element. I dont like the both thing. The design looks for me rather like a bitfild than an enum... so this would be the solution: (DRISUP_BSD | DRISUP_LINUX) a DRISUP_ALL would make more

RE: [Dri-devel] xf86drm.c patch to help FreeBSD's linux compatibi lity, linux's devfs support.

2002-07-09 Thread Mike Mestnik
--- Alexander Stohr [EMAIL PROTECTED] wrote: I'm planing on having DRISUP_BOTH, DRISUP_BSD, DRISUP_LINUX, DRISUP_NONE defined for the 3rd element. I dont like the both thing. The design looks for me rather like a bitfild than an enum... so this would be the solution:

[Dri-devel] Re: IRC Meetings ML notification

2002-07-09 Thread Mike A. Harris
On Tue, 9 Jul 2002, José Fonseca wrote: Date: Tue, 9 Jul 2002 22:09:58 +0100 From: José Fonseca [EMAIL PROTECTED] To: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 List-Id: dri-devel.lists.sourceforge.net Subject: IRC Meetings ML notification First I would like to apoligize