Results 1 to 10 of 10

Thread: Lemote's Playing With Loongson Radeon UVD

  1. #1
    Join Date
    Jan 2007
    Posts
    14,628

    Default Lemote's Playing With Loongson Radeon UVD

    Phoronix: Lemote's Playing With Loongson Radeon UVD

    Many Phoronix readers seem to be infatuated by the MIPS-based Loongson systems, while the hardware is hard to find -- and even if you manage to find it in western markets, it's very expensive. For those fond of the Loongson processors and happen to have a Radeon chipset, Lemote is playing around with Radeon UVD video acceleration...

    http://www.phoronix.com/vr.php?view=MTQ1NDk

  2. #2
    Join Date
    Dec 2008
    Posts
    148

    Default

    Seems ironic that somebody would buy a Loongson and then pair it with something that uses proprietary firmware.

  3. #3
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,434

    Default

    Quote Originally Posted by LLStarks View Post
    Seems ironic that somebody would buy a Loongson and then pair it with something that uses proprietary firmware.
    Why ? The Loongson relies heavily on proprietary CPU microcode. You just don't see it because it's in ROM rather than RAM, and either there is no patch CAM (like Intel and AMD CPUs use for microcode updates) or information on it hasn't been published.

    Same idea as putting a piece of black tape over the "ENGINE" light on your car... no see, no problem
    Last edited by bridgman; 09-05-2013 at 06:58 PM.

  4. #4
    Join Date
    Dec 2008
    Posts
    148

    Default

    Why does RMS approve of the Loongson then? /halfsarcasm

  5. #5
    Join Date
    Mar 2009
    Location
    in front of my box :p
    Posts
    782

    Default

    I think RMS is surprisingly "open" towards firmware things. If it happens in the firmware it's ok.
    Though a free firmware would be the icing on the cake. For now it is already a good step in the right direction.
    Generally a porting and testing of Radeon and UVD capabilities to non-x86 structures is generally interesting. As mentioned, the not so overly powerful CPUs would benefit most from an ASIC for decoding videos.

  6. #6

    Default

    Quote Originally Posted by Adarion View Post
    I think RMS is surprisingly "open" towards firmware things. If it happens in the firmware it's ok.
    Though a free firmware would be the icing on the cake. For now it is already a good step in the right direction.
    Generally a porting and testing of Radeon and UVD capabilities to non-x86 structures is generally interesting. As mentioned, the not so overly powerful CPUs would benefit most from an ASIC for decoding videos.
    So does that require Coreboot, or does it require something like making your own CPUs from the OSS licensed SPARC designs?

  7. #7
    Join Date
    Mar 2013
    Posts
    144

    Default

    Quote Originally Posted by Adarion View Post
    I think RMS is surprisingly "open" towards firmware things. If it happens in the firmware it's ok.
    Though a free firmware would be the icing on the cake. For now it is already a good step in the right direction.
    Generally a porting and testing of Radeon and UVD capabilities to non-x86 structures is generally interesting. As mentioned, the not so overly powerful CPUs would benefit most from an ASIC for decoding videos.
    As long as the user can access, modify and run the software, i.e. the "users' freedom" [https://www.gnu.org/philosophy/free-sw.html], RMS will support it.

    Software can be open source but not free if it's never licensed by the author for distribution or even usage of any kind other then looking at the code. Similarly, hardware can be of open design but not free if it requires signing and the master key isn't distributed.

    So, since RMS did make a stance on Tivoisation, Affero and DRMed +/- signed bioses, I wouldn't say he's completely nonchalant about the hardware.

  8. #8
    Join Date
    Jul 2010
    Posts
    449

    Default

    Quote Originally Posted by c117152 View Post
    As long as the user can access, modify and run the software, i.e. the "users' freedom" [https://www.gnu.org/philosophy/free-sw.html], RMS will support it.
    RMS's stance on firmware depends on whether it can be updated/changed. If so, he considers it software, and that it should be free. If not (i.e. the firmware cannot be replaced) then he considers it hardware.

  9. #9
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,434

    Default

    Quote Originally Posted by archibald View Post
    RMS's stance on firmware depends on whether it can be updated/changed. If so, he considers it software, and that it should be free. If not (i.e. the firmware cannot be replaced) then he considers it hardware.
    AFAIK it's a bit more nuanced than that -- for example if we had room in the VBIOS ROM image to store the microcode images so we could load them into the GPU during BIOS start-up rather than driver start-up that would be considered "better". In fairness, that may be because it moves the microcode images from an "otherwise free" driver to an "already non-free" VBIOS.

    The microcode would still be upgradeable via VBIOS flash, but the hardware would be considered to be open-source-friendly by most people simply because the *driver* didn't have to hold its nose and load the microcode at start-up any more.

    I do understand (and agree with) RMS's underlying position -- it's the real-world interpretation and decision-making based on that (necessarily) abstract position that I sometimes disagree with.

  10. #10
    Join Date
    May 2009
    Posts
    20

    Default

    Quote Originally Posted by bridgman View Post
    AFAIK it's a bit more nuanced than that -- for example if we had room in the VBIOS ROM image to store the microcode images so we could load them into the GPU during BIOS start-up rather than driver start-up that would be considered "better".
    Why not make the non-free blobs, the VBIOS images and microcode images, free?
    Last edited by rah_; 09-07-2013 at 07:39 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •