HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ThomasKaiser
Knowledge
OPEN SOURCE2019–2024
ThomasKaiser / Knowledge

Knowledge

Discover this repository through its Hacker News conversations.

6Distinct people
6Mentions
0Explicit recommenders
294GitHub 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 year6 dated mentions

Observed mentions: 2019-05-23 21:22:42 UTC to 2024-04-15 21:28:14 UTC.

012342019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

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
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC413
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

6 sources
One thing worth noting is that basically, even now (almost 10 months post announcement), almost no one has a 6000U laptop outs (a search on Amazon and Best Buy shows two 6800U laptop models total, one Asus and one Lenovo). Two niche vendors, XMG and Star Labs, have both publicly stated that they would have loved to have offered Ryzen 6000 laptops, but couldn't get any allotments. There are were also well documented chipset issues - even into the summer Lenovo and Asus talked about requiring firmware updates to enable their USB4 ports. That being said, starting w/ Rembrandt, AMD now has full 40Gbps USB4 controllers built on-chip. I'm really looking forward to Ryzen 7040 because Phoenix looks great (Zen4 + RDNA3 on TSMC N4 - yes please) and hopefully USB4 support has matured enough on the AMD side that Framework is able to release something
Read the rest
. My understanding is that the I/O limitation is in the re-timers - currently the Framework uses 4X JHL8040R's (labeled as Burnside Bridge) directly connected to the iTBT: https://github.com/FrameworkComputer/Mainboard/blob/main/Ele... Apple used these for their first M1 MBAs as well: https://github.com/ThomasKaiser/Knowledge/blob/master/articl... But both Apple and AMD are now using Kandou retimers: * https://www.gizchina.com/2022/07/25/apple-completely-got-rid... * https://kandou.com/matterhorn.html * https://kandou.com/assets/downloads/product-briefs/KB8001-Pr...
In The Framework Laptop Chromebook Edition
A2 needs support in the Linux kernel. It's not there, yet. https://github.com/ThomasKaiser/Knowledge/blob/master/articl... "A2 promises even better performance with 4000/2000 read/write IOPS minimum but there's a problem since as outlined by the SD Association A2 cards show "much higher performance than A1 performance by using functions of Command Queuing and Cache". Cache and Command Queuing require host (driver) support since the host needs to activate those new features first. The cache feature on A2 rated cards makes use of volatile RAM on the card requiring the host to learn new commands to issue flushing the cache (involving the risk of data losses -- for details see especially chapter 4.17 in Physical Layer Simplified Specification 6.0)"
In A2-class microSD cards offer no better performance for the Raspberry Pi
My understanding is that A2 cards are generally slower than A1 cards IF you don't have host-side support for managing the volatile-RAM caching that A2 requires. So if the Pi 4 only allows you to run in A1 mode anyway, you're better off buying the A1 card and both saving money and getting a faster card. I don't know if that lack of support is true of the Pi 4, but it does seem to be true of most other SBCs according to https://github.com/ThomasKaiser/Knowledge/blob/master/articl...
In Raspberry Pi microSD card performance comparison

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.