From: kuldeepdhaka9@gmail.com (Kuldeep Singh Dhaka)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel Development
Date: Sun, 23 Feb 2014 23:49:00 +0530 [thread overview]
Message-ID: <530A3B94.90406@gmail.com> (raw)
In-Reply-To: <CAMQVM6o94p21BruTrFWdi3GhAyV7VucMxa5h11VQRpF5C=sr3A@mail.gmail.com>
On 02/23/2014 10:54 PM, subham soni wrote:
> Hello,
> I am a newbie to kernel development. I would like to develop my own
> kernel from scratch. From where should I start from?
developing you own Kernel. nice. i suggest you learn more about kernel
design and their role's. that will make you aware of how things work.
http://wiki.osdev.org/ (+ many more) will be your friends.
> I have a good experience of the commands in Linux
> (Ubuntu,Fedora,Debian,Slackware).
This would help you on your way. :)
> I googled out and I came to know that I should start from Device Drivers.
device drivers are for kernel's that are running.
if you want to make your own, you have to design a infrastructure for
drivers to place.
> Now which device driver should I code?
if you are thinking of starting from Linux source, give it a try :p.
/dev/null is an excellent example to start.
> Or should I master Shell Scripting?
depends on type of work, but i think basic things like Makefile,
compiling from shell, and doing echo work should be ok (at minimum).
> For developing a kernel (my aim here would be to increase the battery
> life, since most laptops have only 1.30 hrs or 2.00 hrs in Linux OS)
> and 3.00 hrs in Windows Environment. How should I start and from where?
all i can say is:
learn more about low power thingi'es so that you can re iterate on what
your asking.
Linux OS -> GNU/Linux OS GNU userland utilities/applications with
Linux Kernel :)
summary:
learn more about kernel design,
how they work,
decide hardware to bake on.
read hardware document
learn from others kernel
VM will be handy. (qemu, ...)
patience <--- important
be ready for hiccup's
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
*Kuldeep Singh Dhaka*
+91-8791676237
Programmer, Open Source, Embedded System, Entrepreneur, System
Administrator, Animal Lover, Web Developer, Learner.
My GnuPG Public Key
<http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x23816C5609DC7E26>
Fork Me <http://github.com/kuldeepdhaka>
Bitcoins Accepted.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140223/b7a41f49/attachment.html
next prev parent reply other threads:[~2014-02-23 18:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 17:24 Kernel Development subham soni
2014-02-23 18:19 ` Kuldeep Singh Dhaka [this message]
2014-02-23 23:35 ` John de la Garza
2014-02-24 1:13 ` freeman
2014-02-24 4:36 ` Pranay Srivastava
2014-02-24 5:44 ` subham soni
2014-02-24 5:49 ` Manish Katiyar
2014-02-24 6:08 ` priyaranjan
2014-02-24 6:44 ` subham soni
2014-02-24 9:45 ` Anuz Pratap Singh Tomar
2014-02-24 17:57 ` Valdis.Kletnieks at vt.edu
2014-02-25 4:51 ` rakesh Bhaskar
2020-03-29 12:27 Harsh chopra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=530A3B94.90406@gmail.com \
--to=kuldeepdhaka9@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).