Announcement

Collapse
No announcement yet.

RadeonHD Driver To Use AtomBIOS

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by bridgman View Post
    The problem with having two different drivers is that you have to do all the acceleration work in the atombios-based driver because you CAN'T SEE THE SCREEN on the other driver 'cause the modesetting code isn't there yet

    Nobody is particularly fond of the idea of doing all the development work in one driver then porting it across to the other driver... over and over again.
    I see the point, thanks for clearing that up

    Comment


    • #17
      they will begin focusing on open-source 3D support for the Radeon HD 4800 series
      Maybe it's some sort of paranoia, but this sounds like "let's skip the R6xx family".

      But it's just paranoia right?
      It would be stupid.

      Comment


      • #18
        It only matters if you own an R6XX product.

        (I do).

        Comment


        • #19
          No plans to skip the 6xx family. I have one in my home PC, there's no damn way we're skipping it

          The issue is that we have sample code for 7xx that actually works, while we're still having problems with the 6xx sample code (it seems to have been broken on 6xx in the process of making it work on 7xx). Starting with code that works (even if it's in the wrong environment and has to be totally rewritten for X/DRI) is "highly attractive".

          6xx and 7xx are pretty close from a driver POV, so rather than getting things working on 6xx this week and same thing on 7xx next week we might go the other way. On the other hand, now that we have sample code working on 7xx we may suddenly figure out why it doesn't work on 6xx.

          Either way, we plan to do 6xx and 7xx in parallel; trying to design code that will work on both.
          Last edited by bridgman; 07-04-2008, 08:43 PM.

          Comment


          • #20
            So kernel modesetting will also use atombios, right?

            Comment


            • #21
              Originally posted by c0un7d0wn View Post
              So kernel modesetting will also use atombios, right?
              That's the way it's looking today. Dave Airlie has been cleaning up the parser to go into the kernel, and Ben H has been working on fixing the big-endian issues. There was a rumour that one of our driver devs had already fixed the big-endian support but it turned out the fixes were for the pre-Atom BIOS instead.

              <deleted the comments about the new AtomBIOS parser we discovered internally 'cause it just confuses things >
              Last edited by bridgman; 07-04-2008, 09:11 PM.

              Comment


              • #22
                Awesome. So there are two drivers for ati hardware and now it turns out there are also two atombios parsers. If we combine them we can have 4 drivers that does the same thing.

                Actually forgot about kms, so that makes, what, 6?

                Comment


                • #23
                  Originally posted by c0un7d0wn View Post
                  Actually forgot about kms, so that makes, what, 6?
                  You forgot about the xf86-video-Avivo driver too
                  Michael Larabel
                  http://www.michaellarabel.com/

                  Comment


                  • #24
                    Ah, Operation "Extreme Redundancy" is carrying on!

                    Comment


                    • #25
                      Hey, there used to be four drivers, now there are only two-ish :

                      http://www.phoronix.com/forums/showthread.php?t=7032

                      Seriously, the X community is going through some very cool times right now. There are a lot of good ideas competing for attention and developer time, and in most cases you get some forking while the pros and cons of each approach are understood, then everyone comes together on a single approach after a while.

                      That said, there are a lot of different worlds co-existing in X right now and both drivers have attributes which are useful to some users. The challenge is to get everyone to agree on what the good and bad bits are.

                      Kernel modesetting will make things seem complicated for a while, but the benefits are going to be significant, particularly the potential for fixing suspend/resume once and for all, or at least making sure the problem is not with the graphics drivers.

                      Finally, you need to look at both the atombios and "quick & dirty 2d" radeonhd branches together if you want to get the whole picture. If anyone feels like testing the "quick & dirty 2d" branch on a 5xx or 690 it should have full EXA acceleration, textured video Xv, and 2d/3d coexistence from radeon, plus the driver abstraction and modestting code from radeonhd, plus a bunch of other recent changes to make all the bits fit together nicely.
                      Last edited by bridgman; 07-04-2008, 09:46 PM.

                      Comment


                      • #26
                        Maybe slightly off topic, but I'm a 3D designer with a strong interest in both Linux and FireGL products, so I was wondering...
                        With these opensource drivers, will there still be a difference between the FireGL and their Radeon counterparts and will that difference be forced upon the open source drivers through AtomBIOS? (Like the way the Windows driver decides what features are to be enabled on a specific adapter, as can be observed from the many succesfull hacks).

                        Comment


                        • #27
                          Originally posted by bridgman View Post
                          That's the way it's looking today. Dave Airlie has been cleaning up the parser to go into the kernel, and Ben H has been working on fixing the big-endian issues. There was a rumour that one of our driver devs had already fixed the big-endian support but it turned out the fixes were for the pre-Atom BIOS instead.
                          Hello everyone. I have a very brief question for brigman: will kernel modesetting also be available on r300?
                          9800pro owner here :-)

                          Comment


                          • #28
                            Originally posted by Kern3lP4nic View Post
                            Hello everyone. I have a very brief question for brigman: will kernel modesetting also be available on r300?
                            9800pro owner here :-)
                            afaik kms can be enabled on any card, it probably will eventually come

                            Comment


                            • #29
                              Originally posted by bridgman View Post
                              One of the differences betwee the open source world and regular commercial development is that where there are strongly held differences you often get a code fork rather than everyone stopping work or one person making an arbitrary decision -- it's not the fastest way to a solution but it's not necessarily all that bad either.
                              I think there have been a couple of these cases. Probably the most famous is Beryl/Compiz

                              Sorry, I forgot about XFree86/Xorg

                              And Rhythmbox/netRhythmbox, that like Beryl/Compiz merged again.

                              Comment


                              • #30
                                Originally posted by StefanHamminga View Post
                                With these opensource drivers, will there still be a difference between the FireGL and their Radeon counterparts and will that difference be forced upon the open source drivers through AtomBIOS? (Like the way the Windows driver decides what features are to be enabled on a specific adapter, as can be observed from the many succesfull hacks).
                                It varies from one generation to the next, but AtomBIOS doesn't force anything -- it just identifies the card as a FireGL product and lets the driver decide what to do. There are other mechanisms we use to force different behaviour -- and when we don't use them, the cards do occasionally get hacked.

                                AtomBIOS commands only cover initialization and modesetting. All the rest -- including 2d, 3d and video acceleration -- are done via the on-chip command processor (cp) or by poking the same registers used by the command processor. I guess at a very abstract level you could say that AtomBIOS does for display & modesetting what cp does for acceleration -- it provides well-tested programming sequences which "just work" for most situations and can be bypassed where necessary.

                                On the 5xx parts I don't believe there will be any behavioural difference between Radeon and FireGL products with the open source driver. Not sure yet about 6xx and up yet.
                                Last edited by bridgman; 07-05-2008, 12:16 PM.

                                Comment

                                Working...
                                X