Announcement

Collapse
No announcement yet.

New Patches Wire Up ACPI Support For RISC-V On Linux

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    New Patches Wire Up ACPI Support For RISC-V On Linux

    Phoronix: New Patches Wire Up ACPI Support For RISC-V On Linux

    A set of 24 Linux kernel patches today wire up the basic ACPI infrastructure support for the RISC-V processor architecture...

    New Patches Wire Up ACPI Support For RISC-V On Linux - Phoronix
    https://www.phoronix.com/news/ACPI-RISC-V-Linux-Patches
    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
    Tags: None
  • #2
    Why are we bringing microsoft's windows bullshit to RISC-V, a platform that windows isn't even close to running on?

    Device tree, people. Device tree.
    • Likes 2

    Comment

    • #3
      Originally posted by Developer12 View Post
      Why are we bringing microsoft's windows bullshit to RISC-V, a platform that windows isn't even close to running on?

      Device tree, people. Device tree.
      Adding mine Signed-off-by...
      • Likes 1

      Comment

      • #4
        I assume ACPI is being used to simplify configuration and addition of new boards / cpus to the kernel.
        • Likes 1

        Comment

        • #5
          Originally posted by Developer12 View Post
          Why are we bringing microsoft's windows bullshit to RISC-V, a platform that windows isn't even close to running on?

          Device tree, people. Device tree.
          Part of the UEFI effort. Stronger platform standardization.
          • Likes 1

          Comment

          • #6
            Yeah, better platform support and such. Still, I wish the code would printk every time it runs 'Your board is stupid' or something like this. <.<
            • Likes 1

            Comment

            • #7
              Originally posted by ayumu View Post

              Part of the UEFI effort. Stronger platform standardization.
              UEFI does not care about Device Tree or ACPI, especially here where UEFI effort means u-boot starting the .efi binaries and ideally providing the device tree to the kernel if the kernel has no newer device tree on hand.
              • Likes 2

              Comment

              • #8
                Originally posted by Alexmitter View Post

                UEFI does not care about Device Tree or ACPI, especially here where UEFI effort means u-boot starting the .efi binaries and ideally providing the device tree to the kernel if the kernel has no newer device tree on hand.
                Maybe it is not a requirement, but they seem to be pushing it pretty hard: https://uefi.org/faq-page

                I hope RISC-V specs make it so that if there's ACPI tables and such, they are generated from device tree, and that device tree is a requisite, but I have not been watching the related working groups for the specs closely.
                • Likes 1

                Comment

                • #9
                  Cool, hell is freezing over. Reduced Instruction set, but Complex boot and firmware configuration. Yay!
                  • Likes 2

                  Comment

                  • #10
                    Originally posted by rene View Post
                    Cool, hell is freezing over. Reduced Instruction set, but Complex boot and firmware configuration. Yay!
                    Yeah... ACPI is a nightmare to implement when you develop OS. Why porting such a massive pile of sht to RISC-V???

                    Comment

                    Previous template Next
                    Working...
                    X