MCD(4)

πŸ“¦ version 11.0, in nixpkgs unstable

πŸ’Ώ mcd β€” Mitsumi CD-ROM driver πŸŽ€

Hiii bestie, so this page is all about the mcd driver β€” it's the section 4 (kernel interfaces) manual page for the Mitsumi CD-ROM situation. Grab a snack, we're getting into it ✨


🌸 SYNOPSIS 🌸

mcd0 at isa? port 0x300 irq 10
options MCD_PROMISC

That's the whole vibe right there β€” one device line, one option, iconic behavior πŸ’…


✨ DESCRIPTION ✨

okay so the mcd driver literally exists to provide support for the Mitsumi CD-ROM controller and drive over on the isa(4) bus. That's it, that's the whole job, and it does it 🫢


πŸŽ€ FILES πŸŽ€

  • /dev/cd[0-9][a-h] β€” the block mode Mitsumi CD-ROM devices, one per drive letter situation
  • /dev/rmcd[0-9][a-h] β€” the raw mode Mitsumi CD-ROM devices, if that's more your speed πŸ¦‹

πŸ¦‹ SEE ALSO πŸ¦‹

intro(4), isa(4), ne(4), we(4) β€” go read those too, iykyk πŸ“š


πŸ’€ BUGS πŸ’€

ngl bestie, this is the part where it gets a little messy 😭

The mcd hardware is difficult to probe accurately. Like, historically speaking, the mcd probe would accept any return values as proof that an mcd drive was actually there. Which sounds chill in theory but it is NOT, because other devices β€” particularly ne(4) or we(4) β€” would then get incorrectly claimed by the mcd driver. Not them getting kidnapped by the wrong driver?? πŸ™ˆ

The driver now only accepts result codes known to indicate Mitsumi-compatible CD controllers, which slays, but the tradeoff is real: it may reject some mcd hardware which returns other result codes. So yeah, some legit hardware might get left on read. πŸ˜”

options MCD_PROMISC brings back the original promiscuous probe behaviour. Use with extreme caution. Fr fr, do not play with this one πŸ’…

and that's the whole page, bestie!! this one came from the Debian edition, dated November 29, 1994 β€” yeah, she's vintage, she's a classic, we respect her πŸ‘‘β­

pinkies out πŸ“

πŸ“¦ where this page comes from