* [update] 2.6.4-rc2 - Realtek 8169 patches
@ 2004-03-07 1:37 Francois Romieu
2004-03-09 9:01 ` crochu nicolas
0 siblings, 1 reply; 4+ messages in thread
From: Francois Romieu @ 2004-03-07 1:37 UTC (permalink / raw)
To: netdev
An updated version of the r8169 patches against 2.6.4-rc2 is available.
Individual files:
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.4-rc2
Tarball:
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.4-rc2/r8169-blob.tar.bz2
Readme:
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.4-rc2/README.txt
Comparison with standard r8169 driver up to the point where r8169-getstats.patch
is applied as described in the README.txt file will be welcome.
If you feel adventurous, you can directly try:
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.4-rc2/r8169-full.patch
Please Cc: netdev@oss.sgi.com on success/failure.
--
Ueimor
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [update] 2.6.4-rc2 - Realtek 8169 patches
2004-03-07 1:37 [update] 2.6.4-rc2 - Realtek 8169 patches Francois Romieu
@ 2004-03-09 9:01 ` crochu nicolas
2004-03-11 18:39 ` Francois Romieu
0 siblings, 1 reply; 4+ messages in thread
From: crochu nicolas @ 2004-03-09 9:01 UTC (permalink / raw)
To: romieu; +Cc: netdev
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
If i apply only these patch, everything goes fine
r8169-dma-api-tx.patch
r8169-dma-api-rx-buffers.patch
r8169-dma-api-tx-buffers.patch
r8169-rx_copybreak.patch
r8169-mac-phy-version.patch
r8169-init_one.patch
r8169-timer.patch
r8169-hw_start.patch
r8169-intr_mask.patch
r8169-suspend.patch
r8169-endianness.patch
r8169-getstats.patch
if i apply
r8169-addr-high.patch,
then i can ping myself, but i can't ping the rest of the world.
and, even if i put back my previous correct working driver,
i can't make it work right => reboot.
nothing realy interesting in the logfiles.
C.Nicolas.
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [update] 2.6.4-rc2 - Realtek 8169 patches
2004-03-09 9:01 ` crochu nicolas
@ 2004-03-11 18:39 ` Francois Romieu
2004-03-12 13:40 ` crochu nicolas
0 siblings, 1 reply; 4+ messages in thread
From: Francois Romieu @ 2004-03-11 18:39 UTC (permalink / raw)
To: crochu nicolas; +Cc: netdev
crochu nicolas <nicolas.crochu@sgam.com> :
> If i apply only these patch, everything goes fine
[...]
Did you stress the driver, say (rsync), ping -f -s 8, ttcp ?
--
Ueimor
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [update] 2.6.4-rc2 - Realtek 8169 patches
2004-03-11 18:39 ` Francois Romieu
@ 2004-03-12 13:40 ` crochu nicolas
0 siblings, 0 replies; 4+ messages in thread
From: crochu nicolas @ 2004-03-12 13:40 UTC (permalink / raw)
To: Francois Romieu; +Cc: netdev
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
Le jeu 11/03/2004 à 19:39, Francois Romieu a écrit :
> crochu nicolas <nicolas.crochu@sgam.com> :
> > If i apply only these patch, everything goes fine
> [...]
> Did you stress the driver, say (rsync), ping -f -s 8, ttcp ?
> --
> Ueimor
I tested with unison, ping -f -s 8
as did a friend with the same hardware.
My kernel : 2.6.3 + patched driver ( except the last 3 patch )
My friend : a stock 2.6.4-mm1 kernel.
everything goes fine.
my friend told me something about the io/schedulers as a source
of instability .. i'm investigatng.
C.Nicolas.
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-03-12 13:40 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-07 1:37 [update] 2.6.4-rc2 - Realtek 8169 patches Francois Romieu
2004-03-09 9:01 ` crochu nicolas
2004-03-11 18:39 ` Francois Romieu
2004-03-12 13:40 ` crochu nicolas
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).