From: andrew may <acmay@acmay.homeip.net>
To: linuxppc-embedded@lists.linuxppc.org
Cc: Armin <akuster@pacbell.net>
Subject: [PATCH] another for ibm_ocp_enet gzip'd
Date: Fri, 15 Mar 2002 11:41:37 -0800 [thread overview]
Message-ID: <20020315114137.A26609@ecam.san.rr.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
This patch includes the last patch that I sent before the
directory move, plus some more stuff.
1. Fix merge error with MAX_NUM_PHYS in find phy loop.
(the for loop condition should match the if check)
2. Fix bad Partner Link check for the added Phy.
3. added mal.sh to generate a new ibm_ocp_mal.c
mal.sh DCRN_MAL_BASE >ibm_ocp_mal.c
or mal.sh DCRN_MAL_BASE DCRN_MAL1_BASE >ibm_ocp_mal.c
will work. It seems that the second on generates a smaller
object file even though the code is bigger for the 405GP.
I would think it is because MAL1 is 0.
This condenses all the get/set mal calls into one for get
and one for set. I also changed mal_num to mal, just to help
me find/change things.
I think this is a better approach than what was in the _mal.c,
but I didn't change the makefile to generate the code on the
fly yet.
4. Added skb_res as a module param and config.in option.
5. Created rx_clean/fill functions to remove duplicate code
in open and the 2 rx interrupts.
6. Handle dev_alloc failures better by retrying to alloc before
the rxde interrupt.
[-- Attachment #2: ocp_enet.diff.gz --]
[-- Type: application/octet-stream, Size: 9410 bytes --]
next reply other threads:[~2002-03-15 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 19:41 andrew may [this message]
2002-03-15 20:05 ` [PATCH] another for ibm_ocp_enet gzip'd Tom Rini
2002-03-15 22:25 ` andrew may
2002-03-15 22:31 ` Tom Rini
2002-03-18 22:25 ` andrew may
2002-03-18 14:53 ` Armin
2002-03-18 22:56 ` andrew may
2002-03-19 0:28 ` Tom Rini
2002-03-19 0:54 ` andrew may
2002-03-19 1:01 ` Tom Rini
2002-03-15 20:06 ` Tom Rini
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=20020315114137.A26609@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=akuster@pacbell.net \
--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).