HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
AsahiLinux
m1n1
Python2021–2026
AsahiLinux / m1n1

m1n1

A bootloader and experimentation playground for Apple Silicon

9Distinct people
14Mentions
1Explicit recommenders
4.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A bootloader and experimentation playground for Apple Silicon

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

I know you said you dont want mac, but I recommend apple only for the hardware. If you want linux, you can use Asahi Linux. Its in the beta stages but it allows your to harness…

havocsupreme used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:06:00 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year14 dated mentions

Observed mentions: 2021-01-15 03:47:03 UTC to 2026-06-28 21:50:22 UTC.

02462021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC505
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC606
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

6 sources
havocsupreme·Apr 20, 2022Recommendation phrase
I know you said you dont want mac, but I recommend apple only for the hardware. If you want linux, you can use Asahi Linux. Its in the beta stages but it allows your to harness mac’s superior hardware to develop on Linux. Apple is proven to make long lasting products that meet all the requirements you’ve list. Recommend M1 in particular, better than most intel and ARM laptops of its generation. https://github.com/AsahiLinux/m1n1
In Ask HN: What’s a good laptop for software development at around $2k?
The solution isn't to stop using rand(). The solution is to stop using newlib. If you're doing your own custom memory management like this, you shouldn't even have a malloc implementation at all. Even newlib is too bloated for your use case. At this point, chances are you're using a trivial subset of the C library and it'd be easy to roll your own. You can import bits and pieces from other projects (I personally sometimes copy and paste bits from PDClib for this). In such a tight embedded project, chances are you don't even have threads; why even pull in that reentrancy code? Freestanding C code with no standard library isn't scary. If you need an example, look at what we do for m1n1: https://github.com/AsahiLinux/m1n1/tree/main/src In particular, this is the libc subset we use (we do have malloc here, which is dlmalloc, but still not eno
Read the rest
ugh of libc to be worth depending on a full one): https://github.com/AsahiLinux/m1n1/tree/main/sysinc
In rand() may call malloc()
correct, i forgot some context about what i meant "apple developing", apple allowed raw images to be used now, this is what i described being used in the cpu manufacturing process for testing units. this was not always an option. i meant this pseudo-feature being made public, not asahi which has been public and apple has been aware of for over a year see here: [1]: https://github.com/AsahiLinux/m1n1/commit/0d4fb00ceb8a14f083... [2]: https://news.ycombinator.com/item?id=29591578
In Asahi Linux alpha release
> as long as they are ARM ISA compatible. And apparently in Apple's case, they get to be a little bit incompatible (no nVHE mode, crazy custom ISA extensions, ...) Which is also obvious proof that they're their own designs, because literally nobody else could or would implement the same Apple-proprietary ISA extensions. Here, we use some of the custom instructions in m1n1: https://github.com/AsahiLinux/m1n1/blob/main/src/gxf_asm.S#L... That won't work on any non-Apple core.
In Power, frequency, management: how M1 E cores win

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.