netdev - Re: need some help on a backport of r8169

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Feb 2007 12:02:43 +0100
From:	Pascal GREGIS <pgs@...erway.com>
To:	netdev@...r.kernel.org
Subject: Re: need some help on a backport of r8169

Francois Romieu a écrit, le Tue 27 Feb 2007 à 12:48:31AM :
> Pascal GREGIS <pgs@...erway.com> :
> [...]
> > Could anyone take a look at my patch and tell me what is missing,
> 
> - It lacks the adequate registers init sequence for a 8168 for instance.
> - Fix went in between 2.6.11 and 2.6.12.
Where is this init sequence in the driver? I searched in the code and didn't find something that could satisfy, then I took the 2.6.12.3 r8169.c, put it in the 2.6.11.11 source tree, applied my patch, changed synchronize_sched(); to synchronize_kernel(); because the symbol was unknown and then I could turn eth1 on and assign it an ip address but the rx and tx count never grew and when I turned eth0 down (a 8139 card) eth1 didn't reply to ping anymore.
 
> 
> There are 59 r8169 related patches between 2.6.12 and current. Only a few
> of those break the API. I'll give it a try tomorrow evening.
Hmm... you wrote this mail at 00 h 48 this morning, what did you mean by tomorrow evening?


Merci

Pascal
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html