From: Paul Mundt <lethal@linux-sh.org>
To: Nick Warne <nick@ukfsn.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 RT8139too NIC problems
Date: Thu, 19 Feb 2004 12:11:22 -0500 [thread overview]
Message-ID: <20040219171122.GA17199@linux-sh.org> (raw)
In-Reply-To: <4034E88C.24740.4C5D4B6@localhost>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On Thu, Feb 19, 2004 at 04:47:08PM -0000, Nick Warne wrote:
> >From my config file:
>
> # CONFIG_8139CP is not set
> CONFIG_8139TOO=y
> # CONFIG_8139TOO_PIO is not set
> # CONFIG_8139TOO_TUNE_TWISTER is not set
> # CONFIG_8139TOO_8129 is not set
> # CONFIG_8139_OLD_RX_RESET is not set
> # CONFIG_8139_RXBUF_IDX= is not set
>
> No other NIC drivers are used.
>
> I am also stuck as to what the new RXBUF_IDX is for. It appears the
> new build needs it, as I cannot remove.
>
So read the help entry in Kconfig. Before this change went in, pretty much
everyone defaulted to a 32k receive ring size, which is also the current
default. If you had used the default value of 2 instead of trying to hack
around it, you might get better behavior from your driver..
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-19 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 16:47 2.6.3 RT8139too NIC problems Nick Warne
2004-02-19 17:11 ` Paul Mundt [this message]
2004-02-19 17:17 ` Nick Warne
2004-02-19 22:48 ` Jeff Garzik
2004-02-20 16:42 ` Nick Warne
-- strict thread matches above, loose matches on Subject: below --
2004-02-19 20:04 Nick Warne
2004-02-21 14:59 Nick Warne
[not found] ` <14539106.1077630890@42.150.104.212.access.eclipse.net.uk>
2004-02-24 18:23 ` Nick Warne
2004-02-24 20:36 Nick Warne
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=20040219171122.GA17199@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@ukfsn.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