From: "Ravinandan Arakali" <ravinandan.arakali@s2io.com>
To: "'Jeff Garzik'" <jgarzik@pobox.com>,
"'Francois Romieu'" <romieu@fr.zoreil.com>
Cc: <netdev@oss.sgi.com>, <leonid.grossman@s2io.com>,
<raghavendra.koushik@s2io.com>, <rapuru.sriram@s2io.com>
Subject: [PATCH 2.6.9-rc2 2/8] S2io: sw bug fixes
Date: Wed, 6 Oct 2004 18:23:24 -0700 [thread overview]
Message-ID: <006201c4ac0c$3e3da970$9810100a@S2IOtech.com> (raw)
In-Reply-To:
Hi,
Attached is the second patch in this submission. It contains the following
software bug fixes.
1. In free_rx_buffers clearing out RxDs not owned by Xena.
2. In alarm_intr_handler, when a serr error occurs, schedule a task to reset
the card rather than stopping Tx queue.
3. In s2io_close freeing IRQ before calling s2io_reset also added a new call
to flush queued tasks. This is not done if the s2io_close itself is called
from a queued task like s2io_restart_nic.
4. read_eeprom function has been changed such that data to be returned is
sent as an input argument and the return value represents a pass/fail. The
previous implementation as Randy had pointed out was error prone as on
failure it returned -1 which can be interpreted as all ff's, so any data
area which contained ff's in the eeprom was likely to be treated as an
error.
5. Added a flag "task_flag" to track if the call to s2io_close is coming
from the s2io_restart_nic function or from the ifconfig <I/F> down called by
user.
6. Moved register_netdev call from just after setting entry points to the
end of the s2io_init_nic function.
7. In s2io.h field added a new member into the s2io_nic structure called
"task_flag".
Thanks,
Ravi
next reply other threads:[~2004-10-07 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 1:23 Ravinandan Arakali [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 1:24 [PATCH 2.6.9-rc2 2/8] S2io: sw bug fixes Ravinandan Arakali
2004-10-14 1:13 Ravinandan Arakali
2004-10-14 14:44 ` Jeff Garzik
2004-10-14 17:35 ` Raghavendra Koushik
2004-10-15 18:52 ` 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='006201c4ac0c$3e3da970$9810100a@S2IOtech.com' \
--to=ravinandan.arakali@s2io.com \
--cc=jgarzik@pobox.com \
--cc=leonid.grossman@s2io.com \
--cc=netdev@oss.sgi.com \
--cc=raghavendra.koushik@s2io.com \
--cc=rapuru.sriram@s2io.com \
--cc=romieu@fr.zoreil.com \
/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).