linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media@vger.kernel.org
Subject: Re: Kernel error "Unknown pixelformat 0x00000000" occurs when I start capture video
Date: Wed, 9 Jan 2019 10:03:12 -0200	[thread overview]
Message-ID: <20190109100312.02a725d8@coco.lan> (raw)
In-Reply-To: <CABXGCsPJJfu7fwVnx3ovHTDF-rBFrUqmc7dqF+R-Q-NE2vmn5w@mail.gmail.com>

Em Wed, 9 Jan 2019 08:51:29 +0500
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com> escreveu:

> I upgraded kernel to 5.0 rc1 and the error message  "Unknown
> pixelformat 0x00000000" are disappeared.
> 
> Instead I see not obvious message "uvcvideo: Non-zero status (-71) in
> video completion handler."

This is unrelated. Usually, you get -71 errors when there's a problem
with usb cabling. This is what it means:

	#define	EPROTO		71	/* Protocol error */

From Documentation/driver-api/usb/error-codes.rst:

``-EPROTO`` [#f1]_, [#f2]_	a) bitstuff error
				b) no response packet received within the
				   prescribed bus turn-around time
				c) unknown USB error

> Maybe in this case better to write "Video format XXX not supported" ?

The message about the lack of support for P010 is still there:

	[    5.218031] uvcvideo: Unknown video format 30313050-0000-0010-8000-00aa00389b71

The best solution would be to really convert this into something that
applications can benefit, e. g. exporting the P010 format to userspace.

> It would help quickly understand that is culprit here.
> 
> 
> --
> Best Regards,
> Mike Gavrilov.



Thanks,
Mauro

  reply	other threads:[~2019-01-09 12:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05 20:05 Kernel error "Unknown pixelformat 0x00000000" occurs when I start capture video Mikhail Gavrilov
2019-01-08 14:45 ` Mauro Carvalho Chehab
2019-01-08 14:54   ` Laurent Pinchart
2019-01-08 15:16     ` Mauro Carvalho Chehab
2019-01-08 15:55       ` Laurent Pinchart
2019-01-08 15:18     ` Mikhail Gavrilov
2019-01-08 15:58       ` Laurent Pinchart
2019-01-08 16:11         ` Mikhail Gavrilov
2019-01-08 18:49           ` Mauro Carvalho Chehab
2019-01-08 19:00             ` Mauro Carvalho Chehab
2019-01-09  3:51               ` Mikhail Gavrilov
2019-01-09 12:03                 ` Mauro Carvalho Chehab [this message]
2019-01-08 21:29             ` Laurent Pinchart
2019-01-09 12:19             ` Sakari Ailus
2019-01-09 13:01               ` P010 fourcc format support - Was: " Mauro Carvalho Chehab
2019-01-09 16:42                 ` Ayaka
2019-01-09 16:52                   ` Nicolas Dufresne
2019-01-09 17:28                     ` Mauro Carvalho Chehab
2019-01-09 18:20                       ` Nicolas Dufresne

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=20190109100312.02a725d8@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mikhail.v.gavrilov@gmail.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;
as well as URLs for NNTP newsgroup(s).