HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ebrandi
FDD-book
Shell2026–2026
ebrandi / FDD-book

FDD-book

FreeBSD Device Driver Book

2Distinct people
3Mentions
0Explicit recommenders
622GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

FreeBSD Device Driver Book

GitHub

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, 5:04:57 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 hour3 dated mentions

Observed mentions: 2026-04-26 22:53:06 UTC to 2026-04-27 06:00:54 UTC.

012026-04-26 22:00:00 UTC to 2026-04-26 23:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 26, 22:002026-04-26 23:00:00 UTC to 2026-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 00:00:00 UTC to 2026-04-27 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 01:00:00 UTC to 2026-04-27 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 02:00:00 UTC to 2026-04-27 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 27, 02:002026-04-27 03:00:00 UTC to 2026-04-27 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 04:00:00 UTC to 2026-04-27 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 05:00:00 UTC to 2026-04-27 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-04-27 06:00:00 UTC to 2026-04-27 07:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 27, 06:00

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
Apr 26, 22:002026-04-26 22:00:00 UTC2026-04-26 23:00:00 UTC110
Apr 26, 23:002026-04-26 23:00:00 UTC2026-04-27 00:00:00 UTC000
Apr 27, 00:002026-04-27 00:00:00 UTC2026-04-27 01:00:00 UTC000
Apr 27, 01:002026-04-27 01:00:00 UTC2026-04-27 02:00:00 UTC000
Apr 27, 02:002026-04-27 02:00:00 UTC2026-04-27 03:00:00 UTC000
Apr 27, 03:002026-04-27 03:00:00 UTC2026-04-27 04:00:00 UTC000
Apr 27, 04:002026-04-27 04:00:00 UTC2026-04-27 05:00:00 UTC000
Apr 27, 05:002026-04-27 05:00:00 UTC2026-04-27 06:00:00 UTC101
Apr 27, 06:002026-04-27 06:00:00 UTC2026-04-27 07:00:00 UTC101

What Hacker News says

3 sources
There is something wrong with it because LLMs are really not capable of writing a useful book, and this book is 100% LLM slop. Look at this totally useless """introduction""" to C: https://github.com/ebrandi/FDD-book/blob/main/content/chapte... First of all this is an entire book, it's 76,000 words. But look at the first nontrivial example of C after "hello world," under "Bonus learning point about C return values" exec_map_first_page(struct image_params *imgp) { vm_object_t object; vm_page_t m; int error; if (imgp->firstpage != NULL) exec_unmap_first_page(imgp); object = imgp->vp->v_object; if (object == NULL) return (EACCES); #if VM_NRESERVLEVEL > 0 if ((object->flags & OBJ_COLORED) == 0) { VM_OBJECT_WLOCK(object
Read the rest
); vm_object_color(object, 0); VM_OBJECT_WUNLOCK(object); } #endif error = vm_page_grab_valid_unlocked(&m, object, 0, VM_ALLOC_COUNT(VM_INITIAL_PAGEIN) | VM_ALLOC_NORMAL | VM_ALLOC_NOBUSY | VM_ALLOC_WIRED); if (error != VM_PAGER_OK) return (EIO); imgp->firstpage = sf_buf_alloc(m, 0); imgp->image_header = (char *)sf_buf_kva(imgp->firstpage); return (0); } This teaches nobody anything. I am sorry but this project is completely useless and there's no way Brandi read a single word of it. This entire book is a dishonest AI scam. I hate LLMs. It is hard to think of another computer technology that has done so much damage for so little good. Edit: I mean look at the intro to for loops. This is supposed to be for total beginners. Example 1: for (int i = 0; i < 10; i++) { printf("%d\n", i); } >> Start at i = 0 >> Repeat while i < 10 >> Increment i each time by 1 (i++) Example 2: for (i = 0; n > 0 && i < IFLIB_MAX_RX_REFRESH; n--, i++) { struct netmap_slot *slot = &ring->slot[nm_i]; uint64_t paddr; void *addr = PNMB(na, slot, &paddr); /\* ... work per buffer ... \*/ nm_i = nm_next(nm_i, lim); nic_i = nm_next(nic_i, lim); } >> What this loop does >> * The driver is refilling receive buffers so the NIC can keep receiving packets. >> * It processes buffers in batches: up to IFLIB_MAX_RX_REFRESH each time. >> * i counts how many buffers we've handled in this batch. n is the total remaining buffers to refill; it decrements every iteration. >> * For each buffer, the code grabs its slot, figures out the physical address, readies it for DMA, then advances the ring indices (nm_i, nic_i). >> * The loop stops when either the batch is full (i hits the max) or there's nothing left to do (n == 0). The batch is then "published" to the NIC by the code right after the loop. >> In essence, a for loop is the go-to choice when you have a clear limit on how many times something should run. It packages initialisation, condition checking, and iteration updates into a single, compact header, making the flow easy to follow. Total garbage. This has literally zero educational value. I assume Brandi is just trying to make a quick buck, he truly has not even glanced at the output. He should be ashamed of himself.
In FreeBSD Device Drivers Book

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.