Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

75% Positive

Analyzed from 1639 words in the discussion.

Trending Topics

#apple#linux#code#llm#llms#hardware#driver#asahi#models#stuff

Discussion (53 Comments)Read Original on HackerNews

MoltenMonsterabout 1 hour ago
https://www.reddit.com/r/AsahiLinux/comments/1whecn1/comment...

> The author was banned from Asahi Linux for hiding his extensive use of LLMs from us in another attempted contribution, and (more importantly) for concealing that he is a former Apple engineer with direct contacts to the people involved in Apple Silicon development. Make of this what you will.

cromka22 minutes ago
I find it extremely ironic that big corp openly steals IP en masse to build their models but hackers are still concerned about using same models for their reverse engineering work.

I think at this point the hacking community needs to grow some balls.

drnick19 minutes ago
If Apple open sourced its drivers this issue wouldn't exist. AI at last gives the "community" a chance to use the hardware they bought the way they want. It's unreasonable to expect anybody to code this kind of stuff "by hand" when automated tools exist.
SXX44 minutes ago
I certainly dont care about hiding LLM contributions and all crazy anti-LLM policies, but I really hope author can share process completely so this can be reproduced by someone not working for Apple.
alightsoul26 minutes ago
Even if this is the case, this is still a valuable contribution to learn upon.
MBCook10 minutes ago
It’s taint. Anyone who looks at it can’t work on a real open source driver because they will have had access to information they’re not supposed to.

It won’t be clean room like the stuff Alyssa did.

alightsoul6 minutes ago
Can't this be used to make a clean room implementation? Have someone write a spec then someone else who is unrelated, implement it from scratch?
theoreticalmal6 minutes ago
That’s the most abstract and esoteric argument I’ve ever heard I think
thrwy19940314about 1 hour ago
All this work is tainted since the poster is ex-Apple[1]. There is no way Linux will take that code, since people from Apple also contribute to Linux and this creates a major conflict.

There's also ongoing issues around Codex for this sort of thing, given Apple is suing OpenAI over stolen trade secrets[2]. And nobody knows whether training data in other models is similarly tainted.

[1]: https://codyho.dev/documents/cody_ho_resume.pdf

[2]: https://www.theguardian.com/technology/2026/jul/10/apple-sue...

IgorPartola42 minutes ago
Now that this work is done and out in the open what in theory would prevent the next generation of LLMs from ingesting it and eventually a non-Apple employee creating yet another driver “from scratch” but with the knowledge of how the hardware works acquired from an LLM or with the help of one?

Basically, aren’t we facing a situation where LLM-assisted knowledge laundering is becoming a thing?

rjsw22 minutes ago
Some arguments in the Apple vs OpenAI case look like they could lead to a decision on whether an LLM can wash away copyright or not.
iAMkenough29 minutes ago
Yes, as well as accountability laundering. Technofascists are loving it.

Nobody has been held accountable for AI selecting a grade school as a bombing target on the first day of America and Israel’s strikes on Iran. 100+ school girls killed, and no accountability.

ADevWithAnIdea38 minutes ago
Linking to another HN comment: https://news.ycombinator.com/item?id=49719480
nine_k42 minutes ago
There were and are many important pieces of Linux kernel that live out of tree; ZFS is a big example.

The problem with this driver is not licensing or code quality; I assume it's under a threat of receiving C&D letter, or maybe also a legal suit for breaking some NDA.

cromka18 minutes ago
> important pieces of Linux kernel that live out of tree; ZFS is a big example.

Including the proprietary GPU drivers. If this MacBook driver end up out of tree, so be it.

porphyra43 minutes ago
Very sad. I really want to get Linux on newer Apple chips working flawlessly but I can understand the legal minefield about this particular work.
cromka17 minutes ago
Nobody does. We're only about to start settling it in courts, likely the supreme ones.
porphyra8 minutes ago
I meant I can understand the fact that a legal minefield exists.

I didn't mean that I understand the actual intricacies of the legal situation.

Sorry for my confusing wording.

ndiddyabout 2 hours ago
It's extremely impressive that they were able to make a working driver so quickly. I think this is one of the best use cases for LLMs. You don't need someone to spend years reverse engineering undocumented hardware anymore. It will interesting to see how good the driver the LLMs came up with is, and whether it can be upstreamed into the Linux kernel.
MBCook9 minutes ago
I’m sure it’s really easy when you can get help from the people who made the chip or write the Apple drivers.
ivanjermakovabout 1 hour ago
Might be one of the only use cases where LLMs are necessary to succeed. Can't imagine the pain of reverse engineering a technology of this scale and "secrecy".
ADevWithAnIdeaabout 1 hour ago
Traditional hardware RE centers around heroics by a small number of very smart people, see: marcan, Alyssa Rosenzweig, Asahi Lina, etc. What they did is insanely impressive, and given how hard it was with LLMs I'm sure I would not personally be able to do this work without LLMs. That said, I'm looking forward to a world where the staring at hexdumps and traces can be delegated to LLMs and talented humans can spend their time building as opposed to head banging.
ndiddy25 minutes ago
Yeah I think it's a shame how much time and effort gets put into understanding things simply because other people want to keep them proprietary.
y1n0about 1 hour ago
The problem I’m finding, at least with today’s models, is that it produces disposable software. It’s not good at making well-architected, durable software. Stuff that could be maintained and bug-fixed.

I mean you can get good stuff out of it if you know what you are doing and guide it, but if you just say “here’s a regression suite. Write an implementation that passes” you will get something that works for a while but ages quickly and will need to be thrown away.

teaearlgraycoldabout 1 hour ago
With today’s technology I’d still want a GPU driver developer guiding the LLM rather than some rando who is out of their element. But cutting down the exploration cycle time and giving the developer massive parallelism (have 10x agents exploring different hypotheses or features) is the real win. We don’t need to skip all the way to slop just to squeak out a little more effort savings.
porphyraabout 2 hours ago
This is super great. The biggest pain point of Asahi Linux is how it doesn't have GPU acceleration on M3 and newer, especially now that M6 is out!

However, Asahi Linux has a strictly no-AI policy [1]. So this great work can't be upstreamed. I expect to see a bunch of AI-assisted forks that get things working smoothly on newer hardware to dominate as most people just care about getting stuff working, while only a handful of purists stick to the non-AI version running on ancient hardware.

[1] https://asahilinux.org/llm-policy/

ADevWithAnIdeaabout 2 hours ago
:) I think we have a surprise in store here. Asahi don't have a monopoly over Linux for Apple Silicon, and upstream Linux absolutely does *NOT* ban LLMs.
doctorpangloss44 minutes ago
i install proprietary modules for nvidia all the time, i'm not going to care if i have to do it for something else that i own
zamadatixabout 2 hours ago
Asahi's long term goal is to get everything possible merged into the (actually) upstream projects anyways so any distro can just work. It'd be nice to see that continue rather than have forks on forks for the sake of singular differences (and it looks like proper upstreaming is what they are going after per the Remaining Work section).
smith7018about 2 hours ago
I imagine either they or others can take their discoveries and write a real driver now, though. The hard part was always the reversing the black box system.
Agingcoderabout 2 hours ago
Maybe I’m getting really old, and I know we live in changing times but the fact this works at all is insane, as in black magic insane.

I assume I’ll get used to it, but my mental model of what’s possible hasn’t been fully rewired yet.

ADevWithAnIdeaabout 2 hours ago
I still can't quite believe it either!
AKSF_Ackermannabout 1 hour ago
I am not by any means a copyright lawyer, so can anyone enlighten me on if it is a good idea for upstream projects to accept such kind of code from an ex-Apple employee, especially since Apple is currently suing OpenAI.
ADevWithAnIdeaabout 1 hour ago
Great observation, two things:

- During my time at Apple I never saw any of the macOS source code, at all, even for userspace components. I had not even heard of things like SPTM.

- I have not worked there since June 2025

I don't believe that there's any risk due to my former Apple employment. As another example, WINE does not ban all former Microsoft employees, they just ban anyone who has ever looked at the Windows source code. If I felt there was even a chance that my employment at Apple may have exposed me to relevant internal secrets, I would refrain from contributing to community projects.

throw123456789116 minutes ago
Have you consulted this with a lawyer, or is it what you simply think/believe.
cromka10 minutes ago
I guess it's none of our business.
SXX41 minutes ago
To the developer: it doesnt matter whatever you can upstream it or not. Just share the code and documentation of how this process can be reproduced.

There plenty of us not working at Apple who can reuse the same approach for M5 and next generations of hardware.

ADevWithAnIdea39 minutes ago
For the kernel driver it's literally just: run the hypervisor, wait for the kick, save the UAT state, replay the whole thing, make sure the output pages change, then just follow the pointer to initdata until you've built the whole tree from scratch. LLM handles the rest.
SXX24 minutes ago
Thanks for the post and answering here, but for someone to follow in your steps there really need to be more information: how did you handle physical hardware? Did it got stuck / frozen / whatever? How did you managed reset / etc? What is your actual step-by-step process other then just telling codex / claude code "do X"? What else had to be solved along the way?

I just think one good part of Marcan's work is that they streamed a lot of their workflow with all kind of problems occured along the way and you could see how to solve them.

And please so not let anti-llm crowd discourage you. People like me who want to use good hardware and already choose to pay for Apple one just need drivers that work good and feature complete - code purity and "quality" is secondary.

GeekyBearabout 2 hours ago
Figuring out how the hardware works and how to interface with it to submit work is a significant step all by itself.
carterschonwaldabout 1 hour ago
im pretty literate in intellectual property, but im pretty confused about the no looking at binary code artifacts bit.
ADevWithAnIdea35 minutes ago
TL;DR:

1. We want to guarantee our work is not a "derivative work" of anything Apple wrote.

2. If we look at any Apple binaries, there's no way prove that our code didn't borrow from Apple.

3. Since we didn't look at any Apple binaries, then there's no way our work can be a derivative work-- we didn't even look at their stuff.

larpingscholar19 minutes ago
Wouldn't using OpenAI break the cleanroom?
compiler-guy6 minutes ago
That is the debate. And it is hotly contested.

The legal framework around all this is way too immature to make a definitive statement one way or the other. Anyone who says otherwise is speculating.

The only way to clarity will be legislation or court cases, because it really could go either way.

xyst26 minutes ago
So this is specific _only_ to M4 Mac Mini and Neo? Or will this work on any M4 SoC such as M4 Max?
sscarduzioabout 1 hour ago
/goal have all this upstreamed to Linux
Advertisement
kmeisthaxabout 1 hour ago
Clean room is not 100% legally necessary for RE, but I would never touch an LLM to do RE work when there's even a chance the models have been trained on the thing I ultimately plan to reimplement.

Furthermore, given that Asahi Linux, the biggest game in town when it comes to running Linux on Apple silicon, is trying to be cleanroom, it is incredibly rude of you to not mention LLMs until after showing a page full of LLM-derived firmware ABI. This is a trap for anyone who's trying to be cleanroom.

jamesgeck0about 1 hour ago
The previous “Part 1” post is very candid about the approach, and the titles of both posts mention prompting.
varispeedabout 2 hours ago
> GPT-6 Astra and GPT-5.6 Sol are absolutely insane

Perhaps before Astra was nerfed. It is now the dumbest model right after Gemini. Sol still holds up.

hypercube3336 minutes ago
Claude models were blocked from logging into my own VM with my own credentials I gave it using ssh that I also gave it by its guard rails. I wouldn't doubt other models are nerfed but...you should provide some context around your comment
ADevWithAnIdeaabout 2 hours ago
Can't disagree more, but my experiences are my own.
recsv-heredocabout 2 hours ago
proof?
NamlchakKhandroabout 2 hours ago
See preview comment