netdev - How come realtek drivers are combined

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-next>] [day] [month] [year] [list]

Date:	Thu, 26 Jun 2008 18:16:42 -0500
From:	Mario Limonciello <mario_limonciello@...l.com>
To:	netdev@...r.kernel.org
Subject: How come realtek drivers are combined

Hi:

I'm new to the list but didn't immediately see an answer to this in
quick searches.

Realtek provides several (separated) drivers for their different
chipsets, r8169, r8168, r8101, etc. I see that they are regularly all
merged into the r8169 driver in the kernel.  How come it works this
way?  Is it just because no one ever bothered to do it differently? 
Obviously, they all share a very similar code base so its somewhat
sensible to try to produce a single driver.  I would think it would work
a lot better for everyone if Realtek and the kernel maintainers that
work on the Realtek driver were directly in sync rather than having to
play tag pulling patches from each other's drivers.

Thanks,
-- 
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@...l.com

Download attachment "signature.asc" of type "application/pgp-signature" (253 bytes)