BeBits - Haiku Matrox MGA driver - Talkback

BeBits

Haiku Matrox MGA driver

Talkback

Go back to the Haiku Matrox MGA driver page

Post a new Talkback comment!

Do I need this?

By skiversoul - Posted on February 16, 2003 - 09:09:43 (#5945)
Current version when comment was posted: V0.13 beta2

First of all, I better say thanks for working on the driver - it's good to see. I have a G400 which works natively in R5. I don't plan to use Dual Head or TV-Out yet (might do eventually) so would I gain any advantage from installing this driver?

no dualhead on G450 or G550? TIP!

By rudolfc - Posted on February 5, 2003 - 14:20:23 (#5744)
Current version when comment was posted: V0.13 beta2

Hi,

While testing TVout I just discovered that dualhead on G450 and G550 _ONLY_ work if you coldstart the card!

So make sure you set the usebios line in the mga.settings file this way:
-------------
usebios false
-------------
And reboot. Now you can use dualhead...

Another hint:
If you want to use dualhead (or TVout) you need a 'special' application to enable that for you. It's a replacement for Be's Screen preferences panel and it's called DualheadSetup.

You can download this app from BeBits also (see link on the driver page at the bottom).

Make sure you get it... you'll probably need it one day ;-)

Rudolf.

disabling overlay

By rudolfc - Posted on December 25, 2002 - 00:51:03 (#5000)
Current version when comment was posted: V0.13 beta2

Hi,

You can disable overlay on VLC by starting it from the command line, with the option --nooverlay specified.

Be's Mediaplayer has a 'application preference' called 'enable hardware video overlays'. You can deselect the checkbox belonging to that option, and quit/restart the MediaPlayer. Now it will use bitmap output.

-----

I don't know the details of the inner workings of BeOS, so I cannot tell you what should be done exactly to really get dualhead support on it. What I do know is that we need this support to enable different resolutions and colordepths on different heads for desktop use. Also BeOS should respect different specifications for all heads; like max. pixelclock/refreshrate, max. resolution, specific colordepths, and features like: this head supports a hardcursor, it supports overlay: things like that.

It would be nice if BeOS could automatically switch from hardcursor to softcursor if the cursor moves to another head. The same applies for video: overlay should be enabled on the head that supports it, and if you move to the other head, bitmap output on that head should be done.

If a card supports overlay on both heads simultaneously, that could be supported too I suppose (don't know of any cards that support that yet BTW).
For instance ATI radeon cards also support overlay on one head only, but on these cards the unit can be switched to the other head. Thomas his ATI driver just looks at the output window position: if more than half is on head1, overlay is output there, otherwise it will be on the other head.
Unfortunately on Matrox Gxxx cards this 'better looking trick' is not possible.

Then there's another limitation on Matrox cards: the output window position for the overlay unit is always calculated relative to the overlay heads left-top corner. If you switch heads and want overlay on the right side of the dualhead 'stretched' head (which will be on the primary VGA connector) you won't get it if TVout is enabled, because BeOS gives the coordinates relative to the total Desktop's left-top corner.

I would have to seriously tweak calcutations in the overlay code in the matrox driver to get that to work: I won't bother because this should be solved inside BeOS itself. Besides: all extra calculations will slow the driver down..

So with TVout enabled, overlay only works as long as you don't switch the heads. Overlay on the TV output is not possible at all except in theory on G400, because the head that has the overlay unit in it cannot generate TV compatible output signals.

Well, after this story you know that dualhead on BeOS remains a 'trick' option, that can have its advantages, but that's never perfect.

So for the people that really want this, we have to hope that it will be incorporated in openBeOS later on or so.
If you are only interested in dualhead because of the possibility to output a movie on the second head, then you are in luck: this *can* be done on the current version of BeOS: using a video consumer node...

Rudolf.

Re: proper Dualhead

By Rene Gollent - Posted on December 24, 2002 - 18:41:09 (#4994)
Current version when comment was posted: V0.13 beta2

vlc has a command-line option to disable overlay usage, and if I remember right media player has an option for it in preferences. Unfortunately I'm nowhere near my BeOS box at the moment so I can't check exactly what/where either one is.

Proper Dualhead?

By bryll - Posted on December 24, 2002 - 12:04:33 (#4991)
Current version when comment was posted: V0.13 beta2

The lack of 'proper' dualhead under BeOS is quite annoying. What would it take to get two screens working properly, instead of one horribly stretched one with popups appearing cut half-way between your two monitors?

I realise that this is a limitation of BeOS... but ... well... what's the chances of this ever happening?

Oh, and is there a way to turn off overlay mode so that a video could be played (letterboxing if required) properly over two displays? I can't find any such options in the standard mplayer or in VLC.

Thanks in advance, and awesome work on a very functional driver for a kickass operating system :)

G550 rocks on BeOS! (thanks Rudolf)

By JP_Raven - Posted on December 21, 2002 - 19:42:26 (#4954)
Current version when comment was posted: V0.13 beta2

I think there's nothing else to add.

Unlogical results with the driver? Hint!

By rudolfc - Posted on December 16, 2002 - 23:06:51 (#4832)
Current version when comment was posted: V0.13 beta2

Hi!

If you are using this driver for the first time, *while* you previously used Mark Watson's G400 driver (upto and including V0.12), or the V0.13 alpha1 driver (which was based on that directly), you need to do an extra manual step *once* in order to activate this new driver!

You should check for this as soon as the results you get from the driver seem to be very 'off' compared to what you would expect from my rambling about it ;-)

(Short version: remove Mark's driver manually, it gets booted before the (open)BeOS driver apparantly ;-)

Here's the long, detailed version:

You need to delete two files (and reboot afterwards):

In:
~/config/add-ons/accelerants/
delete:
MGAGX00.accelerant
(you *should* find 'mga.accelerant' there if you already installed the openBeOS driver V0.13 alpha2 or up)

In:
~/config/add-ons/kernel/drivers/bin/
delete:
gx00.driver
(you *should* find: mga.driver there if you already installed the openBeOS driver V0.13 alpha2 or up)

The logfile this new driver generates is located in your home folder and is called:
mga.accelerant.log

(you can delete mgaGx00.log which is generated by Mark's driver, and you may do the same for mga.accelerant.log if it gets to big: the driver simply creates a new one from scratch)

In:
~/config/settings/kernel/drivers/
you should find:
mga.settings

This is the options file used by the (open)BeOS driver that you don't have to touch unless you want a hardcursor (and use only singlehead modes) or if you want to enable full logging: see the driver's site for details.

--------

If you install a new version of the (open)BeOS MGA driver you won't encounter this manual thing again: it's a one-time thing only.

The install script Apsed wrote for the (open)BeOS MGA driver uninstalls the previous version automatically. It just does not check for the G400 driver Mark wrote...

Hope this helps! If not, make sure to contact me!!

Best regards,

Rudolf.

By rudolfc - Posted on December 16, 2002 - 22:18:16 (#4829)
Current version when comment was posted: V0.13 beta2

Thanks for mailing,

I'll reply via normal mail. I'll first checkout the logfile you sent me. Thanks for that :-)

Rudolf.

G550 DualHead still not working for me!

By JP_Raven - Posted on December 16, 2002 - 21:36:43 (#4828)
Current version when comment was posted: V0.13 beta2

I beg your help, Rudolf.

I sent you a mail if you didn't noticed.

I hope the BeOS gods will be with us and enable me to use my both displays together!

PCI versus AGP

By rudolfc - Posted on December 16, 2002 - 20:00:58 (#4826)
Current version when comment was posted: V0.13 beta2

Hi,

Just finished dinner over here, so now I have time to place a small note about PCI/AGP stuff :-)

AFAIK the AGP slot is just kind of an extended PCI slot. You can use the AGP slot in PCI mode, or you can enable 1x, 2x, 4x or 8x AGP mode (Matrox G550 supports upto and including 4x). Also a feature exists in the AGP slot that's called sideband adressing. The AGP modes and sideband adressing speed up your videocard because the bus that connects the card with the system gets faster: this bus is the bottleneck the most of the time.

Someone told me that AGP needs a motherboard/chipset specific driver in order to work, while PCI is kind of a 'standard' solution, that would work on all motherboards.
This certainly explains I suppose why AGP is not supported on BeOS: it requires a lot of extra work.

However: the AGP slot has (more than) two more advantages over a PCI slot: It has a seperate (extra powerfull) power connection, and the AGP slot has it's private controller chip.

PCI slots 'share' such a chip: there are 3 or 4 PCI slots per controller, so they have to share the bandwidth of the bus which this controller provides.

This latter thing is very important: if you do a lot of graphics stuff, you use (a part of) the available bandwidth. If you have another card on another connector on the same bus, it uses also bandwidth on it: In effect both cards will be slowed down if they generate enough bandwidth to 'saturate' the bus.
An IDE controller or a Gigabit/100Mbit network card are examples of cards that on their own use a considerable amount of bandwidth already (in bursts).

Because most motherboards have two PCI busses (2x3 connectors for example) you could improve the situation a bit by relocating cards to get a convenient setup, but the best solution would be to insert no other card, or use the AGP slot because *this* has a bus completely on its own.

I can give some practical info as well:

AGP in PCI mode versus PCI-bus speed:
I tested the GLteapot demo with software rendering, which consumes a lot of bandwidth on the bus AFAIK. I see no speed difference whatsoever between a AGP card or a PCI card, while I tested both in the same system. (the CPU's over here were not 100% loaded so CPU power was not the problem AFAIK: I use a 2xP3-500 system over here)

power consumption and trouble in PCI/AGP slots:
The G200 card is a card that I would call 'AGP-class', because it was produced in the 'are' the AGP bus was 'common good'. This card draws a lot of power, if you compare it to normal PCI cards.
Some of you might recall the trouble that existed in the early AGP days if you used some power-consuming video cards like the TNT2: the system crashed every now and then because of 'brown-outs' in the mainboards (or graphic-cards) power-supply voltage(s).
The videocard sometimes consumes a lot of power (in bursts) which causes a voltage drop in the copper wiring of the mainboard. Because other logic is also powered with this supply, some chips got to little power during such a burst causing the system to freeze.
If you were lucky, you could overcome this problem by installing a more powerfull PC powersupply (>250Watt). If you were less lucky, your motherboards design was not good enough to withstand these power-surges and the voltage dropped even with such a supply already installed.

Anyway: I stronly suspect that users who have a G200 PCI in their system that hangs their system every now and then, are suffering from this problem. If the driver is faster, the power-burst might become heavier, resulting in more crashes for instance.
Over here I have that problem also: if I place my PCI-G200 in an old system, things go wrong. They even go wrong with the Be driver, though less often. Placing that card in my 'modern' system solves the problem immediately.

Some other users of PCI-G200 also reported this hanging problem to me. I am afraid this cannot be solved easily as you can understand.
Of course: modern motherboards have stronger power-supply lines on their mainboards, and modern PC-hausings have stronger power-supplies so a PCI card will most likely not cause these problems anymore in these systems.

Disclaimer: Of course I could be mistaken about all this: There are other scenario's one can think of that would cause the same problems. PC's are complicated machines after all. I am just stating what I think is plausible, based on my own experience...

Rudolf.

That is the scenario I would like to see.

By ernestTX - Posted on December 16, 2002 - 19:00:25 (#4824)
Current version when comment was posted: V0.13 beta2

Rudolf,

That is exactly the kind of setup I would like to see happen. On your desktop, you would have the video editing application (hopefully, the future wonderful Post Magic app ) and then you would click Play to view your video and it would show up (via some consumer/producer node thingy) on a TV monitor to view fullscreen w/o borders.

You rock, Rudolf. And I know, in theory. But, you are doing such great work, I have faith. Thanks again and to the other posts. I will probably look into the G400 card.

TVout, dualhead, and it's useability

By rudolfc - Posted on December 16, 2002 - 18:42:47 (#4823)
Current version when comment was posted: V0.13 beta2

Matrox G400-G550 cards have a special cable about 20cm in length, that connects to the secondary VGA HD15 connector. The driver is able to detect this adapter, and could automatically choose TVout instead of VGA output later on if the cable is detected.

This cable has two outputs: Y/C or S-VHS on a mini-DIN connector and CVBS on a tulip connector. I only tested output over here on a G400: that's working. Y/C and CVBS are simultaneously generated.
Beware that G450 and G550 are currently *not* capable of TVoutput on BeOS BTW, and also note that TVout contrast/intensity is too low, and that sharpness is not optimal.

If you ever used BeTVOut for Nvidia cards on BeOS, you definately *don't* want to use TVout on Matrox cards for now if you have a choice: You risk being very disappointed in the Matrox output quality..

Currently the output resolution is the same for both heads, with both outputs on VGA and one VGA combined with TVout. TV overscanning is not supported, the special DVD and VCD modes do not exist. Aspect ratio is not very good either.

You can use TVout on G400 to show your Desktop however, with the black border around the picture that's so well known, and that's nessesary to guarantee that you don't miss any content.

If you want to actually read what you display, choose a low resolution Desktop: 640x480 is recommended for NTSC and 800x600 is recommended for PAL.

One final hint: if you have green distortions on your TVoutput, choose another refreshrate in dualheadSetup. While this should not influence your TVoutput, it does however: you can remove the distortions if you are lucky.

For the future I will try to improve on a lot of aspects of this output, and also set it up for G450 and G550 if possible. On top of that dualheadSetup will have to be expanded to support different resolutions and refreshrates for both heads, so independant output is possible in theory. Also the driver needs to support that, which it currently doesn't.

Different resolutions however can only be used for a video consumer node, because BeOS does not really support dualhead.
The current dualhead implementation simply clones or stretches your Desktop on(to) the second head.
You do have the option to switch the left and right part of your Desktop on the monitors, but they have to display the same resolution. Otherwise you would miss a 'corner' of the Desktop.

Beware also that overlay output is only possible on one head. This means that if you drag your video output to the other head, you will end up with a 'magic color' output window that does *not* display video.
This cannot be helped, unless BeOS would officially support dualhead. A videoconsumer node could be very helpfull here for videofreaks also. Let me draw you a 'picture' that I would personally like very much:

You enable the use of the videocomsumer node on your Matrox card in mediaPreferences. This blocks normal dualhead use, and fixes the overlay unit to your primary head that is connected to a VGA screen.
You now start a mediaplayer that contains a video producer node, which in effect sends your video to the consumer node you just selected. This will send your video to your secondary (TV) output, instead of to a output window on VGA.

The TVoutput will be enabled in a DVD or VCD mode dependant on the type of file you play, outputting your video unscaled and fullscreen while overscanning: so no black borders on TV.
Unscaled output will create the sharpest output ever possible on TV, and you don't need the overlay unit for it. If you were to playback a MPEG1 file for example, it would need to be scaled in software (in the node), but colorspace conversion and buffer flipping is done in hardware. DVD output would be done the same, but without any scaling: your TV will do aspect correction scaling if needed.

Because you don't use the overlay unit, you can playback another video using overlay on your primary head simultaneously.
An even nicer possibility would be to instruct the overlay unit to use the TVoutput picture (in YUV format) to be the input picture for the overlay unit. That way you can see your TVoutput in a window on the primary head simultaneously: scaled and filtered.

OK, OK: I'll shut up now ;-)
That's what you get once you start on TVoutput with me. Sorry about that :-)

Now if only somebody outthere would create a videoconsumer node in advance, I would be working on the driver part to enable the above scenario... Don't know if I'll gain enough knowledge to actually pull it off, but it would be nice to try.
I can even provide sourcecode for such a node: Kevin Patterson already did a lot of work on such a thing for Nvidia cards. I would have to double check with him first for the latest status on this...

The future could be very good ;-)

Rudolf.

Re: Which cards are people using and how?

By Rene Gollent - Posted on December 16, 2002 - 17:35:49 (#4821)
Current version when comment was posted: V0.13 beta2

The dualhead cards come with adapters that plug into the second VGA port which gives you the other kinds of connectors (i.e. TV)

Which cards are people using and how?

By ernestTX - Posted on December 16, 2002 - 16:48:06 (#4820)
Current version when comment was posted: V0.13 beta2

First off, great work Rudolf.
I am thinking of getting a Matrox card, mostly for the TV-Out capability. However, in looking at different cards, there seems to be different kinds of cards, i.e. G400, G400 TV, G450, G450 eTV, as well as PCI and AGP models.
Here is what I'm looking to put together with one of these cards, and would appreciate some feedback from people who are using these cards.

Currently I have AGP GeForce 2 card, works great. I do video editing, so my thinking is getting a G400 or G450 TV card w/ TV-Out. Now comes the decision stuff. I see some G-cards w/ just 2 VGA connectors, does one of the connectors with help of converter have composite and Y/C connector? Or does the G400/450 TV cards have composite and Y/C outputs already? Also, since my other card is AGP, would a PCI G-card work in the scenario? Or would it be better to get AGP card and convert one VGA out to video outs? Does the current driver just mirror the desktop, or with the DualHead Setup driver available elsewhere, allow for 2 different resolution setups (i.e. desktop 1024x768 and TV out to 640x480)?

Any suggestions, help and guidance would be greatly appreciated and would make for a merry christmas to myself ;) Thanks

Enabling/testing dualhead on G450(?) and G550

By rudolfc - Posted on December 16, 2002 - 11:56:19 (#4816)
Current version when comment was posted: V0.13 beta2

On G550 you'll need the DVI->VGA adapter if you have a DVI connector on your card.
Dualhead only works in monitor mode ATM, so remove your TVout extension cable.
(BTW: Note that the G400 TV cable is *not* compatible with the G550 TV cable! Do not mix them up...)

The driver redetects for the TV cable on every mode switch and on boot, it's behaviour changes accordingly if you insert or remove this cable. Note please that you *should* only insert and remove cables when your system is powered off!

I found that my Iiyama 15inch CRT monitor does not work on G550 above 1024x768x32 resolution (shuts off), while on G200 for instance it does. My analog flatpanel *does* work above this however: even in 1600x1200x32 mode (on both heads). Apparantly the driver's signal timing is not yet optimal. I'll check that out later on.

OK. When you have connected two analog VGA displays to your card, you can run Mark Watson's DualheadSetup (also on BeBits), and enable dualhead clone mode for example. Make sure you select monitor mode, and for starters try 800x600 or 1024x768 mode in 16 or 32bit colordepth.

If you run into trouble, please let me know!
If you have trouble on a G450/550 with a DVI connector on it, test what happens if you connect your VGA monitor to the secondary output (HD-15 connector), and what happens if you connect it via the HD15->DVI connector while you have a TV cable plugged in on the secondary port.

For these two tests you should reboot and see if your screen works in BeOS (though the driver redetects every mode switch). If it does, the driver correctly switches it's primary output to the connectors on which your monitor is located. This is important for dualhead mode to be able to work.

Please inform me if this works correctly or not when you contact me with dualhead G450/G550 (+DVI connector) trouble. Also a logfile (< 100-200kb) would be greatly appreciated :-)

If it does not work for you, make sure to tell me: That's the only way to get it fixed provided I can find the cause...

If it *does* work, please tell me also... It's always nice to see your 'assumptions' confirmed! And *that* helps driver development also.. ;-)

Best regards,

Rudolf.

G400-G550 dualhead resolutions

By rudolfc - Posted on December 16, 2002 - 11:33:38 (#4815)
Current version when comment was posted: V0.13 beta2

Hi there,

I just tested dualheadsetup with my G550: I am able to use it in dualhead mode in 1600x1200x32 on both heads simultaniously.

According to the specs you can find at the Matrox site, G400 can do 1280x1024x32 on the second head, G450 and G550 can do 1600x1200x32: this is in monitor mode.
TVout resolutions are somewhat lower: G400 and G450 max 1024x768x32, G550 1600x1200x32.
DVI max. resolutions are 1280x1024x32 for G550, and also for G450 I think (could not verify this yet).

Currently TVout only works on G400, G450 and G550 TVout will hopefully be enabled on a later driverversion.
DVI is not yet supported, but hopefully will be later on.

While currently the refreshrates for the primary and secondary head are the same (monitor mode), they can be set independantly in theory. I'll try to setup that later on too.
Also I think I'll limit the driver to adhere to the specs for dualhead and TVout mode: currently you can 'overclock' the driver and enable 1152x864 TVout mode for instance. (Using this will shorten the lifespan of your card!)

Thanks for the comments so far!

Rudolf.

By JP_Raven - Posted on December 15, 2002 - 14:58:22 (#4802)
Current version when comment was posted: V0.13 beta2

It's a really great card! I'm happy with mine's.

However, it looks like this new drvier had DualHead support for G550 ? If it's the case I'm sad I don't succeed in using it.

How to do? I tried DualHead setup but my secondary display keeps shut off whatever I try.

I'd be happy to get help if DualHead on G550 is really supported by this new release of the driver.

Good work anyway, guys!

By Reddog99 - Posted on December 15, 2002 - 09:58:42 (#4797)
Current version when comment was posted: V0.13 beta2

This driver seems to have cured a distortion problem my G400 has always had. Great work!

Pat

Re: Dualhead

By Rene Gollent - Posted on December 15, 2002 - 03:44:30 (#4795)
Current version when comment was posted: V0.13 beta2

The G400/G450 can do a max of 1024x768 on the secondary head, since it only has a 135MHz RAMDAC powering that..the G550 would appear to be capable of 1600x1200 based off Matrox's page (http://www.matrox.com/mga/products/tech_info/g550_factsheet.cfm) if you're interested.

DualHead questions

By JJ - Posted on December 14, 2002 - 23:33:49 (#4793)
Current version when comment was posted: V0.13 beta2

Thanks for all the great work on this.

I don't use matrox right now, but I do intend to go dual head as soon as possible, that will really reduce my dependance on w2k 1 more notch.

Question, what is the dual head exp like, do you get 1600.1200.32/16 on both screens? Does the main head go even higher? How does G550 compare to G450,400 etc generally!

no overlay tip

By rudolfc - Posted on October 22, 2002 - 11:02:40 (#3703)
Current version when comment was posted: 0.13 beta1

Hi,

If you run this driver and you cannot get overlay to work, make sure you have deleted *all* of Mark Watson's G400 driver.
Some users have reported trouble here that was solved after removing the last remaining stuff on the old driver...

Rudolf.

Thanks Rudolf.

By JP_Raven - Posted on October 17, 2002 - 16:26:00 (#3655)
Current version when comment was posted: 0.13 beta1

My only hope is that all the primary head will work fine soon... So that I may have any DualHead support one day or the another! :-)

Anyway, let's all applause these driver writer -- Rudolf and all the others! Without them, no drivers, and with no driver, no BeOS ;-)

Thanks to all the courageous driver writers!!!

g550 dualhead / parhelia

By rudolfc - Posted on October 16, 2002 - 22:01:43 (#3643)
Current version when comment was posted: 0.13 beta1

Hi there,

Dualhead on G550:
Dualhead currently only works on G400 and G450 cards AFAIK. On G550 only the primary head is functional for now.
I have not even looked yet at this area. First I want all primary heads to be working optimally ;-)

Parhelia / Gxxx comparison:
Matrox has not yet published any register level docs on the Parhelia chips. Therefore I cannot tell you how different or similar these cards are. I expect a brand new design though..

As long as no register level specs are known BTW, I will not even try to support Parhelia cards. If I would have access to these specs, I would certainly take a (brief) look though..
Of course, currently I will concentrate my efforts on what I already stated on the driver's website.
There's work enough to be done for now :-)

Rudolf.

Are Parhelia and G-series at all similar on a driver level?

By Jace - Posted on October 16, 2002 - 01:50:52 (#3620)
Current version when comment was posted: 0.13 beta1

Are Parhelia and G-series at all similar on a driver level?

The reason I ask is that this new card from Matrox has me interested (course, I need a new motherboard to use one but sooner or later...). Can existing Matrox BeOS drivers be updated to support the Parhelia chipset/cards or is that a completely different family?

Hey, thanks for the work on this driver. I'm a huge Matrox fan and use nothing else. I use a Dualhead G450, btw.

DualHead support on G550

By JP_Raven - Posted on October 15, 2002 - 15:34:51 (#3608)
Current version when comment was posted: 0.13 beta1

DualHead don't work with Millenium G550. Not with mine's, actually. It didn't with the previous driver using DualHeadSetup and, well, it still doesn't work with this shiny new one with the same DualHeadSetup.

accelerant.h

By nymia - Posted on October 14, 2002 - 21:20:57 (#3600)
Current version when comment was posted: 0.13 beta1

Thanks for the comment, I'll start with accelerant.h and then go forward from there.

overlay / 3d

By rudolfc - Posted on October 14, 2002 - 08:31:26 (#3589)
Current version when comment was posted: 0.13 beta1

Hi, thank you all for your comments so far :-)

A few remarks:
Overlay: is not supported by Be's R5 MPEG codec it seems, so you need VLC to get that. Or use NiftyPlayer: it will use 'magic overlay' which actually transforms the MPEG codec output to the supported colorspace.
If you use DivX make sure you use VLC or Carlos Hasan's FFMPEG codec (de-install the old DLL wrapper codec).
With this codec you can use Be's Mediaplayer for it.
On R5's Mediaplayer overlay only works on certain types of mediafile. On DANO the supported range is much larger (also MPEG)

3D: If you look at the accelerant.h file in DANO you'll find the hooks needed for 3D in the driver. I fear this is not nearly enough info though..

Regards,
Rudolf.

By kancept - Posted on October 14, 2002 - 08:05:32 (#3588)
Current version when comment was posted: 0.13 beta1

I am still unable to get any overlay support using this or the beta sent to me. I love the card (and dualhead - but that's another issue). Any suggestions? I have disabled dualhead as suggested in the docs, and still nogo.

By nymia - Posted on October 14, 2002 - 06:30:29 (#3586)
Current version when comment was posted: 0.13 beta1

At this point trying to implement the chip's 3d ops would be somewhat of a waste of time: 1) there isn't a way to take advantage of them in BeOS 5, and 2) the specifications for doing GL drivers were never complete or released for the OGL Beta.

==============================================

Regarding:

#1, I'd like to know more of it because if this problem can be sorted out by submitting code or calling up some people will probably do more good in having a 3D API for BeOS.

#2, OK, they are incomplete, that is fine. The question now is how do we move forward from there?

Also, I think a 3D API, much like MS's D3D can be implemented, though. I would be willing to put some effort in having a 3D API a reality.

Thanks.

Re: Found it in mga_proto.h

By Rene Gollent - Posted on October 14, 2002 - 02:02:14 (#3585)
Current version when comment was posted: 0.13 beta1

At this point trying to implement the chip's 3d ops would be somewhat of a waste of time: 1) there isn't a way to take advantage of them in BeOS 5, and 2) the specifications for doing GL drivers were never complete or released for the OGL Beta.

Found it in mga_proto.h

By nymia - Posted on October 14, 2002 - 01:56:41 (#3584)
Current version when comment was posted: 0.13 beta1

OK, no need to answer the question. I found it.

This card is great for 2D ops. I hope developers who have this card can use them. The protos below show the functions:

/*acceleration functions*/
status_t gx00_acc_init();

status_t gx00_acc_rectangle(uint32 xs,uint32 xe,uint32 ys,uint32 yl,uint32 col);

status_t gx00_acc_rectangle_invert(uint32 xs,uint32 xe,uint32 ys,uint32 yl,uint32 col);

status_t gx00_acc_blit(uint16,uint16,uint16, uint16,uint16,uint16 );

status_t gx00_acc_transparent_blit(uint16,uint16,uint16, uint16,uint16,uint16, uint32);

status_t gx00_acc_wait_idle();

How about the 3D ops? Put that in and you will definitely be THE MAN!

Quick question about the instruction set

By nymia - Posted on October 14, 2002 - 01:30:16 (#3583)
Current version when comment was posted: 0.13 beta1

Just wondering if the code contains information about the chip's instruction set.

I'm interested in getting some information on the card's ability to perform matrix operations and blitting in the instruction set, though.

Thanks.

!!!

By s_d - Posted on October 14, 2002 - 00:54:54 (#3581)
Current version when comment was posted: 0.13 beta1

Inspite I use Radeon myself, I really appreciate this work!!!

By Rogier - Posted on October 13, 2002 - 22:22:43 (#3579)
Current version when comment was posted: 0.13 beta1

This is very good driver and a lot of work!!! Vooral doorgaan ;-)



	Comment Pages: << prev \| 1 \| 2 \| next >>













			Recent Downloads - # 59 Total Downloads - # 107 Total Views - # 36 User Ratings - # 15




			Video Drivers




			1. BePodder - 9.80 2. QEMU - 9.68 3. ScummVM - 9.57 4. cpu_fix - 9.42 5. Jukebox - 9.40 6. libdl.so - 9.40 7. Haiku AGP busm... - 9.35 8. vim6 - 9.31 9. Beezer - 9.26 10. HandBrake - 9.25




			1. BeOS 5 Perso... - 13,618 2. Realtek RTL8... - 13,131 3. Ati Radeon G... - 12,598 4. Ensoniq Audio... - 7,577 5. ATI Rage 128... - 7,450 6. USB Joystick... - 5,673 7. Broadcom 440x... - 5,418 8. S3 Trio 64 v2... - 4,736 9. USB Serial dr... - 4,714 10. Intel Extreme... - 4,475




			You are not logged in. Login


	Unless otherwise noted, everything is copyright © 1999-2009 Haikuware. All Rights Reserved. For more legal trivia, take a gander at our Legal Stuff page and our Privacy Statement.