![](https://seccdn.libravatar.org/avatar/30fae5bce90608fb3df5c018c586aea6.jpg?s=120&d=mm&r=g)
The downside of the AtomParser approach (as far as my very limited knowledge lasts) is that the code in the AtomParser is i386 depending, so there is no easy way to run this card on e.g. PPC or any other architecture. (But there are graphic card bioses downloadable from ATI for some cards for the PPC architecture and I heard some other implementations try to run the atombios code with an i386 simulator). LieGrü, strub --- Louise Hoffman <louise.hoffman@gmail.com> schrieb:
The two projects had different goals. Dave and I wanted to play with ATOMBIOS and to take advantage of the existing functionality that is already supported in the radeon driver (2D/3D accel, drm/command process support, etc.). ATOMBIOS is a set of card specific tables and scripts that can be used to program certain functions on the chip. This includes setting modes, routing crtcs, dpms, initializing the chip, etc. ATOMBIOS provides a common API to perform these functions. The x86 bios, the windows driver, fglrx, etc., use these scripts to program the card. This makes it much easier to bring up new asics and program the chips. ATOM allowed Dave and I to get the driver up quickly so we could start to play with things like 2D and 3D, using the command processor, etc. since much of that works unchanged on newer chips. Down the road I'd like to see one code base, but it will take some work and time of course. We'll get there eventually.
Thanks for the explanation =) I didn't really understood what ATOMBIOS was, bit now I just think of it as an API to make driver developers work easier =) -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
__________________________________ Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. www.yahoo.de/clever -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org