I just did something similar to bring mainline Linux to my Daylight DC-1 [1] [2], although possibly more difficult since I had to start from scratch.
I can guarantee the same amount of work, without AI, takes probably 10x or more time (I did it in the past w/ the Google Pixel C [3]).
Unfortunately it looks like pmOS is against AI [4], so I'll likely switch away from pmOS and never contribute a single line in the future.
Too bad, I was a huge fan [5].
Because one of the biggest hurdles to porting the Linux kernel and device-specific software to more hardware and making existing hardware work better is one of the things that "AI" can (seemingly, caveat) do surprisingly well?
Not to say PM (or any other project) should/shouldn't use AI. There are plenty of other salient reasons to reject AI. But given (from what I remember) postmarket's goal is basically saving as many phones from becoming ewaste as possible, well, an LLM could actually be a formidable way to get more hardware than ever running.
Couldn't these concerns be addressed through two potential angles ?
- You make your AI do all that work, pay xxx tokens worth to get something running and you can use your old phone while taking full responsability for your vibe code. Each user will have to do it, but the whole path could be optimize LLM side as well, after all you're just renting it.
- You use AI to find a working solution but vet it and write everything's needed to meet the submission standard. You put the time needed for it to be accepted as non AI, and proudly put your name on the line as the final author of everything you submit.
denysvitali · · focus · HN ↗
I can guarantee the same amount of work, without AI, takes probably 10x or more time (I did it in the past w/ the Google Pixel C [3]).
Unfortunately it looks like pmOS is against AI [4], so I'll likely switch away from pmOS and never contribute a single line in the future. Too bad, I was a huge fan [5].
[1]: <a href="https://daylightcomputer.com/product" rel="nofollow">https://daylightcomputer.com/product
[2]: <a href="https://x.com/DenysVitali/status/2091238391710888416" rel="nofollow">https://x.com/DenysVitali/status/2091238391710888416
[3]: <a href="https://github.com/pixelc-linux/documentation" rel="nofollow">https://github.com/pixelc-linux/documentation
[4]: <a href="https://docs.postmarketos.org/policies-and-processes/development/ai-policy.html" rel="nofollow">https://docs.postmarketos.org/policies-and-processes/develop...
[5]: <a href="https://blog.denv.it/posts/pmos-k3s-cluster/" rel="nofollow">https://blog.denv.it/posts/pmos-k3s-cluster/
officeplant · · focus · HN ↗
Why would you think one of the more beloved projects for linux mobile phones would be pro-AI?
spijdar · · focus · HN ↗
Not to say PM (or any other project) should/shouldn't use AI. There are plenty of other salient reasons to reject AI. But given (from what I remember) postmarket's goal is basically saving as many phones from becoming ewaste as possible, well, an LLM could actually be a formidable way to get more hardware than ever running.
makeitdouble · · focus · HN ↗
- You make your AI do all that work, pay xxx tokens worth to get something running and you can use your old phone while taking full responsability for your vibe code. Each user will have to do it, but the whole path could be optimize LLM side as well, after all you're just renting it.
- You use AI to find a working solution but vet it and write everything's needed to meet the submission standard. You put the time needed for it to be accepted as non AI, and proudly put your name on the line as the final author of everything you submit.