Joblo stop development but the driver is really needed. Callisto works but not perfect and we have no sources to correct it.

Now I have working sources of Apple's IONDRVFramebuffer and Joblo's XRadeonFB that is based on very old Framebuffer v1.2 and it doesn't work.

I have Radeon9000 and work under Tiger. Is there any programmer want to join us (with OLE2) to make this project works in Leo with other Radeons?
Useful link to linux drivers

Any suggestions and advices welcomed.

TODO:
1. Make zero project be working. - Done!
2. Add Radeon functionality step by step keeping the driver works.
3. Study what IORegistry's keys used by the driver and write it into injector (or gfx).
4. Trace GA connection to make AGP working.

This is compilable version - start point. Without radeon functions yet.

EDITED 17.04.2008
There are all needed sources
IOGraphics by Apple. My version contains all codes from latest and old version with my comments who from where. Some codes needed only for PowerPC. Later I'll exlude its.
RadeonFB by Joblo. My old corrections for RadeonIGP. But the project is wrong at all. It is useful as template "How to correct IOGraphics to work with Radeon".
RadeonXF. Linux driver for R200-R400 based on RadeonFB . Many useful corrections to the project.
RadeonHD. Linux driver for R500-R600. It is very different driver so I don't know yet what is better: write one driver for all (if(R600){}) or make two different projects.
I also know that Linux driver for RS300 chipset is wrong cause I make my own AGPGart and compare settings. I have AMD documents about RS630 but have no informations about RS300, RS400, RS480 that is requested.

EDITED 26.05.2008
Joined project without kernel panic. Needed more corrections.
http://forum.insanelymac.com/index.php?sho...96664&st=45

For testing purpose Dong (very thanks!) create a nice driver RadeonPCI and utility RadeonDump
To use type in terminal
sudo kextload -v RadeonPCI.kext
./RadeonDump -r 0,1000 -- may be I ask you for other range
./RadeonDump -i


EDITED 21.07.2008
The new project based on OpenAti project http://openati.sf.net.
Now the driver is constructed as ATIDNRV and work together with any IONDRVSupport version.
So if it doesn't work then reboot in safe mode and delete the kext. I need your dmesg or system.log.
The significant part of codes rewritten according to RadeonXF sources and intended for any Radeon from R200 to R700(?). Needs testing.
The driver will work with ATILead.kext that inject a name "ATI,ATIPC".
To test install ATILead.kext, correct it's info.plist to your DevID
Install Ati.kext.
Try to boot and report. Try to understand why it doesn't work for you.
Sources of Ati.kext
What to change in ATILead.info.plist at posts #352 and #357.
Hoe to test at post #344

Here is Dong's test version RadeonHD
Also try and report.

At the current state its don't change resolution. It will be next step.

its said that 10.5.3 has ATI Radeon 3650 and 34×0 support.

Thank you for this Slice.
I can't help much reguarding coding since I don't have the knowledge but I'll try to do my possible on other sides as I already did.
I'll talk to the staff members about creating you your own subforum in Xlabs.

Also you can find here the official ATI docs about GPU programming, that ATI finally recently released, if you don't already have it.
http://ati.amd.com/developer/open_gpu_documentation.html

Yes, I got the documents. Without its I can't bring myself to revive the project.

Next step:
I got more sources about Radeon. Now I have correct procedure to read LegacyBIOS while XRadeonFB project deals only with ATOMBIOS.

Two bad rezults:
1. IONDRVSupport compiled from the sources above gives blue screen with ATIRadeonX1600AGP while previous version works!
2. Linux driver is still wrong

Word access to odd address!

This codes is wrong too


Is there anybody point me to good documentation about Legacy Radeon VideoBIOS?

EDIT:
Possible workaround
RADEON_BIOS16(entry) -> RADEON_BIOS8(entry) and other byte access

RADEON_BIOS8(offset + 6) -> RADEON_BIOS8(offset + 1)
I check its with 3 BIOS. Seems to be good

Find differencies in INDRVSupport v1.4.3 and 1.4.4
v1.4.3

v1.4.4 Where kIONDRVPCIInterruptSource = 0
v1.4.3
v1.4.4

Only in 1.4.3

Reseach continue

I think I don't need to rewrite IONDRVFramebuffer as joblo did. The better way is to rewrite IONDRVDevice as separate kext.

EDITED:
as ATINDRV

No any interest?

Hi,
I'm really interested, because the only reason I'm still working on Tiger is that my X800XT isn't working with QE/CI at the moment and I don't have resolution change options

Thanks for trying to make a working kext !!!

AntarcticPL

Hi,

I'm really interested too, this thread is the first thing I go look at when I start Safari.
(But we're not supposed to ask things in the X Labs, so I jus wait around)

QE/CI is the only thing I'm missing right now.

Thanks for making the effort for us!

Justin

Good, my work will be not hollow. I want to speak with programmers.

I made changes into zero project to combine best features from IONDRV v1.4.3, 1.4.4 and 1.4.5
My version have a number 1.4.42 to differ from Apple's.
For me it works.
One output from syslog

may be useful if black or blue screen is achieved.
Thinking about more outputs to understand mechanics.

Good job you done!
Actually I'm looking at these apple and linux source codes too because personally I need a working framebuffer driver with resolution change ability for my x1400 mobility. I'll take a look at your code immediately.
But what you are doing now seems not related to 3D acceleration, which means no support for QE/CI. AFAIK, ATINDRV.kext is only a framebuffer driver. Therefore, many ppl may will be disappointed by this.

3D acceleration is supported on almost all models from and later to ATI 9550 so it's not the main problem.
On its side, the framebuffer is not working on all models prior to X1000, partially working on almost all models between X1000 and X2000.
So this is the priority for the moment, also, dealing with 3D acceleration without having a working framebuffer wouldn't be the best way to go.

@Slice
Maybe you should update files download in the main thread too ?

little off-topic : I'm still searching on my side about X1600 efi and IOreg strings, I was thinking it would be nice to start a kind of "dictionnary thread" where we'd write each string and what we know about it. Users could test and update their findings, hopefully this could allow to dig the knowledge about it.
off-topic 2 : extended desktop on X1600 seems to be impossible simply because the wormy framebuffer (used for X1600 and other R500 powered cards) can only output a LVDS signal on the main head. This seems logical since the only mac having X1600 is the 1st macbook pro, with output 1 used for LVDS flatpanel, and output 2 for external screen, and Xserve with X1300 only has external output.. That would explain why only some rare laptop users (having a LVDS display) managed to get it. Enabling the desktop by itself is not impossible but it always ends on a black screen, confirming the fact it's probably an output "format" problem. The second head seems to be "switchable" LVDS, CRT, DVI, TV...

All this leads me to think about the fact that other framebuffers like the one for X1900 cards (which is an external card) may support all kinds of outputs on both channels. X1600 and X1900 can't be so different, I doubt ATI restarted from scratch the way its cards work on every model. There are big chances that this lowlevel stuff is common to all R500 series if not all X1000. So what could really differ between those 2 framebuffers beside some "details" ? My idea is to binary patch the sphyrna framebuffer to make it compatible with X1600. However I'm aware this is only naive theory, but if you have the documents, maybe you know those differencies and maybe it's only some memory adresses to patch here and there.

OK! I updated the topic.
About 3D acceleration. It is performed by ATIRadeonXXXX.kext that is not available in sources. Is it good enogh? I found no!

Calculation of mc_fb_location (physical address of Framebuffer) different for IGP, for OpenFirmware and for all other Radeons. But ATIRadeonXXXX.kext uses only OF variant . Can I patch it? Yes.
Do I know exactly what to do? No! I made a test version of ATIRadeon8500 for IGP that works more or less, while original one - never.
This calculation performed twice. In ATIRadeon.kext and in IONDRVFramebuffer.kext so during debugging we can find best settings.
ATIRadeonXXXX doesn't perform screen output. It works through Framebuffer. For good 3D we need good Framebuffer. For example CallistoFB doesn't work in AGP mode.
Yes, I shall return to QE problem having good framebuffer.

Registry keys.
IONDRV uses such keys (getProperty):

That's all. Other settings found in ioreg are needed for other drivers.

About RadeonHD project. http://wiki.x.org/wiki/radeonhd

It is Linux!

Yeah, I'm studying how to put radeonHD stuff in IONDRVSupport. Even in radeonHD, Rv5XX and Rv6XX are treated slightly different because of one offset in register address for them and/or something else I don't know yet.

Glad to see a developer!

I'll be absent up to 21.04.2008. Speak with you later.

Hiya

Just wanted to mention that I am also very interested in this project! I also still have: Quartz Extreme: Not Supported

Do I understand correctly that the aim of this project is to create a frame buffer that would allow for QI?

I am using Leopard 10.5.1 with a ATI Radeon X800PRO (AGP), and Callisto 008 has given me resolution and refresh rate changes. Further I've loaded ATIRadeon9700 drivers, AGPGArt & IONDRVSupport.

I am not a developer, but I can do testing, let me know if this would be useful with the above for this project.

Cheers,

N.M.

It would be best framebuffer.

You give me useful reports so welcome!

Great, go for it! |-)



Let me know what I can test, and please help me a bit with the test plan; meaning which kexts to load with it, which versions, etc.

Looking forward!

What is the flag

Any ideas?

Host means AGP controller???

kIOFBHostAccessFlagsKey is defined as "IOFBHostAccessFlags" in IOGraphicsTypes.h. A simple google did not find any registry dump contains this flag.

May be this flag is reserved by Apple for a future. If so we can use it for our purpose.

Now I am ready to join projects. But some questions are still unresolved and I want to have advices what to do.
1. My RadeonIGP have shared video memory located at physical address=0x38000000. But IONDRVFramebuffer works with address=0xd0000000. Internal Radeon readdressing? How it works?
2. Radeon Register
MPP_TB_CONFIG = 0x134
used only for save and restore. Its function?
3. How many differences between R400, R500 and R600 family?

I did a google and found this:
(II) RADEONHD(0): Mapped IO at 0x2b01de1c6000 (size 0x00010000)
(==) RADEONHD(0): Write-combining range (0xf0000000,0x8000000)
(II) RADEONHD(0): PCI FB Address (BAR) is at 0xF0000000 while card Internal
Address is 0x38000000
(II) RADEONHD(0): Mapped FB at 0x2b01de861000 (size 0x08000000)
Looks like PCI Address VS. GPU Address, but I have no idea about their detailed roles as both are Physical addresses in the eye of the device driver. Maybe DMA GART readdressing is involved in the PCI Address scheme.


Also by google, I found this:
> 1) If MEM_CNTL and CONFIG_MEMSIZE are not re-initialised to their power-up
> value, a BIOS bug ends up corrupting the chip's memory interface.
>
> 2) If the misnamed MPP_TB_CONFIG register is not set properly, a bug in
> the chip causes it to return zeroes for read-outs of its PCI ROM.
>
> Both issues have been seen using various Radeon cores, including R200,
> RV200, etc.

> > > MPP_TB_CONFIG was for an issue on the Radeon 7500
> > > (RV200). Unfortunately, I can't elaborate too much on what exactly it
> > > does, because it's a fix we got from ATI without much detail. The
> > > problem it fixed, though, is that without the MPP_TB_CONFIG change the
> > > BIOS ROM can't be read after the BIOS has been run.

ie., MPP_TB_CONFIG must be handled in case the card BIOS is run multiple times. Reboot is an example. Otherwise, only zero is returned when read the BIOS ROM for the second time.


Can't say much about this. The difference between R500 and R600 should be less when compared with R400 since at least R500 and R600 are dealt by the same linux driver although in many cases parallel functions are used to treat R500 and R600 differently.

Thank you, Dong!

I took your information.
About differencies. I shall make driver as universal. Be ready to correct it to new chips.

I begin to write final project. It takes me several days because thousand strings must be rewriten.
I can't divide project to ATIXNDRV and IONDRVFramebuffer. More easy to me make IORadeonSupport and some injector (ATILead) to customize some registry values.

By looking at codes in radeonHD driver's utility folder and ATILead, I wrote a small utility for Mac to dump Radeon card BIOS ROM and IO register values in user space. I provide it here in case you don't have such a tool.

To use it, just open a terminal and type:
sudo kextload -t RadeonPCI.kext //place a kernel side thing matched to "ATY*" or "display" and response to below dump cmd
./RadeonDump -d //dump BIOS ROM to a file named as: devID.subVenID.subSysID.vga.rom
./RadeonDump -r 0x308,0x338 //dump to terminal IO register values within 0x308,0x338 or else you want

The execute files are compiled on my leopard 10.5.2. You may want to recompile them from source code.

compiled for leopard 10.5.2:Click to view attachment
compiled for tiger 10.4.8:Click to view attachment
source code:Click to view attachment

For tiger, you still need edit Info.plist to change OSBundlerequirement to your version number, ie. 8.8.1 --> 8.6.1 if you are running 10.4.6.

Very well!
May be you create new topic about RadeonPCI in the subforum?

I try to recompile it to Tiger but unsuccessful because it uses some Leo functions

I am also unsuccessful with lspci and don't know why.
Can you give me your IOUserClient class description?

One useful link about Radeon200M
http://dri.freedesktop.org/wiki/Radeon200M...goryHardware%29

No specific leopard functions are used, simply need to change the build rule to use 10.4u.sdk. The post has been updated with a compiled version for tiger, which I've tested with kextload on my tiger 10.4.8 without problem. RadeonDump included is also working. If recompile it, other archs other than i386 need to be removed from cmd parameter list.
One possible problem is that I just choose the IODeviceMemory who has a size of 0x10000 as IO register memory area, but I'm not sure for this.

I check it with my hackintosh N1. OSX 10.4.9. Works fine even with nVidia!!!

But not with Radeon registers on nVidia

It still not work in 10.4.6....
Same result as I previously have with lspi


I made the joined project IORadeonSupport but with numerous mistakes. The last one

I understand that it is subroutine description error. But how can I find which of hundreds?

So the BIOS of video card is loaded to the same physical address 0xc0000 no matter ati or nvidia.

Looks like nVidia IO register area is not with a size of 0x10000, but with 0x20000.

I did a google on this. It may be caused by no support for UUID cmd section in mach-o execute file for 10.4.6. Add an -no_uuid link option may solve it.

Can you find any other error information other than this?Well, I found your posts on x86dev.org about lspci.
Here I attach a new kext with the -no_uuid link option and select IO area upon the size is between 0x10000 and 0x20000. Click to view attachment
You may try it with both of your hackingtoshs.

Since you had the same problem loading the userclient related kexts. Now I'm thinking why don't you upgrade to 10.4.8 or is 10.4.6 required for your specific hardware?

We have no purpose to read nVidia registers. We work around ATI.

Same problem


Hack 1 at evening (home). Hack 2 at moning and midday (job).

It is really hard question. I tried to install Official ComboUpdate 10.4.8 as with hackintosh 1. All freezes at AppleACPiPlatform.kext no matter what kernel I tried to use. Old kext is not compatible with new kernel. I can't start even with -v -s.
I tried also JaS 10.4.8 PPF1, PPF2, Kalyway 10.4.10, MacDotNub 10.4.10. They are loaded (so kernel+ACPI works?) but stopped at installer. I have no more ideas how to install or upgrade my Hackintosh 2 to new system.

Return to our main problem. Here is a sources of joined project. What I did?
1. Insert Joblo's additions to IONDRVFramebuffer 1442. Only three commands support:
cscGetVideoParameters
cscGetModeTiming
cscGetNextResolution
and procedures to support the commands.
2. Correct Joblo's access to Radeon Registers and VideoBIOS (as in ATILead).
3. Large rewrite of GetConnectorsInfoFromBIOS according to Linux Project XF.
4. Add decsriptions to Radeon registers. Not all yet!
I didn't make IONDRVDevice initialization as Joblo do supposing that ATILead may do it.

Sorry, the sources contain a mistake that I didn't catch yet. May be you can help?

Probably kernel 8.4.1 that I have doesn't support kIOUCStructIStructO used in lspci and RadeonPCI.
But it supports kIOUCScalarIScalarO used in IOGraphicsFamily.
http://lists.apple.com/archives/darwin-dri...c/msg00014.html

EDITED:
Sorry, it is used in IOFramebufferUserClient.cpp so it must works.

EDITED:
Better rezult

But now RadeonDump do nothing...
It tells me about error but when all is OK no any output

Just as the usage said, there is no space between start,end otherwise it will give you this error.
Well, if you like dump one register each time, please download this Click to view attachment to the RadeonPCI folder and compile it by yourself. It add support to usage like: ./RadeonDump 0x100 .

I downloaded your IORadeonSupport source code and finally managed compile it under my 10.5.2. Basically, you have some redefinition problems. What I did is just moving codes back and forth between these files to avoid it. Three files in Radeon folder are removed after these as they seemed no longer needed.

Source after modifing: Click to view attachment
Compiled for tiger kexts: Click to view attachment

First of all, thank you, Dong, very much!
You bring me out of deadend. Now I can successfully compile it.
Strange, but I always need to recompile your kexts to make it loadable for my comp:
"2 unknown cmd field"... as RadeonPCI so IORadeonSupport.
Now RadeonPCI loads fine and present in kextstat.
But RadeonDump doesn't produce output. How can I recompile it? XCode project or makefile?

IORadeonSupport.
As I see you exclude IONDRVLibraries. Rezult

Now I recompile it and begin testing. Wait...

Yes, kernel panic

You are always welcome as this is at least something I can do to support you on this project. At present I have no idea what causes this difference, but good that you can recompile and load it.

RadeonDump.c is a simple c source file, you just need to put it in the RadonPCI folder as it includes a header file there. If you open RadeonDump.c, the first comment tells you how to compile it in a terminal. (a normal c language compile cmd )

I did not remember I excluded IONDRVLibraries.h. When you recompiled, did you include it back? Maybe something else caused the kernel panic.

OK! I really never used command line. I am not from Linux world, I am from MacOS Classic.
With Hackintosh N1 (now) I can't reach nVidia registers. All other is OK


Yes, I include back IONDRVLibraries.cpp and .h and correct global->local #include. The project now compilable and loadable without problems. You'd also may improve IORadeonSupport.info.plist.
1. IOProbeScore must be higher then IONDRVSupport to have these two drivers simultaneously. I set 30000.
2. It is better to set matching

to avoid work with 0x03800000 - second stupid head as in X1600Pro

Next problem - kernel panic. It is easy to trace. I simply insert IOLog()s at every place and look. My last stop at getting MMIO address of Radeon registers. Why? I'll trace provider->getName() and all IODeviceMemories of the provider .
Other problems follows. May be not good EDID found in BIOS or getting from I2C. May be not good I2C at all. We can compare it with Linux.
And huge future problem - correct using of Radeon Registers for different chips...
Kernel panic is a trifle.
But I have 3 days holiday.

When I test with IOGraphics source code, I found all ATI acceleration kexts (as listed in Info.plist) require IONDRVSupport to load. But when I check some online vanilla IOReg dumps, IONDRVSupport seems not loaded while native ATI framebuffer driver is used instead.
I can't figure out how this is achieved.

It seems system check the presense of IONDRVSupport.kext to load accelerator but really other driver is loaded.
I have an observation that even if ATINDRV.kext is not loaded in my system it influence on whole ATI driver behaviour.
I propose that ATINDRV::probe() methods called, made some tunings and return kIOReturnUnsuccessful so the kext is not loaded but change the system .

IOGraphicsFamily from our project works fine but I see no difference with Apple's one. We may take into account that we can rewrite IOAccelerator class Have you ideas what to change in it?

that was my original point-out during study of IONDRVFramebuffer
it's massively using IONDRV device subclass for any hardware related issues

With returning, Ole2!

2 joanplanas
To have QE we need good Framebuffer but Framebuffer is not enough for QE.
I also want to have QE and I work.

if you need help to test will be attentive to the messages.

thanks!

------
HP pavilion dv5098ea
ati radeon xpress 200m
amd turion 64

Current state.
I don't like three thing:
1. Zero project IONDRVFramebuffer 1.4.42 doesn't work with IONDRVDevice while 1.4.3 does.
Result - KP at get MMIO.
2. I rewrite IOBootNDRV class to Radeon procedure.
Result - KP at ret = ndrv->getNextResolution.
It is better to create new class IORadeonNDRV (as ATINDRV). Rewrite all again?
3. I rewrite IONDRVFramebuffer class to include I2C members.
It is better to create new class.

I look at connectorsInfo output - no any sense in the digits. Needed investigations.

I am wrong
IONDRVSupport 1.4.3 doesn't work with IONDRVDevice too. So I see no mistakes in 1.4.42 zero project.
Why RadeonFB project make it?


I need not only testers (I have no alpha version yet). I need advices.

EDITED:
I can't understand yet but previously I can boot with IONDRVDevice
http://forum.insanelymac.com/index.php?sho...91042&st=63

Why not now?
Is there anybody who can successfully boot into gui with ATILead 1.2.0 and without other Radeon drivers?

I really need to use IONDRVDevice because it is provider of ATINDRV class.

Continue developement.

I was fighting with numerous memory allocation errors. Now no more kernel panics.
The driver loaded and give me... black screen. But now I can make dmesg with useful debugging info.
There are plenty of other mistakes needed to resolve.
1. I can't obtain correct EDID either from DDC or BIOS. I manually inject some EDID by ATILead.

2. I got correct connection info from BIOS. I have three output: internal LCD, external CRT and TVOUT. But how to use these info? Probably it is needed to create three nubs of NDRVDevices one for each connections and launch three Framebuffers with own datas.
3. I got not correct resolutions info from EDID. Some simple mistakes.

To correct these mistakes it is needed huge work but not impossible.

To Slice,

Thank you for your hard works.
I hope some days my AGP card (ATI 9600 pro) and mainboard (Asrock 4Dual-VSTA (VIA PT880 chipset))
would work with Leopard and QE/CI.

heng2006

go Slice!!!

YOU ARE THE MAN!!!

according to Wikipedia:

"Some graphics card drivers have historically coped poorly with the EDID, using only its standard timing descriptors rather than its Detailed Timing Descriptors (DTDs). Even in cases where the DTDs were read, the drivers are/were still often limited by the standard timing descriptor limitation that the horizontal/vertical resolutions must be evenly divisible by 8. This means that many graphics cards cannot express the native resolutions of the most common wide screen flat panel displays and liquid crystal display televisions. The number of vertical pixels is calculated from the horizontal resolution and the selected aspect ratio. To be fully expressible, the size of wide screen display must thus be a multiple of 16×9 pixels. For 1366×768 pixel Wide XGA panels the nearest resolution expressible in the EDID standard timing descriptor syntax is 1360×765 pixels. Specifying 1368 pixels as the screen width would yield an unnatural screen height of 769.5 pixels.

Many Wide XGA panels do not advertise their native resolution in the standard timing descriptors, instead offering only a resolution of 1280×768. Some panels advertise a resolution only slightly smaller than the native, such as 1360×765. For these panels to be able to show a pixel perfect image, the EDID data must be ignored by the display driver or the driver must correctly interpret the DTD and be able to resolve resolutions whose size is not divisible by 8."

which means, EDID data may not be enough for correct display resolution recovery, but DTD should be parsed instead.

Thanks for warning. I know