hardware.
--
Ryan Underwood, <[EMAIL PROTECTED]>
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start
all cards support the framebuffer width
necessary for mergedfb.
--
Ryan Underwood, <[EMAIL PROTECTED]>
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover whic
rs for these cards. The nice thing is
that they left all the symbols in for you if you wanted to rev-eng it.
I don't know of anything that would make the rev-eng illegal, unless you
agreed to a EULA prohibiting it or else you end up violating a patent or
something.
--
Ryan Underwood, <[EMAI
Found this "random" link which some folks may be interested in:
http://members.shaw.ca/mm99mm/S3_Virge_programming_spec.html
--
Ryan Underwood, <[EMAIL PROTECTED]>
---
SF email is sponsored by - The IT Product Guide
Read
general rule of thumb regarding patents is to play dumb
until you haven't any choice (receive a C&D, or patent is somehow
brought to your attention otherwise).
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
L and bump mapping and I don't know of
the other chips do.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
7;s the default thing to do for code
going into the Linux kernel. It doesn't necessarily mean that they
would only grant permission for the code to be used in GPL scenarios.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
alization and locking as well as checking the validity of the
buffers if desired.
I just mashed this down so its probably half baked. Any thoughts?
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
On Sat, Jun 12, 2004 at 11:40:42AM -0400, Alex Deucher wrote:
>
> multi-head and ryan's latest work removes the hallib requirements from
> the matrox driver,
Not yet. Hopefully soon. :)
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
is still in a separate library, the legal issues have not changed.
Is it possible to integrate s3tc but ship with it disabled, similar to
how FreeType operates regarding the hinting patents owned by apple?
Then individual distributors can choose whether or not to enable it
depending on their loc
fect. I'm slowly beginning to suspect that R/W doesn't mean what I
think it means with respect to MMIO registers.
--
Ryan Underwood, <[EMAIL PROTECTED]>
#include
#include
#include
#include
#include
#include
#include
#include
#define MGA_VENDOR 0x102b
#define G400_DEVICE
On Mon, Apr 26, 2004 at 02:49:36AM -0500, Ryan Underwood wrote:
>
> I wrote a quick program to parse out the microcode from the XFree86
> mga_ucode.h files.
attaching sample output. seems that g200 and g400-mt ucodes are much
bigger than g400 ucodes in general.
--
Ryan Underwood
On Sun, Apr 25, 2004 at 11:57:28PM -0500, Ryan Underwood wrote:
>
> I think I'll be doing some footwork on this one.
I wrote a quick program to parse out the microcode from the XFree86
mga_ucode.h files. From here a disassembler can be written if we can
ever figure out the op code
> support DDR RAM and tdfx didn't recognize it. Is still there any
> developer that could fix it?
can you take a physical picture of this card and post it? I have never
seen such a card.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
similar, and
that equivalent C implementations are available. All the world's not a
386, especially with hardware who are implemented in PCI form.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
e someone
identifies this binary blob as code-without-source in the future, and
defer the actual removal to that future date if it ever arrives?
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
On Sat, Apr 17, 2004 at 08:16:36PM +0100, Alan Cox wrote:
> On Sad, 2004-04-17 at 19:40, Ryan Underwood wrote:
> > Of course, if the legal advice you refer to was specifically aimed at
> > the firmware scenario, where you have a blob of who-knows-what that does
> > no
s seemed to imply that you could
upgrade the microcode to a new version without changes to the driver.
This is not always true because the command interface may change from
revision to revision of the microcode.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
ing systems
more flexible. My beef is mainly that a lot of people are considering
sourceless firmware to be outside the DFSG, which amounts to an
inconvenience to users for a dubious political gain. But that is
off-topic for dri-devel probably.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
t are not, or not known to be, general purpose computers. As long as
the microcode is legally redistributable, I dont have a problem with it.
(Granted, some of the microcode included with the Linux kernel seems not
to be freely redistributable, and that is obviously a problem that some
have be
ware fog and alpha; take
your pick. :)
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
y.x/743
Apparently the card advertised hardware T&L on the box, and Diamond
assumed they would be able to get it working in driver upgrades after
the product shipped.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
under
windows. I guess it would only be G400+, since G200 only has one WARP
so it seems that it wouldnt be able to do hardware multitexture.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
l for savage2000 support.
Savage2000's 3D engine has a T&L unit that, IIRC, S3 never even could
get working right. I think it worked in D3D but they disabled it in
OpenGL due to hardware problems or something. So there would be another
unique aspect to the Savage2000 compared to the r
nly someone were able to coax a little info
from ATI. :) I think only NDA people might have any luck there though,
and unfortunately none of them probably have the hardware anyway. I'd
definitely want to play around with it once I clear out my current mga
stuff, in case someone knows who
Ermm...
http://www6.tomshardware.com/graphic/19991230/fury-04.html
Looks like it enumerates two display adapters. Which means either the
two chips _are_ seen as separate entities by PCI, or the windows driver
has some kind of child/multifunction device hack in it.
--
Ryan Underwood, <[EM
two chips divide up rendering tasks. Also, was there a
dual head version made? There is a place on the board for a second VGA
connector, but I can't find any info about that either.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
I'm not sure about what features/kludges Knoppix ships their kernels
with.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
On Sat, Jan 31, 2004 at 04:19:45PM -0600, Ryan Underwood wrote:
>
> That should be fine. Pull Mesa and xc from DRI CVS, edit
> xc/config/cf/host.def to point to the Mesa directory, and in xc/Makefile
> comment out this line:
>$(MAKE_CMD) $(MFLAGS) $(WORLDOPTS) World
&g
ny experience with
the savage driver but this is what I use for other DRI work. If you
have any other questions feel free to post here.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
hing for further instructions and thought perhaps I was supposed to
use -rtrunk instead.
I've just checked a complete copy and am building it now. Thanks for
the tutelage.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
On Wed, Jan 21, 2004 at 01:30:15AM +0100, Michel Dänzer wrote:
> On Wed, 2004-01-21 at 00:02, Ryan Underwood wrote:
> >
> > Are those fixes on a branch somewhere? It appears trunk's version is:
> > /* $XFree86: xc/lib/GL/mesa/src/drv/mga/mga_xmesa.c,v 1.19 2003/0
On Tue, Jan 20, 2004 at 02:13:50PM -0800, Alex Deucher wrote:
>
> --- Ryan Underwood <[EMAIL PROTECTED]> wrote:
> [snip]
> >
> > No code was copied, only some defines. I need other people to check
> > the
> > code and tell me if it will break on other v
On Wed, Jan 21, 2004 at 01:30:15AM +0100, Michel Dänzer wrote:
> On Wed, 2004-01-21 at 00:02, Ryan Underwood wrote:
> >
> > Are those fixes on a branch somewhere? It appears trunk's version is:
> > /* $XFree86: xc/lib/GL/mesa/src/drv/mga/mga_xmesa.c,v 1.19 2003/0
ers() call is the important bit. Without that the
> pipeline wasn't flushed properly.
Are those fixes on a branch somewhere? It appears trunk's version is:
/* $XFree86: xc/lib/GL/mesa/src/drv/mga/mga_xmesa.c,v 1.19 2003/03/26 20:43:49 tsi Exp
$ */
but that is from Michel's trunk
On Wed, Jan 21, 2004 at 12:23:17AM +0200, Ville Syrjälä wrote:
> On Tue, Jan 20, 2004 at 03:47:49PM -0600, Ryan Underwood wrote:
> >
> > Hi,
> >
> > GL_ATI_envmap_bumpmap seems to describe identical functionality to
> > DirectX6 EMBM. ATI's dr
e sure my
i2c code is 100% correct.
Someone needs to track down the bug that causes a server crash and
subsequent lockup if a dualhead config is used but mga_hal is not
available (either not around or wasn't compiled with support for it). I
thought I fixed it with a oneliner in that patch bu
Hi,
GL_ATI_envmap_bumpmap seems to describe identical functionality to
DirectX6 EMBM. ATI's drivers support this extension and it is
implemented in Mesa apparently. Does anyone know of a demo or sample
code that utilizes this extension?
--
Ryan Underwood, <[EMAIL PROTECTED]>
si
ed with the second head. I don't have a second
> monitor to test right now.
I just uploaded a patch to the bug tracker that makes DPMS work on the
second head among other things (i2c/maven related).
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
should do?
If it really is forking somehow, using -f on strace should follow the
forks. But I have a feeling that isn't what is really going on.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
n't have a second
> monitor to test right now.
Thanks for your tries and your insight. I will try to hunt these bugs
when exams are over. In the meantime let me know if you come up with
any patches and I can test them out.
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
y use DPMS on the second head? My second monitor blanks from the X
screen blanker, but remains on, consuming power. The first one powers off
as expected. I posted earlier about this to the XFree86 list, including a
list of changelog entries corresponding to second-head DPMS on G400, but
didn
On Wed, Dec 10, 2003 at 12:25:36PM -0600, Ryan Underwood wrote:
>
> In an open software architecture like the DRI, we should do our best to
> support proprietary vendors when they give us the means to do so, but
> all the pissing and moaning about what they will and won't do shou
what they will and won't do should go
either to /dev/null or, more productively, towards opencores.org and a
fully open windowing accelerator and programmable 3D graphics pipeline
core. The technology is there, it just needs the mindshare and people's
willingness to embrace it.
Imagi
On Wed, Dec 10, 2003 at 09:03:34AM +0200, Ville Syrjälä wrote:
> On Tue, Dec 09, 2003 at 01:24:16PM -0600, Ryan Underwood wrote:
> >
> > Thanks for the insight. Is this already something that has been
> > extensively looked at without success, or would it be worth my tim
it off should solve the
> problem since render (used for AA fonts) will use teh software paths
> instead.
>
> Alex
>
> --- Ryan Underwood <[EMAIL PROTECTED]> wrote:
> >
> > By "turn off HW render", you mean RenderAccel "off", or NoAccel "
e and
> I don't know if they both keep state properly. that's probably were
> your corruption comes from.
>
> Alex
>
> --- Ryan Underwood <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I've had some problems with certain
is stomping on memory used for the fonts, but only under certain
circumstances (triggered by e.g. quake2 and crack-attack).
any ideas?
--
Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
to the
> 2D/3D drivers is impossible since it is a binary only driver! Ask
> matrox to add support. that's your only option right now.
>
> Alex
--
Ryan Underwood, <[EMAIL PROTECTED]>
---
This SF. Net email is sponsored
fer driver though, so maybe things are different
e.g. if you are using a VGA text mode on console.
--
Ryan Underwood, , icq=10317253
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
ht
16MB, no more than 16MB of system memory can be used as
non-local texture memory for the AGP card.
--
Ryan Underwood, , icq=10317253
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_
51 matches
Mail list logo
