Tosh. You would need an OS to use the catalyst drivers -- but you don't necessarily need catalyst to use the chip, and you wouldn't need an OS to directly interface to the chips if you were given their specification (or reverse engineered it) [on this note: do the GPU chips directly implement PCIE, or is there an additional interface chip for this -- I suspect the former, meaning you would simply need a USB to PCIE interfacing chip...] -- which is however highly unlikely since I don't think ATI would publish this sort of data / reverse engineering would be tedious. You would be wasting a lot of time reimplementing what the catalyst drivers already do (although you would only need a small part of the functionality for bitcoin mining) once you had this data as well. In other words it is pointless to do the above, but it is not actually necessary to use an OS.
I didn't say you necessarily need the catalyst driver to utilize the GPUs, but I said it was necessary because writing your own OpenCL implementation for a GPU would make this project go from very, very difficult to
insanely difficult. AMD has a team of about 80 developers working full-time on their Catalyst driver (I am not kidding you).
The open source Radeon HD driver (which is about four years old) just recently was able to run a proof-of-concept OpenCL application:
http://phoronix.com/forums/showthread.php?69064-Using-OpenCL-with-the-radeon-driver-to-print-Bitcoins-is-this-posible#post252304Probably at 1% the speed of the Catalyst driver.
Developing an OpenCL implementation isn't
that hard, developing a
well-performing OpenCL implementation is! Just look at the radeon driver (open source Linux driver for the Radeon HD GPUs). AMD has a man dedicated to work on this full-time, and there are plenty of volunteer developers, and it doesn't support a fraction of the features Catalyst does, and it performs at a fraction of what the Catalyst driver does.
Building a custom GPU motherboard and writing a driver that only achieves 50% the performance of the Catalyst driver is hard and a waste of time (and it wouldn't be able to churn out 800 MH/s in this case).
In other words it is pointless to do the above, but it is not actually necessary to use an OS.
Necessary, no. Necessary if you want a device performing as well as the Catalyst driver without spending 100,000 man hours developing a custom Radeon HD driver with OpenCL capabilites, yes.
I'm telling you man, a GPU driver is
a lot more complex than most people think. It's basically a small operating system running on the GPU: memory manager and process scheduler are both a necessary part of a GPU driver. It's basically a massive serial-to-parallel compiler (translating a series of Direct3D or OpenGL instructions into tens of thousands of threads with instructions the GPU chip can understand and execute in parallel). It's actually quite fascinating. This covers the very basics of a GPU driver:
http://fgiesen.wordpress.com/2011/07/01/a-trip-through-the-graphics-pipeline-2011-part-1/Starting in 2008, AMD released all documentation for some of their GPUs
(1) (yes, that's about 2500 pages of hardware, firmware and software specification), after the open source Linux community had encouraged them to do so because "if we have the specifications some hacker will come around and develop a much better driver than the proprietary one". Today reads 2012, and the open source driver
still isn't really usable for the average gamer (who buys a $200-$800 graphics card and then proceeds to use a driver that only performs at 20% the speed of the Catalyst driver?)