From: Philippe De Muyter <phdm@macqel.be>
To: akpm@osdl.org
Cc: jeff@garzik.org, netdev@vger.kernel.org, jesse@icplus.com.tw
Subject: Re: [patch 3/8] sundance: remove TxStartThresh and RxEarlyThresh
Date: Mon, 23 Oct 2006 00:05:52 +0200 [thread overview]
Message-ID: <20061022220552.GA1122@ingate.macqel.be> (raw)
In-Reply-To: <200610202142.k9KLg5W6003719@shell0.pdx.osdl.net>
On Fri, Oct 20, 2006 at 02:42:05PM -0700, akpm@osdl.org wrote:
> From: Jesse Huang <jesse@icplus.com.tw>
> For patent issue need to remove TxStartThresh and RxEarlyThresh. This patent
> is cut-through patent. If use this function, Tx will start to transmit after
> few data be move in to Tx FIFO. We are not allow to use those function in
> DFE530/DFE550/DFE580/DL10050/IP100/IP100A. It will decrease a little
> performance.
[...]
> @@ -1111,6 +1109,7 @@ static irqreturn_t intr_handler(int irq,
> int tx_cnt;
> int tx_status;
> int handled = 0;
> + int i;
What the use here of adding this variable ? Is that actually a part of another
patch ?
>
>
> do {
> @@ -1153,17 +1152,14 @@ static irqreturn_t intr_handler(int irq,
> np->stats.tx_fifo_errors++;
> if (tx_status & 0x02)
> np->stats.tx_window_errors++;
> +
> /*
> ** This reset has been verified on
> ** DFE-580TX boards ! phdm@macqel.be.
> */
> if (tx_status & 0x10) { /* TxUnderrun */
> - unsigned short txthreshold;
> -
> - txthreshold = ioread16 (ioaddr + TxStartThresh);
> /* Restart Tx FIFO and transmitter */
> sundance_reset(dev, (NetworkReset|FIFOReset|TxReset) << 16);
> - iowrite16 (txthreshold, ioaddr + TxStartThresh);
I must be dense, but I do not understand how merely preserving the value of
a register across a reset can infringe on any patent
Philippe
next prev parent reply other threads:[~2006-10-22 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 21:42 [patch 3/8] sundance: remove TxStartThresh and RxEarlyThresh akpm
2006-10-22 22:05 ` Philippe De Muyter [this message]
2006-11-07 9:37 ` 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=20061022220552.GA1122@ingate.macqel.be \
--to=phdm@macqel.be \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=jesse@icplus.com.tw \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.