lkml.org 
[lkml]   [2006]   [May]   [31]   [last100]   RSS Feed
Views: [more markup]   [less markup]   [headers]   [forward]  
 
 
Messages in this thread
/
DateWed, 31 May 2006 07:50:32 +0200
FromManfred Spraul <>
SubjectRe: [PATCH-2.4] forcedeth update to 0.50
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-05-31 07:53    [from the cache]
©2003-2008