linux-kernel - Re: Need help to understand and develop the 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-prev] [day] [month] [year] [list]

Message-ID: <20120413131621.GA11036@home.goodmis.org>
Date:	Fri, 13 Apr 2012 09:16:21 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Vishal Nandanwar <operational.people@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Need help to understand and develop the device drivers

On Fri, Apr 13, 2012 at 02:41:29PM +0530, Vishal Nandanwar wrote:
> Hi,
> 
> I am new in Linux device driver development. Currently I am learning
> drivers from the book "Linux device drivers" by Rubini. This book is
> quite big and quite boring. What are the ways to learn the drivers?

What are ways to learn the drivers? By reading really big and boring
books!

I read the "AMD64 Architecture Programmer's Manual Volume 2: System
Programming" from cover to cover. Now *that* was a boring read. But it
was required to be efficient at doing my job.

> 
> Do any one have any guide in video or PPT format or in any other format?
> 

You are obviously clueless to what you are doing. Most people here do
not even own Power Point, nor do they even run Windows (I don't). I'm
happy that Windows developers are interested in learning how to work
with Linux, but I'm disgusted at someone that doesn't want to put the
effort in to learn how to do it the correct way.

Kernel developing in not easy (this includes device drivers) and should
not be taken lightly such that you can start developing after reading
some silly PPT presentation.

If you don't `want to put in the effort to read a "big boring book" to
learn how to develop the correct way, we don't want you developing
drivers for our kernel. Because I can guarantee that your code will be
nothing more than shit.

-- Steve

PS. I don't want to discourage you. If you decide that what you just
asked was really silly, and you figure out that it does take an effort
to do kernel developing, then I welcome you with open arms.

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