| 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: <87y4wivujg.fsf@tassilo.jf.intel.com> Date: Fri, 27 Jun 2014 15:48:03 -0700 From: Andi Kleen <andi@...stfloor.org> To: Nawn Given <wood.quinn.s@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Writing Device Drivers Nawn Given <wood.quinn.s@...il.com> writes: > I recently read some post-commentary on very old Linux mailing list > messages (announcement to 0.96.) > > I'm interested in how someone writes a driver for their hardware. What > is the process (or if it's become harder to explain since the early > 90s, what was the process back then) for Linux? 1. Open editor 2. Type code 3. Test code 4. Repeat until code works. No substantial change since 0.96 as far as I know. -Andi -- ak@...ux.intel.com -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists