From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9atom
Date: Fri, 4 Jan 2013 14:44:43 -0500 [thread overview]
Message-ID: <7521b5d1fdc0098bceb82c83660444bf@ladd.quanstro.net> (raw)
In-Reply-To: <20130104202252.0b9bec10@zinc.9fans.fr>
> Surprisingly, I have another version of this patch
> which should convince your former colleague :-)
>
> http://www.9legacy.org/9legacy/patch/pc-sdata-dma.diff
@@ -455,6 +455,8 @@
and
.I slot
to use as a root device for bootstrapping.
+.SS \fL*nodma=\fP
+Disable DMA on (S)ATA controllers.
it's a pretty consistent mistake in plan 9 (and elsewhere)
that ide is confused with ata or sata. these the are all
on different levels. "Disable DMA on IDE controllers."
ide device register set (analogue FIS)
sata on-the-wire protocol (analogue pata)
ata abstract command set.
ahci is not in this list because it's a programming
interface that is not directly tied to the hardware.
there are other programming interfaces for the
same hardware. (e.g. marvell & lsi interfaces.)
"sdata" is a misleading name, since it implies that it
actually handles the read/write ↔ ata command
translation. what it does is translate between
read/write and ata+ide in one fell swoop.
this sounds economical, until one realizes that things
like PUIS (power-up in standby) and SCT are fancy
protocols that happen at the ATA layer, and if not
abstracted, need to be repeated for every driver.
in essence, this is the rationale for the fis library:
it's tiresome rewriting the PUIS protocol.
- erik
next prev parent reply other threads:[~2013-01-04 19:44 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 3:50 erik quanstrom
2013-01-03 8:17 ` Bence Fábián
2013-01-04 9:37 ` faif
2013-01-04 16:19 ` erik quanstrom
2013-01-04 16:27 ` John Floren
2013-01-04 16:35 ` Aram Hăvărneanu
2013-01-04 16:39 ` Rox 64
2013-01-04 17:26 ` John Floren
2013-01-04 17:41 ` John Floren
2013-01-04 18:48 ` David du Colombier
2013-01-04 19:05 ` Richard Miller
2013-01-04 19:22 ` David du Colombier
2013-01-04 19:44 ` erik quanstrom [this message]
2013-01-04 20:08 ` David du Colombier
2013-01-04 20:27 ` Bakul Shah
2013-01-04 20:36 ` erik quanstrom
2013-01-04 20:59 ` Bakul Shah
2013-01-05 2:21 ` erik quanstrom
2013-01-05 20:07 ` Rox 64
2013-01-05 20:10 ` Rox 64
2013-01-05 21:13 ` David du Colombier
2013-01-05 22:42 ` Rox 64
2013-01-05 23:25 ` John Floren
2013-01-05 23:36 ` Jacob Todd
2013-01-05 23:43 ` Rox 64
2013-01-05 23:56 ` John Floren
2013-01-06 0:29 ` Rox 64
2013-01-06 0:55 ` Rox 64
2013-01-06 1:05 ` Matthew Veety
2013-01-06 14:24 ` Rox 64
2013-01-06 14:28 ` erik quanstrom
2013-01-06 16:49 ` Rox 64
2013-01-06 17:34 ` John Floren
2013-01-04 19:31 ` Jack Johnson
2013-01-04 19:35 ` erik quanstrom
2013-01-04 19:50 ` Rox 64
2013-01-04 20:03 ` Matthew Veety
2013-01-04 20:24 ` erik quanstrom
2013-01-04 20:33 ` Rox 64
2013-01-04 22:13 ` David du Colombier
2013-01-04 20:55 ` Matthew Veety
2013-01-04 17:49 ` erik quanstrom
2013-01-04 18:46 ` David du Colombier
2013-01-04 16:34 ` Richard Miller
2013-01-04 17:58 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2013-03-01 14:11 erik quanstrom
2011-11-21 20:13 erik quanstrom
2011-05-07 2:57 erik quanstrom
2011-05-16 14:41 ` Steve Simon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7521b5d1fdc0098bceb82c83660444bf@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).