From: Andreas Kemnade <andreas@kemnade.info>
To: Unknown <devnull@uvos.xyz>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-omap@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH] media: staging: drop omap4iss
Date: Thu, 21 Nov 2024 17:21:19 +0100 [thread overview]
Message-ID: <20241121172119.4b46727e@akair> (raw)
In-Reply-To: <1aa03cb201857f70bc46143a16465f0a08870401.camel@uvos.xyz>
Am Thu, 21 Nov 2024 12:40:37 +0100
schrieb Unknown <devnull@uvos.xyz>:
> Hi,
>
> > BT200 has a camera without mainline sensor driver.
> > Droid4 has also a camera. What is the status of the sensor driver?
> > What about the samsung-espresso tablets? And the xyboards?
>
> Same as your device droid4 and xyboard handle the camera via m3
> firmware.
> The droid 4's rear camera is totaly unkown with no datasheed or open
> source driver known to exist.
that page suggests that there is an open source driver for the
rear camera:
https://elektranox.org/2018/02/0025-droid-camera/
Quoting:
https://searchcode.com/file/50297519/drivers/media/video/msm/sensors/ov8820_v4l2.c
BTW:
Bt200 has OV7692
> The front camera has avaialble datasheed and out of tree driver.
> The xyboards cary the same sensor as the d4's rear module.
>
> We (maemo leste, a distro that has put considerable effort into
> bringing up the droid 4, droid bionic and xyboard) do hope to
> eventually bring up the front camera on the droid, as all the
> componants for this are floating around, but are currenly not working
> on this issue.
>
So summary:
there are potential real users of omap4-iss. Apparently all of them
require besides a working a omap4-iss to work on some sensor driver to
have something useful.
If omap4-iss would be known-working there are probably better chances
that more jump in.
Regards,
Andreas
prev parent reply other threads:[~2024-11-21 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <815a789d-85a5-44a1-8b9c-429ac0101e3f@xs4all.nl>
2024-11-18 19:00 ` [PATCH] media: staging: drop omap4iss Andreas Kemnade
2024-11-19 7:02 ` Laurent Pinchart
2024-11-20 7:54 ` Andreas Kemnade
2024-11-20 8:39 ` Laurent Pinchart
2024-11-21 10:27 ` Andreas Kemnade
2024-11-21 10:52 ` H. Nikolaus Schaller
2024-11-21 11:12 ` H. Nikolaus Schaller
2024-11-21 11:40 ` Unknown
2024-11-21 16:21 ` Andreas Kemnade [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=20241121172119.4b46727e@akair \
--to=andreas@kemnade.info \
--cc=devnull@uvos.xyz \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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