From: rfabbri@gmail.com (Ricardo Fabbri)
To: kernelnewbies@lists.kernelnewbies.org
Subject: linux camera drivers
Date: Sat, 3 Mar 2012 01:51:31 -0300 [thread overview]
Message-ID: <CACjTMEyp2ZhOKKYDM-H5a-AVtAeX4FGGWHWSjWe0fbdQ4r9Dsw@mail.gmail.com> (raw)
In-Reply-To: <20120301145213.GA6403@kroah.com>
>> 3.Are there any tutorials/pdfs to understand camera drivers in linux kernel.
>
> What is wrong with the code itself?
>
Please provide a more thoughtful answer. At least say if that's your
tried-and-true approach or if it's a suggestion to look into the code.
Ricardo.
next prev parent reply other threads:[~2012-03-03 4:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 12:27 linux camera drivers Mayank Agarwal
2012-03-01 14:52 ` Greg KH
[not found] ` <CAKjpqyJJzEekx4C3RfVBecjY7oictgWts+EVRhQNjsCJ_4d80Q@mail.gmail.com>
2012-03-03 4:21 ` Mayank Agarwal
2012-03-03 5:03 ` Greg KH
2012-03-05 8:46 ` Prabhakar Lad
2012-03-07 2:34 ` Chetan Nanda
2012-03-03 4:51 ` Ricardo Fabbri [this message]
2012-03-03 5:03 ` Greg KH
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=CACjTMEyp2ZhOKKYDM-H5a-AVtAeX4FGGWHWSjWe0fbdQ4r9Dsw@mail.gmail.com \
--to=rfabbri@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).