From: Manfred Spraul <manfred@colorfullife.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: marcelo@kvack.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: [PATCH-2.4] forcedeth update to 0.50
Date: Wed, 31 May 2006 07:50:32 +0200 [thread overview]
Message-ID: <447D2EA8.8020001@colorfullife.com> (raw)
In-Reply-To: <20060530220319.GA6945@w.ods.org>
Hi Willy,
Willy Tarreau wrote:
>I started from the latest backport you sent in september (0.42) and
>incrementally applied 2.6 updates. I stopped at 0.50 which provides
>VLAN support, because after this one, there are some 2.4-incompatible
>changes (64bit consistent memory allocation for rings, and MSI/MSIX
>support).
>
>
>
I agree, 2.4 needs a backport. Either a full backport as you did, or a
minimal one-liner fix.
Right now, the driver is not usable due to an incorrect initialization.
Or to be more accurate:
# modprobe
# ifup
works.
But
# modprobe
# ifup
# ifdown
# ifup
causes a misconfiguration, and the nic hangs hard after a few MB. And
recent distros do the equivalent of ifup/ifdown/ifup somewhere in the
initialization.
Marcelo: Do you need a one-liner, or could you apply a large backport patch?
--
Manfred
next prev parent reply other threads:[~2006-05-31 5:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 22:03 [PATCH-2.4] forcedeth update to 0.50 Willy Tarreau
2006-05-31 5:50 ` Manfred Spraul [this message]
2006-05-31 5:54 ` Willy Tarreau
2006-05-31 18:05 ` Marcelo Tosatti
2006-05-31 19:50 ` Manfred Spraul
2006-05-31 19:43 ` Willy Tarreau
2006-05-31 20:07 ` Marcelo Tosatti
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=447D2EA8.8020001@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=aabdulla@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=willy@w.ods.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.