Announcement

Collapse
No announcement yet.

XAA In X.Org Has Finally Met Its Executioner

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

  • gilboa
    replied
    Originally posted by Ex-Cyber View Post
    What you missed is that the cirrus driver is not actually being dropped, it will just be temporarily broken in git by the removal of XAA, which wouldn't have accelerated much anyway on any system released in the past ~4 years.
    1. Don't be rude. Period.
    2. There's no doubt that cirrus and old, and should be have taken behind the shed and shot; but as long as qxl has yet to reach the same stability (as cirrus), I can only hope the X-devs will take the time to maintain with some-type-of-working-acceleration.

    Are we done?

    Leave a comment:


  • curaga
    replied
    MGA should be included in the list. The only driver version supporting EXA is the experimental 1.9, and it works worse than the stable, XAA-using one.

    Leave a comment:


  • Ex-Cyber
    replied
    Originally posted by curaga View Post
    No such system will run a compositing environment. We are talking mostly laptops with integrated neomagic, trident, whatever.

    Operations as basic as moving a window will become slow, no? Oh, and the loved behavior of MS Windows too will appear, where moving a window will peak one core.
    I'd be surprised if moving a window isn't already slow on this hardware. When most of it came out, it was still standard practice to only show an outline when moving a window.

    Leave a comment:


  • curaga
    replied
    Originally posted by daniels View Post
    In practical terms, you're not getting acceleration anyway. XaaNoOffscreenPixmaps has been the default since 2008, which means that XAA will only accelerate operations where the only drawable referenced is the screen pixmap. For GTK and Qt, this means nothing ever, since they do all their rendering to an offscreen pixmap first, and then copy that to the screen pixmap. If you're running in a composited environment -- it's all offscreen. So, about the only effect this really has is making xtank and Motif apps in a non-composited environment slower.
    No such system will run a compositing environment. We are talking mostly laptops with integrated neomagic, trident, whatever.

    Operations as basic as moving a window will become slow, no? Oh, and the loved behavior of MS Windows too will appear, where moving a window will peak one core.

    Leave a comment:


  • Ex-Cyber
    replied
    Originally posted by gilboa View Post
    I assume that I misread something.
    Feel free to explain what I missed (as opposed to mocking my failing intelligence).
    What you missed is that the cirrus driver is not actually being dropped, it will just be temporarily broken in git by the removal of XAA, which wouldn't have accelerated much anyway on any system released in the past ~4 years.

    Leave a comment:


  • gilboa
    replied
    I assume that I misread something.
    Feel free to explain what I missed (as opposed to mocking my failing intelligence).

    - Gilboa

    Leave a comment:


  • airlied
    replied
    Originally posted by gilboa View Post
    Gaah.
    Hopefully someone will notice that besides QXL (that's still being activally developed) cirrus is the default virtualized graphics card in qemu / qemu-kvm.
    I'd hate to move all my non-QXL VM's to vesa because of this...

    - Gilboa
    I hope someone will learn how to read.

    Dave.

    Leave a comment:


  • gilboa
    replied
    Gaah.
    Hopefully someone will notice that besides QXL (that's still being activally developed) cirrus is the default virtualized graphics card in qemu / qemu-kvm.
    I'd hate to move all my non-QXL VM's to vesa because of this...

    - Gilboa

    Leave a comment:


  • daniels
    replied
    Originally posted by curaga View Post
    In other words, any last shreds of acceleration are being removed for any cards in that list. Way to make even more hardware unusable.
    In practical terms, you're not getting acceleration anyway. XaaNoOffscreenPixmaps has been the default since 2008, which means that XAA will only accelerate operations where the only drawable referenced is the screen pixmap. For GTK and Qt, this means nothing ever, since they do all their rendering to an offscreen pixmap first, and then copy that to the screen pixmap. If you're running in a composited environment -- it's all offscreen. So, about the only effect this really has is making xtank and Motif apps in a non-composited environment slower.

    Leave a comment:


  • agd5f
    replied
    Originally posted by DeepDayze View Post
    Agreed, there's perfectly good old laptops and desktops that still function...maybe there needs to be a xserver-legacy-1.11 branch with someone who could step forward to maintain the older X server along with the classic drivers. If enough people say something maybe the X developers can look into what's doable
    Anyone that wants to can check out older xservers from git and use them. However, I suspect most people won't notice much of a difference since XAA really hasn't accelerated much for the last 4 years since XAA offscreen pixmap support has been broken and disabled. Note that this only removes XAA support, not the drivers themselves.


    Originally posted by DeepDayze View Post
    Also what about the Radeon 7500-9000 series that use the R100~R200 drivers? I have 2 thinkpads that use these graphics chips and I'd like to keep using them with Linux
    All radeons are still fully supported (EXA, KMS, DRI2, etc.). This basically only affects hw that pre-dates the original radeon.

    Leave a comment:

Working...
X