Originally posted by bridgman
View Post
Announcement
Collapse
No announcement yet.
The Linux 2.6.36 Kernel Will Have Some Fun DRM
Collapse
X
-
I actually saw quite a big difference with HyperZ on my nasty Radeon IGP 345M. It turned what was otherwise a completely useless piece of crap into something that was almost usable. I was able to switch from 800x600 to 1024x768 in some games like RTCW. Yes, I realise this chip was never meant for games but that's all I had at the time.
Leave a comment:
-
Originally posted by FunkyRider View PostIn other news, R800 (EG) acceleration will be picked up in Linux Kernel 2.6.48! It means you suckers who bought the cards will wait for another 3 years! haha
You're not wrong though. It will be in 2.6.48 as well
Leave a comment:
-
Originally posted by Nille View PostSounds like this is now the time for Alex or Richard to ask Question about SI, NI and Fusion
NI OSS support: 2020 AD
Fusion support: who knows?
Leave a comment:
-
In other news, R800 (EG) acceleration will be picked up in Linux Kernel 2.6.48! It means you suckers who bought the cards will wait for another 3 years! haha
Leave a comment:
-
Originally posted by yotambien View PostIn that case, I didn't know what you meant. I thought the situation was something like, "we now know how to correctly program these chips within the OSS design". Instead, it seems that you were actually missing hardware details.
In many cases we know what registers need to be programmed and what to put in them, but there are subtle seauencing dependencies which are not documented anywhere.
The devs have fairly easy access to 99% of the HW details and can work through the driver and hardware teams to get to maybe 99.9% fairly easily. That last 0.1% is a real pain though... and quite often the chip seems completely broken until you find that last 0.1% ;(
There are all kinds of troubleshooting tools, it's just that modern high end GPUs are really big and complex. That works OK when the effort is spread across thousands of people, but it's a bit hard for a small team to do the same. That's why I have hope for piggybacking on the original design effort.
Originally posted by yotambien View PostNow, this comment obviously comes from somebody whose coding skills go no further than solving equations in python, but, if some OSS developers have access to the millions of lines of code you talk about, i.e. they work not only from the released documentation but also from closed code, how do they manage to restrict themselves and not implement the solutions adopted in the closed driver? Are the drivers so different in complexity, size and design that there are no low hanging fruits to be taken from that information? Not that I doubt of their professional integrity, of course : )
EDIT - I wonder if having to delete and repost rather than edit is artificially inflating my post count ?
Leave a comment:
-
Intel GMA 4500MHD?
I really hope Intel will be on time (2010 Q3) with its 4500MHD full hardware H.264 support.
Leave a comment:
-
Originally posted by yoshi314 View Posti wonder how much difference does hyperz make, in raw numbers.
Leave a comment:
Leave a comment: