←back to thread

OpenGL 3.1 on Asahi Linux

(asahilinux.org)
512 points simjue | 2 comments | | HN request time: 0s | source
Show context
zamadatix ◴[] No.36213299[source]
From a follow up post on Mastadon https://social.treehouse.systems/@AsahiLinux/110497512340479...:

"Also in this update:

We now have a cpuidle driver, which significantly lowers idle power consumption by enabling deep CPU sleep. You should also get better battery runtime both idle and during sleep, especially on M1 Pro/Max machines.

Thanks to the cpuidle driver, s2idle now works properly, which should fix timekeeping issues causing journald to crash.

Also thanks to the cpuidle driver, CPU boost states are now enabled for single- and low-threaded workloads, noticeably increasing single-core performance.

Thermal throttling is now enabled, which should keep thermals in check on fanless (Air) models. There was never a risk of overheating (as there are hard cutoffs), but the behavior should now more closely match how macOS works, and avoid things getting too toasty on your lap.

Random touchpad instability woes should now finally be gone, thanks to bugfixes in both the M1 (SPI) and M2 (MTP) touchpad drivers.

A bugfix to the audio subsystem that fixes stability issues with the headphone jack codec.

New firmware-based battery charge control, which offers fixed a 75%/80% threshold setting. To use this, you need to update your system firmware to at least version 13.0, which you can do by simply updating your macOS partition to at least that version or newer. This new charge control method also works in sleep mode.

U-Boot now supports the Type A USB ports (and non-TB ports on the iMac), so you can use a keyboard connected to any port to control your bootloader.

And last but not least, this kernel release includes base support for the M2 Pro/Max/Ultra SoCs! We are not enabling installs on these machines yet as we still have some loose ends to tie, but you can expect to see support for this year's new hardware soon."

replies(6): >>36213477 #>>36214241 #>>36215165 #>>36216598 #>>36217305 #>>36226845 #
brohee ◴[] No.36226845[source]
Another follow up on Mastodon is about the ban evasion that HN does specifically for Asahi. https://social.treehouse.systems/@marcan/110503050993279759

I find it pretty tasteless for HN to do that.

replies(2): >>36226946 #>>36234860 #
e40 ◴[] No.36226946[source]
It’s a little hard to understand what is going on. Can you explain? Thanks.
replies(1): >>36227103 #
pyrox ◴[] No.36227103[source]
Asahi Linux's site previously redirected any site with the Referer header set to 'news.ycombinator.com' to google.com. They did this because they believe that Hacker News' community fosters a hostile environment, and thus it was blocked. Setting `rel=noreferrer` on an `a` tag means that the browser will not submit this header, thus meaning this sort of redirect will not occur. Also(as per Marcan's Mastodon account), this rel tag has only been added to asahilinux.org links, not any other links on HN. This means that the moderators of HN believe that the commentary that has in the past been quite misinformative should be allowed, and they are deciding to bypass the block that was put in place by the Asahi team. Now, as per https://social.treehouse.systems/@marcan/110503331622393719 , they're adding an HTML header to anyone who has submitted a post to HN(or has the submit page in their history), as they have no other way of doing anything, as they no longer have the Referer header.
replies(2): >>36227457 #>>36228230 #
101011 ◴[] No.36227457[source]
This raises interesting moral questions that I'm not sure I have an answer to.

For one, I don't believe this place fosters a hostile environment, although it's definitely a place where people love to tell you how you're technically wrong about something.

For another, I would guess that there are a very limited number of websites that would opt into this sort of anti-traffic behavior. Hacker news could certainly choose to honor it, but it also feels within their right to bypass the block.

I wonder if there's a sort of middle ground, where HN alerts the user of the redirect that would have occurred, but still shoots the user to the desired location.

But now you're getting into user flows and begging the question as to why the redirect is there in the first place.

I'd love to know more about the perceived hostility, even reading up on Mastodon left me with more questions than answers.

replies(3): >>36228274 #>>36229753 #>>36234392 #
troad ◴[] No.36229753[source]
> This raises interesting moral questions that I'm not sure I have an answer to.

It's not really all that much of a moral conundrum. Marcan's belief - expressed a number of times on his Mastodon - appears to be that he can prevent other people from discussing something, for the sole reason he doesn't want it discussed. It's not a particularly defensible position in an open society.

In particular, he is upset that people on Hacker News tend to point out that a contributor on Asahi - Lina - appears to be a computer-generated anime alter ego of Marcan himself.

Me, I have absolutely no problem with Marcan having an anime alter ego, but I don't think it's entirely reasonable to expect people to refrain from noticing this and remarking on it. Marcan disagrees, and this is the source of the HN-Marcan rift.

(As I've remarked before, I do mind OSS projects listing fake contributors, for both ethical and legal reasons, but that's another discussion.)

replies(4): >>36230117 #>>36231993 #>>36238060 #>>36256717 #
asmor ◴[] No.36230117[source]
You are misunderstanding. You can discuss your conspiracies anywhere you want, just not on a post pointing to the people that have to deal with the fallout of your unfounded conjecture.

Also assuming there is a "fake contributor", who cares under which names contributions are split up? The work still got one. Also, it is absolutely not your project, you don't get to demand people show their ID when they write code for a project.

replies(1): >>36230365 #
troad ◴[] No.36230365{3}[source]
> Also assuming there is a "fake contributor", who cares under which names contributions are split up? The work still got one. Also, it is absolutely not your project, you don't get to demand people show their ID when they write code for a project.

If I contribute my code to an open source project, then I - as the copyright holder - agree to license my work under an open licence.

If I use an OSS project, I am using other people's copyrighted work under an open licence from them. Without that licence, I have no legal basis on which to use that work.

Only real people can (currently) hold copyright. If person X writes some code, but the licence (incorrectly) attributes the copyright to person Y, and person Y purports to give me an open licence to use that work, then - crucially - I have no license from the actual copyright holder (person X) to use their work.

Until an effective open source license is made, this code is not open source; it is completely proprietary. If person X chooses to sue you for copyright infringement, it is no defence to say that you're using it under a license from person Y, because person Y had no right to give you that licence.

This is a major ethical and legal problem. I would be very wary of the Asahi codebase.

replies(1): >>36230507 #
asmor ◴[] No.36230507{4}[source]
If you wanted to split hairs this thin, you wouldn't use any project with at least one german citizen as contributor, since they can never truly yield all copyright on a work. You'll be fine. Anonymous contributions to free software (or even entire releases done anonymously, e.g. Bitcoin) are not actually uncommon.

As I said, very weird hangup to have, definitely not motivated by other reasons.

replies(2): >>36230983 #>>36232610 #
PrimeMcFly ◴[] No.36232610{5}[source]
What makes ze Germans special?
replies(1): >>36232666 #
asmor ◴[] No.36232666{6}[source]
Right to moral objection.
replies(1): >>36233091 #
PrimeMcFly ◴[] No.36233091{7}[source]
That doesn't explain anything. Can you elaborate?
replies(1): >>36233916 #
1. asmor ◴[] No.36233916{8}[source]
The most commonly cited example is a musician objecting to use of their music during a neo nazi rally. They won that case as the court judged the integrity of the work to be compromised.
replies(1): >>36234094 #
2. PrimeMcFly ◴[] No.36234094[source]
I see. Well, I don't think that would affect code in the same way. If they have already contributed it then it's out in the open, and unless the maintainer was doing something objectionable they wouldn't have a case, and even if they did it would only be enforceable in Germany.