HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
tinygrad
7900xtx
Python2024–2025
tinygrad / 7900xtx

7900xtx

Discover this repository through its Hacker News conversations.

7Distinct people
8Mentions
0Explicit recommenders
462GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 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 month8 dated mentions

Observed mentions: 2024-03-24 15:16:43 UTC to 2025-01-21 07:41:27 UTC.

0122024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsMar 20242024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 20242024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-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 2025-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 2025

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
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC220
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC202
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC000
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC000
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC101
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC000
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC000
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC110
Nov 20242024-11-01 00:00:00 UTC2024-12-01 00:00:00 UTC000
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC101

What Hacker News says

8 sources
> Looking at his recent track record[1] One might argue he's had a pattern for even longer. While he did do some early hypervisor glitching, even his PS3 root key release was basically just applying fail0verflow's ECDSA exploit (fail0verflow didn't release the keys specifically because they didn't want to get sued ... so that was a pretty dick move [1]). For his projects, I think it's important to look at what he's done that's cool (eg, reversing 7900XTX [2], creating a user-space driver that completely bypasses AMD drivers for compute [3]) and separating it from his (super cringe) social media postings/self-hype. Still, at the end of the day, here's hoping that someone at AMD realizes that having terrible consumer and workstation support will basically continue to be a huge albatross/handicap - it cuts them off basically all academic/res
Read the rest
earch development (almost every single ML library and technique you can name/used in production is CUDA first because of this) and the non-hyperscaler enterprise market as well. Any dev can get a PO for a $500 Nvidia GPU (or has one on their workstation laptop already). What's the pathway for ROCm? (honestly, if I were in charge, my #1 priority would be to make sure ROCm is installed and works w/ every single APU installed, even the 2CU ones). [1] https://en.wikipedia.org/wiki/Sony_Computer_Entertainment_Am... [2] https://github.com/tinygrad/7900xtx [3] https://github.com/tinygrad/tinygrad/blob/master/docs/develo...
In ROCm Device Support Wishlist
HiPHInch·Oct 9, 2024Submission

Ask HN: In October 2024, is it a good idea to get an RX 7900 XT for ML?

Pros: Relatively low price - The 7900XT is more competitively priced compared to equivalent NVIDIA GPUs. Good 4K gaming performance - For games at 4K resolution, the 7900XT can provide satisfactory performance. George Hotz's tinybox project offers both 6x 7900XTX and 6x 4090, indicating that the 7900XT may have promising applications in certain computational fields. Open-Source - ROCm (Radeon Open Compute) is open-source, while NVIDIA's official drivers are not. We should support open-source initiatives. Cons: Less mature software ecosystem - Getting research programs to run on the 7900XT may require substantial debugging and optimization work. Higher power consumption - Compared to NVIDIA products of the same tier, the 7900XT generally has higher power consumption. Driver stability issues - AMD GPU d
Read the rest
rivers have historically been less stable and reliable than NVIDIA's, potentially leading to driver crashes and other problems. Resources: https://github.com/geohot/7900xtx Run machine learning on 7900XT and 7900XTX on PyTorch: https://gist.github.com/AlkindiX/9c54d1155ba72415f3b585e26c9df6b3 https://github.com/ROCm/ROCm
1 points · Open discussion
>> I see no indications either that either nvidia nor any of the rest of the manufacturers has moved any respectable amount of functionality to the firmware. Someone who believes this could easily prove that they are correct by "simply" taking their 4090 and documenting all its functionality, as was done with the [7900 xtx](https://github.com/geohot/7900xtx). You can't say "I see no indications/evidence" unless you have proven that there is no evidence, no?
In NVIDIA Transitions Fully Towards Open-Source Linux GPU Kernel Modules
> I do love AMD because its drivers are open source as opposed to nVidia. AMD's drivers are not really more open that Nvidia's. Similar to Nvidia's Open GPU Kernel Module's[0], AMD's opensource drivers are mostly a shim that wrap firmware blobs[1] in which the functionality you really care about is contained. [0] https://github.com/NVIDIA/open-gpu-kernel-modules/discussion... [1] https://github.com/geohot/7900xtx/
In AMD ROCm Going Open-Source: Will Include Software and Hardware Documentation

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.