"Radeon Audio", from the perspective of the user, should appear as just another audio driver.
If you select Radeon Audio, AND you have a television connected by HDMI, then the sound output comes from your television speaker(s).
I was pointing out that from a driver-writers perspective, it's a bit different than other AHI drivers.
"Common" ahi drivers might to make a list of available outputs, so the user may choose front jack, rear jack, optical out etc..
Far more common is to already KNOW what those choices are in advance, and the selector is then a static list.
In deference to that, a Radeon audio driver has no "audio output" to offer. it merely provides a path to the television, and the driver
must interrogate the TV to find out what, if any, outputs are available.
If the HDMI cable is not connected, there is no audio (path) to be explored.
If there IS an HDMI monitor/Television connected, then the driver must explore it on startup to figure out what it might be capable of.
I'm not saying it's too difficult. I am just pointing out one of the differences.
If one takes a broader look, the "HDAudio" specification was designed from the ground-up to support having one universal driver. That sounds GREAT, but it also means that the driver must be prepared to interrogate the hardware for every possible scenario, and be ready to deal with whatever it finds (or does not find, as in the first example mentioned). If a driver finds NO audio outputs.. Fail?. Nope. Go down the wire and ask the television what it has.. but what if the television is really just a recording device? You can not poll a device for capabilities if you are pre-recording it's source material.
Now I am beginning to confuse myself. Which may not be a very challenging task.
I declare official "Time Out". Today will be spent walking, talking, shopping, and dining with my lovely wife Kimberly <3. She has much nicer software than my Amiga anyway.
The programming will wait.