linux-kernel - Writing Device Drivers

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]

Message-ID: <CAM83q7BgHSUs5RyWQat_z4O=1sGgecOUb11jAxkun4JSUOe-cg@mail.gmail.com>
Date:	Fri, 27 Jun 2014 16:54:20 -0500
From:	Nawn Given <wood.quinn.s@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Writing Device Drivers

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?
--
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/