From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Ashwin Kirpalani <akcooper8@gmail.com>
Subject: Re: Potential patch for ov2640 with imx6
Date: Mon, 20 May 2013 07:04:19 -0700 [thread overview]
Message-ID: <519A2D63.7010506@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKqFH76wn8vedi9FH3yRpvpnXBO8ttwpdjEs=e_1fFkUHA@mail.gmail.com>
On 05/20/2013 04:56 AM, Otavio Salvador wrote:
>> On Mon, May 20, 2013 at 7:43 AM, Gary Thomas <gary@mlbassoc.com
>> <mailto:gary@mlbassoc.com>> wrote:
>> On 2013-05-19 13:47, Ashwin Kirpalani wrote:
>>
>> I have a ov2640 camera which did not work out of the box with
>> the ov2640.c mxc v4l2 driver in the linux-imx kernel. I have a
>> patch for it to work with i.mx6. My board is the
>> sabrelite Would you accept it and is this the right place to
>> submit it?
>>
>>
>> What MACHINE are you using? It seems that the 'imx6qsabrelite' MACHINE
>> is deprecated and you should use 'nitrogen6x' from meta-fsl-arm-extra
>> This will use the Boundary Devices kernel which may already have the
>> change you are looking for.
>>
>>
> In fact, currently, both are using the kernel. That's the reason we
> moved it to -extra layer in dylan.
>
And it doesn't have support for the OV2640.
The kernel tree is the right place to merge the patch.
Ashwin, if you forward the patch to me and if it looks clean,
we'll be happy to include it in our tree. We probably won't
want to include it in the default kernel configuration, since
it's clearly not widely used.
Are you using another KLT camera module for the OV2640?
How difficult is it to glue up to the SABRE Lite/Nitrogen6X?
Please advise,
Eric
prev parent reply other threads:[~2013-05-20 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 19:47 Potential patch for ov2640 with imx6 Ashwin Kirpalani
2013-05-19 20:02 ` Otavio Salvador
2013-05-20 10:43 ` Gary Thomas
2013-05-20 11:56 ` Otavio Salvador
2013-05-20 14:04 ` Eric Nelson [this message]
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=519A2D63.7010506@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=akcooper8@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.