From: Ricardo Scop <scop@digitel.com.br>
To: Jean-Denis Boyer <jdboyer@mediatrix.com>
Cc: linuxppc-embedded@lists.linuxppc.org,
Dan Malek <dan@embeddededge.com>,
andy_lowe@mvista.com
Subject: Re[2]: Kernel oops while routing
Date: Wed, 5 Dec 2001 19:41:13 -0300 [thread overview]
Message-ID: <12820.011205@digitel.com.br> (raw)
In-Reply-To: <F1BED55F35F4D3118C0F00E0295CFF4DFF9E7F@mail.mediatrix.com>
Jean-Denis,
Wednesday, December 05, 2001, 3:01:28 PM, you wrote:
JDB> IMHO, I could suggest an easier patch, that would result in modifying only
JDB> one line of code, without changing the 'tx_full' logic. In function
JDB> fcc_enet_start_xmit, instead of checking the ready bit (which is bad), we
JDB> could only check if cur_tx has reached dirty_tx, and then call
JDB> netif_stop_queue. Does it make sense?
Make sense to me. I'll try it out.
JDB> BTW, I worked hard last week in debugging the fcc_enet driver. It was not
JDB> handling correctly some transmission errors, resulting in the transmitter
JDB> completely stopping, without restarting. This is related to an errata
JDB> (CPM37) from Motorola about the 8260, concerning the way of restarting the
JDB> transmitter. If someone is interested, I can release a patch for that.
I'm interested!
Ricardo Scop mailto:scop@vanet.com.br
R SCOP Consulting
------------------------------------------------------------------
"What's money? A man is a success if he gets up in the morning and
goes to bed at night and in between does what he wants to do."
~Bob Dylan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-05 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 18:01 Kernel oops while routing Jean-Denis Boyer
2001-12-05 18:21 ` Peter Desnoyers
2001-12-05 18:33 ` Dan Malek
2001-12-05 22:41 ` Ricardo Scop [this message]
2001-12-07 15:56 ` Arto Vuori
-- strict thread matches above, loose matches on Subject: below --
2001-11-29 22:42 Dan Malek
2001-12-05 3:24 ` Re[2]: " Ricardo Scop
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=12820.011205@digitel.com.br \
--to=scop@digitel.com.br \
--cc=andy_lowe@mvista.com \
--cc=dan@embeddededge.com \
--cc=jdboyer@mediatrix.com \
--cc=linuxppc-embedded@lists.linuxppc.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).