From: shampavman.cg@gmail.com (shampavman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Writing device drivers
Date: Wed, 12 Jun 2013 19:11:55 +0530 [thread overview]
Message-ID: <51B87AA3.3010108@gmail.com> (raw)
In-Reply-To: <CAK5mtezP3KEPh3ssDJErObzsYa6+326b0zb0ztYcPHNCmXVH6w@mail.gmail.com>
On 06/12/2013 07:06 PM, Victor Rodriguez wrote:
>
>
>
> On Wed, Jun 12, 2013 at 8:11 AM, shampavman <shampavman.cg@gmail.com
> <mailto:shampavman.cg@gmail.com>> wrote:
> Hi all,
>
> I've followed up LDD3 and started off with writing device drivers . As
> usual i've started with char drivers given in that book and also started
> to make minor modifications to learn it better and so on.
>
> Now i would like to know how to take it forward and start writing
> drivers for a profession.
> I know its too early to call myself a guy writing device drivers but how
> do i take if forward from here so that i can become one.
>
> Is the only solution to pick up a device which does not work on linux
> and get it working? Are there any other ways as well?
>
>
> Shampavman
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
> Hi Shampavman
>
> There are many ways to became a Linux Device Driver Developer.
>
> -> New Embedded platforms ; There are many platforms with none
> official Linux kernels ( came to my mind some with HDMI like DN2800MT)
I had to state my other problem here. Without actual hardware to work on
its not possible to do much right.
In such a scenario what can i do?
> -> Fix and test the current development kernel. Check on Bugzilla the
> thousands of bugs that haven't been fixed ( waiting for you )
>
here again the same thing, Unless I have the right hardware i dont know
what the heck works and what doesn't . Or is there another way to work
around this limitation?
> Hope it helps
>
> Regards
>
> Victor Rodriguez
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130612/acd36178/attachment-0001.html
next prev parent reply other threads:[~2013-06-12 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 13:11 Writing device drivers shampavman
2013-06-12 13:36 ` Victor Rodriguez
2013-06-12 13:41 ` shampavman [this message]
2013-06-17 6:53 ` Jonathan Paugh
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=51B87AA3.3010108@gmail.com \
--to=shampavman.cg@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).