Although there are still plenty of known issues with the R600 driver, I've decided to the ninth public TinyGL beta release with a preview of the R600 driver included.

Although this is called the R600 driver, in this update only Evergreen and Northern Islands based Radeons are supported. Support for R600 and R700 based Radeons will be added at a later date.

Since the R600 driver is a preview driver with known issues, expect to find plenty of applications and games that either misrender or crash the system. If you come across something that doesn't work correctly, please report it here in this thread and in the case of misrendering, please include a screenshot as well.

Edit: The newly supported Radeons are the following models:
Radeon HD 5450
Radeon HD 5550
Radeon HD 5570
Radeon HD 5610
Radeon HD 5670
Radeon HD 5750
Radeon HD 5770
Radeon HD 5830
Radeon HD 5850
Radeon HD 5870
Radeon HD 5970
Radeon HD 6350
Radeon HD 6450
Radeon HD 6570
Radeon HD 6670
Radeon HD 6750
Radeon HD 6770
Radeon HD 6790
Radeon HD 6850
Radeon HD 6870
Radeon HD 7350
Radeon HD 7450
Radeon HD 7470
Radeon HD 7510
Radeon HD 7570
Radeon HD 7670
Radeon HD 8350
Radeon HD 8450
Radeon HD 8470
Radeon HD 8490
Radeon R5 220
Radeon R5 230
Radeon R5 235
Radeon R5 235X

Quote:

Sweet!!!

> The newly supported Radeons are […] everything in the Radeon HD 6000 series […]

Nice. Does this include improved 2D support for TeraScale 3 (RV970-based HD 69xx)?

Quote:

No, you're right. It still very much excludes Cayman-based Radeons. I'll update the list in the post you quoted.

Hey @bigfoot
Have you received my e-mail (July, 18th 2023, subject "depth buffer in tiinygl")?

I still can't found reason of the simple problem in rendering with enabled depth buffer test but disabled writing to depth buffer. I don't see any reason why the artifacts are visible. Polygons on the same z-position shouldn't collide if writting to depth buffer is disabled. I used this method quite often and it always worked without any problems (also on macOS).

I attached to the mail simple source which shows the the problem. It is reporducible on my PowerBook G4 A1138.
I use TinyGL from MorphOS 3.18. I haven't tried the ninth public TinyGL beta release yet.

[ Edited by MDW 15.08.2023 - 12:11 ]

Quote:

Yes I have! I'm a bit behind on replying to emails, sorry about that. I'll get to yours in the near future.

Quote:

That won't make a difference, so you don't have to test.

Quote:
No problem. I can imagine your TODO list. :)

I asked you because I had some problems with my account @amiga.pl so I didn't know if my e-mail was received. Now I know so I don't hurry up please. It is not a blocker for me, I don't have any deadline. I have thousand other tasks in my lame-project. :)
Thanks!

Checking in on any updates?

If it would help I'm happy to pitch in to get a G5 PCIe system to Bigfoot.

You might wanna add a generator to that .....

Quote:

I would as well! I would do anything to get support for the newer cards like OS4.1 has on its systems.

Quote:

Yeah +1

Hi friends!
Any news about this?
Just for curiosity..not pressure! :)

The offer still stands by me and other to buy and ship a PCIe based PowerMac to Bigfoot.

Question...

Radeon HD 8490 is one of the cards listed as added in the newest TinyGL beta. I have no clue what these cards are like in terms of performance, 2D / 3D overlay, etc. but there seem to be a lot of OEM Dell and HP cards on eBay for like £15. Anyone got any idea if these would work? I'm looking for something to try in the 4x slot of my X5000 (via an extender due to physical limitations).

Assuming we don't know, and I give it a go, is the release 9 of the TinyGL driver included in the download of MOS 3.18 so the card will work from boot or are there complications in bringing up a fresh system with such a card?

These drivers are not needed for booting, so anything that is listed for 2D in the 3.18 FAQ will work.

So, the reason I asked the question is because the card in question (HD8490) is listed in this thread (previous page), but isn't listed at all on the Morph 3.18 hardware FAQ page. I don't think it really matters TBH. When I looked up the hardware it seems that an 8490 isn't really much better than the HD5450 that I do have. Unfortunately that one refuses to work in the 2nd slot.

Quote:

https://www.morphos-team.net/hardware

Code:

So it is listed and it should give you a basic working system on a clean 3.18 install.

But sure it was an entry level card released 11 years ago, so I wouldn't ecpect much.

Sorry, don't know how I missed that. I did look, honest!

Today I've released the tenth public TinyGL beta release.

The main focus of this release is implementing support for framebuffer objects. However, in the course of doing that, many other related and unrelated parts of TinyGL have been improved as well, resulting in better OpenGL compliance and more features being implemented.

Please note that the R600 driver is absent from this release, but that it will be readded in a future release once I've updated it to the current TinyGL requirements.

For software developers, please make sure you read the included ReadMe file for important information on using new TinyGL features and fixes.

I'd like to thank everyone who's helped test this release, but especially beworld for his tireless testing and feedback regarding framebuffer objects and my general TinyGL improvements as well as jPV for his very helpful testing in this last week that helped me fix a handful of problems that would otherwise have made it into this release undetected.

Yay!

Thanks so much bigfoot, beworld and jpv! Will try right now.

Wow! Good news!

Great news, thanks bigfoot, beworld and jPV!

At every boot I have the activity indicator of debug 'on'. I do not know what/who is responsible, sdl 2 or tinygl latest releases. So here is the log that I obtain.

20.070| 128 bytes read
20.070| block#0 bytesum 0x0
20.070| 0x00: 00 ff ff ff ff ff ff 00 26 cd 11 66 26 0b 00 00 .ÿÿÿÿÿÿ..Í.f....
20.070| 0x10: 10 19 01 03 80 3c 22 78 2a 2f a5 a5 54 50 9e 27 .......x....TP..
20.070| 0x20: 10 50 54 33 08 00 71 00 81 40 81 80 a9 40 b3 00 .PT3..q.........
20.070| 0x30: 95 00 d1 c0 01 01 02 3a 80 18 71 38 2d 40 58 2c ..ÑÀ......q8..X.
20.071| 0x40: 45 00 56 50 21 00 00 1e 00 00 00 ff 00 31 31 32 E.VP.......ÿ.112
20.071| 0x50: 38 31 35 31 36 30 32 38 35 34 00 00 00 fd 00 37 8151602854...ý.7
20.071| 0x60: 4c 1e 53 11 00 0a 20 20 20 20 20 20 00 00 00 fc L.S............ü
20.071| 0x70: 00 50 4c 58 32 37 38 33 48 0a 20 20 20 20 00 61 .PLX2783H......a
20.071|
20.071| ID manufacturer Name = 'IVM'
20.071| ProductCode = 0x6611
20.071| Serial Number 260b0000
20.071| Week of Manufacture 16
20.071| Year of Manufacture 2015
20.071| EDID Structure Version 1.3
20.071|
20.071| Basic Display Parameters and Features
20.071| checkDDCdata: Video input: Digital signal
20.071| Max. Horizontal Image Size 60 cm
20.071| Max. Vertical Image Size 34 cm
20.071| Display Transfer Characteristic (Gamma): 2.2
20.071|
20.071| Feature Support (0x2a)
20.071| Supports Active Off/Very Low Power
20.071| RGB color display
20.071| Preferred timing mode is indicated in the first detailed timing block
20.071| (Note: Use of preferred timing mode is required by EDID structure version 1.3 and higher
20.071|
20.071| Phosphor or filter chromacity
20.071| red_x 0.6445 red_y 0.3301
20.071| green_x 0.3154 green_y 0.6201
20.071| blue_x 0.1543 blue_y 0.06445
20.071| white_x 0.2354 white_y 0.1338
20.071|
20.071| Established Timings
20.072| 640 x 480 @ 60Hz (IBM, VGA)
20.072| 640 x 480 @ 67Hz (Apple, MacII)
20.072| 800 x 600 @ 56Hz (VESA)
20.072| 800 x 600 @ 60Hz (VESA)
20.072| 1024 x 768 @ 60Hz (VESA)
20.072|
20.072| Standard timing identification #1
20.072| code 0x7100 (HActive 1152 Pixels VActive 720 Lines RefreshRate 60Hz Aspect 16:10)
20.072| Standard timing identification #2
20.072| code 0x8140 (HActive 1280 Pixels VActive 960 Lines RefreshRate 60Hz Aspect 4:3)
20.072| Standard timing identification #3
20.072| code 0x8180 (HActive 1280 Pixels VActive 1024 Lines RefreshRate 60Hz Aspect 5:4)
20.072| Standard timing identification #4
20.072| code 0xa940 (HActive 1600 Pixels VActive 1200 Lines RefreshRate 60Hz Aspect 4:3)
20.072| Standard timing identification #5
20.072| code 0xb300 (HActive 1680 Pixels VActive 1050 Lines RefreshRate 60Hz Aspect 16:10)
20.072| Standard timing identification #6
20.072| code 0x9500 (HActive 1440 Pixels VActive 900 Lines RefreshRate 60Hz Aspect 16:10)
20.072| Standard timing identification #7
20.072| code 0xd1c0 (HActive 1920 Pixels VActive 1080 Lines RefreshRate 60Hz Aspect 16:9)
20.072|
20.072| monitor descriptor 2 type 0xff
20.072| Monitor S/N: 1128151602854
20.072| monitor descriptor 3 type 0xfd
20.072| Monitor range limits
20.072| min vfreq 55 max vfreq 76
20.073| min hfreq 30 max hfreq 83
20.073| max pixclk 170MHz (0)
20.073|
20.073| monitor descriptor 4 type 0xfc
20.073| Monitor name: PLX2783H

I forgot to say that I obtain this debug log only with my macmini. On my amigaone x5000 I do not obtain any debug log.

Brumiga

[ Edité par Brumiga 29.09.2024 - 18:33 ]

@Brumiga

Ignore it.