From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>,
"halil.karabacak" <halil.karabacak@boun.edu.tr>
Cc: Linux arm msm <linux-arm-msm@vger.kernel.org>
Subject: Re: Using CCI_I2C Driver for OV9282 on Qualcomm RB5 Vision Kit
Date: Thu, 8 Sep 2022 01:37:29 +0100 [thread overview]
Message-ID: <4cd73207-eff9-2f72-fabd-da3ed3a9f6bd@linaro.org> (raw)
In-Reply-To: <166258721180.2677993.14675525254961646895@Monstersaurus>
On 07/09/2022 22:46, Kieran Bingham wrote:
> Hi Bryan,
>
> Quoting Bryan O'Donoghue (2022-09-07 17:03:51)
>> On 24/08/2022 14:34, Bryan O'Donoghue wrote:
>>> On 24/08/2022 12:08, halil.karabacak wrote:
>>>> After some trials and errors, I achieved something but, are these
>>>> resolutions in the attached file correct? And I could read nothing
>>>> from the camera right now.
>>>> Regards,
>>>> Halil
>>>
>>> They don't look right.
>>>
>>> Are you trying with the imx577 or the ov9282 ?
>>
>> So I had a poke at the ov9282 today.
>>
>> ov9282 is detected on this branch here.
>>
>> https://git.linaro.org/people/bryan.odonoghue/kernel.git/log/?h=linux-stable-22-08-01-imx577-camss
>>
>> libcamera can't eat Y10P though
>> [1]
>
> Hrm - it should 'now'.
>
> It was originally added in [2] in November last year - but the
> corresponding V4L2 entry [3] was missed. It's been added last month, so
> should work now. Please let us know if it still causes you issues.
>
> [2] https://git.libcamera.org/libcamera/libcamera.git/commit/?id=9e3470ad3e4f03364c8160917117d62fde5a7d88
> [3] https://git.libcamera.org/libcamera/libcamera.git/commit/?id=26c82ce13697e1af5950f4935ecff83c6453f351
>
> --
> Kieran
Ah NICE
linaro@linaro-gnome:~/libcamera/build/src/cam$ git show
commit 6225d647b47982833fa654bf9cf65eb8c04d2036 (HEAD -> master,
origin/master, origin/HEAD)
Author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Date: Sat Sep 3 17:44:00 2022 +0300
Available cameras:
1: 'ov9282' (/base/soc@0/cci@ac4f000/i2c-bus@1/camera@60)
2: 'imx412' (/base/soc@0/cci@ac50000/i2c-bus@0/camera@1a)
---
bod
prev parent reply other threads:[~2022-09-08 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:25 Using CCI_I2C Driver for OV9282 on Qualcomm RB5 Vision Kit halil.karabacak
2022-08-23 13:42 ` Bryan O'Donoghue
[not found] ` <1ecd2058040c8e087ab1e0c34d3aac2d@boun.edu.tr>
[not found] ` <69bdc9d7b5556575bf38cc6adc100e4a@boun.edu.tr>
2022-08-24 13:34 ` Bryan O'Donoghue
2022-09-07 16:03 ` Bryan O'Donoghue
[not found] ` <166258721180.2677993.14675525254961646895@Monstersaurus>
2022-09-08 0:37 ` Bryan O'Donoghue [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=4cd73207-eff9-2f72-fabd-da3ed3a9f6bd@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=halil.karabacak@boun.edu.tr \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-arm-msm@vger.kernel.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