<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[radxa zero 3e, debian, linux 5.10, imx287: Inappropriate ioctl for device]]></title><description><![CDATA[<p dir="auto">Hi, I'm trying to use imx287 on radxa zero 3e using the same C code I successfully used for rpi zero 2w:</p>
<pre><code class="language-cpp">...
int fd = open("/dev/video0", O_RDWR);
...
int camIdx = 0;
int input = camIdx;
int ret = ioctl(m_cam_fd, VIDIOC_S_INPUT, &amp;input);
// ret &lt; 0: strerror(errno) == "Inappropriate ioctl for device"
</code></pre>
<p dir="auto">Could you please tell if I'm missing something?<br />
Do I need to select different device or VIDIOC_S_INPUT argument?</p>
<p dir="auto">After selecting the camera, I was going to use the same approach which worked for rpi zero 2w: <code>VIDIOC_TRY_FMT</code>/<code>VIDIOC_S_FMT</code>/<code>VIDIOC_REQBUFS</code>/<code>VIDIOC_QUERYBUF</code>/<code>VIDIOC_QBUF</code>/<code>VIDIOC_DQBUF</code>, is it possible? Does driver support this?</p>
<p dir="auto">I'm able to set cam params using <code>mv_mipi_i2c_new.sh</code> and it works (I set different <code>metime</code> values - and I see that laser (connected to cam output) brightness is changing)</p>
<pre><code class="language-sh">v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null
</code></pre>
<pre><code class="language-sh">./i2c_tools$ sudo ./mv_mipi_i2c_new.sh -b 2 -w metime 18
./i2c_tools$ sudo ./mv_mipi_i2c_new.sh -b 2 -w metime 180
</code></pre>
<pre><code class="language-sh">$ media-ctl -p -d /dev/media0
Media controller API version 5.10.160

Media device information
------------------------
driver          rkcif
model           rkcif_mipi_lvds
serial          
bus info        
hw revision     0x0
driver version  5.10.160

Device topology
- entity 1: stream_cif_mipi_id0 (1 pad, 4 links)
            type Node subtype V4L flags 0
            device node name /dev/video0
	pad0: Sink
		&lt;- "rockchip-mipi-csi2":1 [ENABLED]
		&lt;- "rockchip-mipi-csi2":2 []
		&lt;- "rockchip-mipi-csi2":3 []
		&lt;- "rockchip-mipi-csi2":4 []

- entity 5: stream_cif_mipi_id1 (1 pad, 4 links)
            type Node subtype V4L flags 0
            device node name /dev/video1
	pad0: Sink
		&lt;- "rockchip-mipi-csi2":1 []
		&lt;- "rockchip-mipi-csi2":2 [ENABLED]
		&lt;- "rockchip-mipi-csi2":3 []
		&lt;- "rockchip-mipi-csi2":4 []

- entity 9: stream_cif_mipi_id2 (1 pad, 4 links)
            type Node subtype V4L flags 0
            device node name /dev/video2
	pad0: Sink
		&lt;- "rockchip-mipi-csi2":1 []
		&lt;- "rockchip-mipi-csi2":2 []
		&lt;- "rockchip-mipi-csi2":3 [ENABLED]
		&lt;- "rockchip-mipi-csi2":4 []

- entity 13: stream_cif_mipi_id3 (1 pad, 4 links)
             type Node subtype V4L flags 0
             device node name /dev/video3
	pad0: Sink
		&lt;- "rockchip-mipi-csi2":1 []
		&lt;- "rockchip-mipi-csi2":2 []
		&lt;- "rockchip-mipi-csi2":3 []
		&lt;- "rockchip-mipi-csi2":4 [ENABLED]

- entity 17: rkcif_tools_id0 (1 pad, 4 links)
             type Node subtype V4L flags 0
             device node name /dev/video4
	pad0: Sink
		&lt;- "rockchip-mipi-csi2":1 []
		&lt;- "rockchip-mipi-csi2":2 []
		&lt;- "rockchip-mipi-csi2":3 []
		&lt;- "rockchip-mipi-csi2":4 []

- entity 21: rkcif_tools_id1 (1 pad, 4 links)
             type Node subtype V4L flags 0
             device node name /dev/video5
	pad0: Sink
		&lt;- "rockchip-mipi-csi2":1 []
		&lt;- "rockchip-mipi-csi2":2 []
		&lt;- "rockchip-mipi-csi2":3 []
		&lt;- "rockchip-mipi-csi2":4 []

- entity 25: rkcif_tools_id2 (1 pad, 4 links)
             type Node subtype V4L flags 0
             device node name /dev/video6
	pad0: Sink
		&lt;- "rockchip-mipi-csi2":1 []
		&lt;- "rockchip-mipi-csi2":2 []
		&lt;- "rockchip-mipi-csi2":3 []
		&lt;- "rockchip-mipi-csi2":4 []

- entity 29: rkcif-mipi-luma (0 pad, 0 link)
             type Node subtype V4L flags 0
             device node name /dev/video7

- entity 32: rockchip-mipi-csi2 (5 pads, 29 links)
             type V4L2 subdev subtype Unknown flags 0
             device node name /dev/v4l-subdev0
	pad0: Sink
		[fmt:Y8_1X8/704x544 field:none
		 crop.bounds:(0,0)/704x544
		 crop:(0,0)/704x544]
		&lt;- "rockchip-csi2-dphy0":1 [ENABLED]
	pad1: Source
		-&gt; "stream_cif_mipi_id0":0 [ENABLED]
		-&gt; "stream_cif_mipi_id1":0 []
		-&gt; "stream_cif_mipi_id2":0 []
		-&gt; "stream_cif_mipi_id3":0 []
		-&gt; "rkcif_tools_id0":0 []
		-&gt; "rkcif_tools_id1":0 []
		-&gt; "rkcif_tools_id2":0 []
	pad2: Source
		-&gt; "stream_cif_mipi_id0":0 []
		-&gt; "stream_cif_mipi_id1":0 [ENABLED]
		-&gt; "stream_cif_mipi_id2":0 []
		-&gt; "stream_cif_mipi_id3":0 []
		-&gt; "rkcif_tools_id0":0 []
		-&gt; "rkcif_tools_id1":0 []
		-&gt; "rkcif_tools_id2":0 []
	pad3: Source
		-&gt; "stream_cif_mipi_id0":0 []
		-&gt; "stream_cif_mipi_id1":0 []
		-&gt; "stream_cif_mipi_id2":0 [ENABLED]
		-&gt; "stream_cif_mipi_id3":0 []
		-&gt; "rkcif_tools_id0":0 []
		-&gt; "rkcif_tools_id1":0 []
		-&gt; "rkcif_tools_id2":0 []
	pad4: Source
		-&gt; "stream_cif_mipi_id0":0 []
		-&gt; "stream_cif_mipi_id1":0 []
		-&gt; "stream_cif_mipi_id2":0 []
		-&gt; "stream_cif_mipi_id3":0 [ENABLED]
		-&gt; "rkcif_tools_id0":0 []
		-&gt; "rkcif_tools_id1":0 []
		-&gt; "rkcif_tools_id2":0 []

- entity 38: rockchip-csi2-dphy0 (2 pads, 2 links)
             type V4L2 subdev subtype Unknown flags 0
             device node name /dev/v4l-subdev1
	pad0: Sink
		[fmt:Y8_1X8/704x544@100/52300 field:none]
		&lt;- "m00_b_mvcam 2-003b":0 [ENABLED]
	pad1: Source
		-&gt; "rockchip-mipi-csi2":0 [ENABLED]

- entity 43: m00_b_mvcam 2-003b (1 pad, 1 link)
             type V4L2 subdev subtype Sensor flags 0
             device node name /dev/v4l-subdev2
	pad0: Source
		[fmt:Y8_1X8/704x544@100/52300 field:none]
		-&gt; "rockchip-csi2-dphy0":0 [ENABLED]

</code></pre>
]]></description><link>http://forum.veye.cc/topic/710/radxa-zero-3e-debian-linux-5-10-imx287-inappropriate-ioctl-for-device</link><generator>RSS for Node</generator><lastBuildDate>Fri, 04 Sep 2026 13:55:29 GMT</lastBuildDate><atom:link href="http://forum.veye.cc/topic/710.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 10 Nov 2025 23:19:18 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to radxa zero 3e, debian, linux 5.10, imx287: Inappropriate ioctl for device on Wed, 12 Nov 2025 01:20:40 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nkos" aria-label="Profile: nkos">@<bdi>nkos</bdi></a> Cheers!</p>
]]></description><link>http://forum.veye.cc/post/4946</link><guid isPermaLink="true">http://forum.veye.cc/post/4946</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Wed, 12 Nov 2025 01:20:40 GMT</pubDate></item><item><title><![CDATA[Reply to radxa zero 3e, debian, linux 5.10, imx287: Inappropriate ioctl for device on Tue, 11 Nov 2025 21:28:31 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/veye_xumm" aria-label="Profile: veye_xumm">@<bdi>veye_xumm</bdi></a>, thanks a lot, <code>yavta</code> example helped, I can receive images now, topic is resolved</p>
<p dir="auto">There are diffirences between <code>rpi</code> and <code>radxa</code>: buffer format, image packing and setting params (I can use approach from <code>i2cwrite.c</code>)</p>
<p dir="auto">Both my code and <code>yavta</code> are not able to do some things I can do on rpi (e.g. <code>VIDIOC_S_INPUT</code>), but it seems I can use camera without them</p>
]]></description><link>http://forum.veye.cc/post/4945</link><guid isPermaLink="true">http://forum.veye.cc/post/4945</guid><dc:creator><![CDATA[nkos]]></dc:creator><pubDate>Tue, 11 Nov 2025 21:28:31 GMT</pubDate></item><item><title><![CDATA[Reply to radxa zero 3e, debian, linux 5.10, imx287: Inappropriate ioctl for device on Tue, 11 Nov 2025 01:24:28 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nkos" aria-label="Profile: nkos">@<bdi>nkos</bdi></a><br />
Below is a tutorial on using this camera module on Radxa boards.<br />
<a href="https://wiki.veye.cc/index.php/MV_Camera_on_Radxa_Boards" rel="nofollow ugc">https://wiki.veye.cc/index.php/MV_Camera_on_Radxa_Boards</a></p>
<p dir="auto">Unlike the Raspberry Pi platform, on RK platforms, some preparatory work is required to use our module, which involves configuring the appropriate image parameters using <code>media-ctl</code>.<br />
However, based on the information you provided, it seems you have already set it up correctly.</p>
<p dir="auto">Once this preparation is complete, the process of capturing images is the same as on the Raspberry Pi.</p>
<p dir="auto">If you encounter any issues, you can refer to the code example at:<br />
<a href="https://wiki.veye.cc/index.php/MV_Camera_on_Radxa_Boards#Example_of_yavta" rel="nofollow ugc">https://wiki.veye.cc/index.php/MV_Camera_on_Radxa_Boards#Example_of_yavta</a></p>
<p dir="auto">Additionally, we have an open-source client software available for your use and reference.</p>
<p dir="auto"><a href="https://github.com/veyeimaging/veye_viewer" rel="nofollow ugc">https://github.com/veyeimaging/veye_viewer</a></p>
]]></description><link>http://forum.veye.cc/post/4944</link><guid isPermaLink="true">http://forum.veye.cc/post/4944</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Tue, 11 Nov 2025 01:24:28 GMT</pubDate></item></channel></rss>