TNT1 to Geforce radeon: All visuals are supported in depth 8. Granted, I probably should have looked around more and I may have ended up finding the supported hardware page on haikuware myself. Xorg 1 , xorg. The network has 35 drivers and will take some time to go through.
|Date Added:||12 September 2017|
|File Size:||38.26 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I think that simply adding a link to the haikuware hardware page on to this page http: Hardware compatibility wiki Compatibility. Sorry, just saw you mentioned only PCI.
This one is not clear cut. Better to just support popular widely available hardware which is what developers will do with new OSes or select specific hardware and support that.
Instead, developers use a bug tracker to report problems. Yes, not working or untested with newest Haiku revision. Thus probably anyone with a modern Intel HDA device which is most new laptops and desktops gets this driver selected.
So, I am kinda iffy on hda. Section “Device” Identifier ” devname ” Driver “neomagic” Reserve the given amount of memory in bytes for the XVideo overlay. The driver supports magictraph 8, 15, 16 and 24 for all magicgra;h except magicgrah NM which does not support depth Example, some of the listed Radeon X models do not work with radeon driver.
Now back to wired. TrueColor and DirectColor visuals are supported in the other depths.
The audio should be kinda quick to do too. And yes, would be nice if there was an easier way to know hardware supported by OS from drivers included in image.
NeoMagic – Wikiwand
Rotate the display clockwise magidgraph counterclockwise. Radeon Original r to Radeon X r Add each individual card into its own listing? Using this option solves the problem at the expense of reducing the memory available for other operations.
Radeon Original r to Radeon X r s3: I just wanted to say thanks for looking into this and making driver support more clear. Granted, I probably should have looked around more and I may have ended up finding the supported hardware page on haikuware myself. I or someone else magicgrapb have to read the code to figure it out. Jens Owen, Kevin E. This leaves the hardware matrix where people can mzgicgraph their actual experience with certain hardware.
People can then click driver link s off hardware page to get to the driver page s to see if their hardware will be supported and by what driver. At least not presently but maybe later on.
Re: X-windows with NeoMagic MagicGraph 128V
So, I think it may be better to individually list each of those chipsets? For network, I am looking at taking a shortcut and not list supported hardware. The network has 35 drivers and will take some time to go through.
On boards with limited memory, display of large XVideo buffers might fail due to insufficient available memory.
CONFIG_FB_NEOMAGIC: NeoMagic display support
I think that simply adding a link to the haikuware hardware page on to this page. I think that each piece of hardware should have its own entry. So in theory you write one driver which implements the software side of the standard according to the documentation, and all conforming hardware will work.