mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net,
	Bernhard Kaindl <bk@suse.de>, Ingo Molnar <mingo@elte.hu>
Subject: [PATCH] Documentation: correction to debugging-via-ohci1394
Date: Mon, 18 Feb 2008 19:40:09 +0100 (CET)	[thread overview]
Message-ID: <tkrat.c3c4e46842ad7e84@s5r6.in-berlin.de> (raw)

Rectify a factoid about firewire-ohci.

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
Ingo, I can get this to Linus via linux1394-2.6.git.

 Documentation/debugging-via-ohci1394.txt |   13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

Index: linux-2.6.25-rc2/Documentation/debugging-via-ohci1394.txt
===================================================================
--- linux-2.6.25-rc2.orig/Documentation/debugging-via-ohci1394.txt
+++ linux-2.6.25-rc2/Documentation/debugging-via-ohci1394.txt
@@ -36,13 +36,14 @@ available (notebooks) or too slow for ex
 Drivers
 -------
 
-The OHCI-1394 drivers in drivers/firewire and drivers/ieee1394 initialize
-the OHCI-1394 controllers to a working state and can be used to enable
-physical DMA. By default you only have to load the driver, and physical
-DMA access will be granted to all remote nodes, but it can be turned off
-when using the ohci1394 driver.
+The ohci1394 driver in drivers/ieee1394 initializes the OHCI-1394 controllers
+to a working state and enables physical DMA by default for all remote nodes.
+This can be turned off by ohci1394's module parameter phys_dma=0.
 
-Because these drivers depend on the PCI enumeration to be completed, an
+The alternative firewire-ohci driver in drivers/firewire uses filtered physical
+DMA, hence is not yet suitable for remote debugging.
+
+Because ohci1394 depends on the PCI enumeration to be completed, an
 initialization routine which can runs pretty early (long before console_init(),
 which makes the printk buffer appear on the console can be called) was written.
 

-- 
Stefan Richter
-=====-==--- --=- =--=-
http://arcgraph.de/sr/


             reply	other threads:[~2008-02-18 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 18:40 Stefan Richter [this message]
2008-02-18 19:09 ` Ingo Molnar

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=tkrat.c3c4e46842ad7e84@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=bk@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=mingo@elte.hu \
    /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®