From: "Mikael Starvik" <mikael.starvik@axis.com>
To: "'Bartlomiej Zolnierkiewicz'" <B.Zolnierkiewicz@elka.pw.edu.pl>,
"'Mikael Starvik'" <mikael.starvik@axis.com>,
"'Jeff Garzik'" <jgarzik@pobox.com>,
"'Andrew Morton'" <akpm@osdl.org>
Cc: "'Linux Kernel'" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] CRIS architecture update
Date: Mon, 7 Jun 2004 07:42:18 +0200 [thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C668640C44@exmail1.se.axis.com> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C668D47E56@exmail1.se.axis.com>
>It will probably fail on devices needing write access because
>e100_dma_begin() always passes e100_read_command as
>argument to e100_start_dma().
e100_read_command is a variable that is either 1 for reads
or 0 for writes. This variable is set in e100_dma_write and
e100_dma_read. As long as the framework calls dma_write or
dma_read before it calls dma_begin it will work just fine.
The driver has been tested with a ext2 filesystem on a disk
(and the files are still there after a sync and reboot).
/Mikael
next parent reply other threads:[~2004-06-07 5:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BFECAF9E178F144FAEF2BF4CE739C668D47E56@exmail1.se.axis.com>
2004-06-07 5:42 ` Mikael Starvik [this message]
[not found] <BFECAF9E178F144FAEF2BF4CE739C668D47C24@exmail1.se.axis.com>
2004-06-07 5:53 ` Mikael Starvik
2004-06-07 18:43 ` Sam Ravnborg
2004-06-07 19:00 ` Bartlomiej Zolnierkiewicz
[not found] <BFECAF9E178F144FAEF2BF4CE739C668D0BC1E@exmail1.se.axis.com>
2004-06-04 5:46 ` Mikael Starvik
2004-06-04 16:57 ` Sam Ravnborg
2004-06-04 23:25 ` Bartlomiej Zolnierkiewicz
[not found] <200406031419.i53EJgVI027812@hera.kernel.org>
2004-06-03 15:41 ` Jeff Garzik
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=BFECAF9E178F144FAEF2BF4CE739C668640C44@exmail1.se.axis.com \
--to=mikael.starvik@axis.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®