From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux1394-devel@lists.sourceforge.net,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] firewire: net: rate-limit log spam at transmit failure
Date: Sun, 07 Nov 2010 13:03:08 +0100 [thread overview]
Message-ID: <4CD6957C.5030504@s5r6.in-berlin.de> (raw)
In-Reply-To: <1289100737.3277.32.camel@maxim-laptop>
Maxim Levitsky wrote:
> I have here my own hack to set the transaction timeout,
You can use firecontrol to set it on-the-fly. To set it on node ffc2 i.e. the
node with phy ID 2, and controller 1 (i.e. libraw1394 "port" 1):
# echo "w . 2 0xfffff0000018 4 3" | firecontrol 1
This sets the whole-seconds part to 3, which gives you 3.1 seconds timeout if
the fractional part at 0xfffff000001c is still at its default value of 0.1
seconds, i.e. 800 << 19 (subsecond part in units of (1/8000)s shifted by 19).
# { echo "r . 2 0xfffff0000018 4"; echo "r . 2 0xfffff000001c 4"; } |
firecontrol 1
displays the current register value on node ffc2 at port 1. Type "help" in
firecontrol for more available firecontrol commands.
--
Stefan Richter
-=====-==-=- =-== --===
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-11-07 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tkrat.01ca17fba0508ae0@s5r6.in-berlin.de>
[not found] ` <tkrat.1b9925fa1d199c23@s5r6.in-berlin.de>
[not found] ` <tkrat.18b9f67ac78dcbea@s5r6.in-berlin.de>
[not found] ` <tkrat.276aeae22ec60090@s5r6.in-berlin.de>
2010-11-07 3:26 ` [PATCH] firewire: net: rate-limit log spam at transmit failure Maxim Levitsky
2010-11-07 3:32 ` Maxim Levitsky
2010-11-07 12:03 ` Stefan Richter [this message]
2010-11-08 1:41 ` Maxim Levitsky
2010-11-08 8:12 ` Stefan Richter
2010-11-07 11:10 ` Stefan Richter
2010-11-07 12:04 ` Maxim Levitsky
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=4CD6957C.5030504@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=maximlevitsky@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).