From: Carl Karsten <carl@nextdayvideo.com>
To: linux-amlogic@lists.infradead.org
Subject: v4l error on stretch c2
Date: Thu, 11 Apr 2019 01:16:13 -0500 [thread overview]
Message-ID: <CADmzSSj+dm6siBGP-LPzJ=i1pZU3vK7z-VsR4Qf6HT2yu8Z-6Q@mail.gmail.com> (raw)
I'm getting errors reading a uvc video stream:
Linux odroid3 4.19.20-meson64 #5.75 SMP PREEMPT Fri Feb 8 10:08:40 CET
2019 aarch64 GNU/Linux
gst-launch-1.0 v4l2src device=/dev/hdmi2usb/by-num/all0/video ! fakesink
error: XDG_RUNTIME_DIR not set in the environment.
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could
not read from resource.
Additional debug info:
gstv4l2bufferpool.c(1058): gst_v4l2_buffer_pool_poll ():
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
poll error 1: Invalid argument (22)
Execution ended after 0:00:18.608430528
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...
gst-launch-1.0 v4l2src device=/dev/hdmi2usb/by-num/all0/video ! fakesink
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Device
'/dev/hdmi2usb/by-num/all0/video' is not a capture device.
Additional debug info:
v4l2_calls.c(633): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
Capabilities: 0x4a00000
Setting pipeline to NULL ...
Freeing pipeline ...
--
Carl K
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-04-11 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 6:16 Carl Karsten [this message]
2019-04-11 15:25 ` v4l error on stretch c2 Carl Karsten
2019-04-11 17:27 ` Nicolas Dufresne
2019-04-11 18:08 ` Carl Karsten
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='CADmzSSj+dm6siBGP-LPzJ=i1pZU3vK7z-VsR4Qf6HT2yu8Z-6Q@mail.gmail.com' \
--to=carl@nextdayvideo.com \
--cc=linux-amlogic@lists.infradead.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).