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
| ||
|
Message-ID: <20070710212513.GB3436@electric-eye.fr.zoreil.com> Date: Tue, 10 Jul 2007 23:25:13 +0200 From: Francois Romieu <romieu@...zoreil.com> To: Jonathan Larsen <agentc0re@...il.com> Cc: netdev@...r.kernel.org Subject: Re: Fwd: r8169 driver supporting the 8167 dev ID Jonathan Larsen <agentc0re@...il.com> : > I've been looking for the r8169 driver that is for the 2.6.x kernel > and also supports the device id 8167, 10ec. chipset is the 8110sc. > im sure someone is familiar with this. It is not the most used chipset in the 816x family but there are some known users, yes. > i noticed on the most latest kernel that such a driver exists. i > downloaded a gentoo live cd and found out. im trying to compile a > driver for a 2.6.16.52 kernel, it's for smoothwall. > i was hoping someone could help me out in getting the source so i > could compile it under the 2.6.16.52 kernel and have it work with my > 8110sc chipset nic's. The patchkit from 2.6.18 to (almost) current contains 47 patches. git is a wonderful tool for endless nights of S&M backporting but I'd appreciate to understand why you can not use a more recent kernel before engaging. > hope i've included enough info and description in what i am trying to > accomplish. i just hope it's possible. thank you! :) git format-patch v2.6.18..v2.6.23-rc1 -- drivers/net/r8169.c gives a good summary of the changes in the r8169 driver. One starts from a 2.6.16.something base and cycle through {apply/ignore}/compile/fix {reject/api change} for each patch until the r8169 driver reaches a decent state. It is not difficult but it takes time. -- Ueimor - 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
Powered by blists - more mailing lists