From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: "Alexandre-Xavier Labonté-Lamoureux" <axdoomer@gmail.com>,
linux-media@vger.kernel.org,
"Guennadi Liakhovetski" <g.liakhovetski@gmx.de>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>
Subject: Re: Bug: Two device nodes created in /dev for a single UVC webcam
Date: Mon, 19 Feb 2018 13:52:04 +0000 [thread overview]
Message-ID: <dd70c226-e7db-e55e-e467-a6b0d1e7849d@ideasonboard.com> (raw)
In-Reply-To: <CAKTMqxtRQvZqZGQ0oWSf79b3ZGs6Stpctx9yqi8X1Myq-CY2JA@mail.gmail.com>
Hi Alexandre,
Thankyou for your bug report,
On 17/02/18 20:47, Alexandre-Xavier Labonté-Lamoureux wrote:
> Hi,
>
> I'm running Linux 4.9.0-5-amd64 on Debian. I built the drivers from
> the latest git and installed the modules.
Could you please be specific here?
Are you referring to linux-media/master branch or such? The latest from Linus' tree?
Please also detail the steps you have taken to reproduce this issue - and of
course - if you have made any code changes to make the latest UVC module compile
against a v4.9 kernel...
Building the latest git tree and installing as a module on a v4.9 kernel is
quite a leap... I wouldn't have expected that to work.
The code would have to be compiled against a v4.9 kernel directly, and I didn't
think compiling the UVC driver against older kernels worked.
(at least it didn't work cleanly when I tried to compile v4.15 against a v4.14
kernel last month)
> Now, two device nodes are
> created for my webcam. This is not normal as it has never happened to
> me before. If I connect another webcam to my laptop, two more device
> nodes will be created for this webcam. So two new device nodes are
> created for a single webcam.
I believe Guennadi's latest work for handling meta-data (in the latest v4.16-rc1
I think) will create two device nodes.
> The name of my webcam appears twice in the device comobox in Guvcview
> because of this. One of them will not work if I select it.
It would be expected that only the device with video functions as a streaming
camera device, while the other would not.
> My webcam has completely stopped working with Cheese and VLC.
This part is of particular concern however.
Guennadi - Have you tested Cheese/VLC with your series?
Are there any known issues that need looking at ?
>> v4l2-ctl --list-devices
> Laptop_Integrated_Webcam_E4HD: (usb-0000:00:1a.0-1.5):
> /dev/video0
> /dev/video1
>
>> ls /dev/video*
> /dev/video0 /dev/video1
>
> Have a nice day,
> Alexandre-Xavier
Regards
Kieran Bingham
next prev parent reply other threads:[~2018-02-19 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 20:47 Bug: Two device nodes created in /dev for a single UVC webcam Alexandre-Xavier Labonté-Lamoureux
2018-02-19 13:52 ` Kieran Bingham [this message]
2018-02-19 13:58 ` Guennadi Liakhovetski
2018-02-19 16:19 ` Laurent Pinchart
2018-02-20 18:18 ` Devin Heitmueller
2018-02-20 23:54 ` Laurent Pinchart
2018-02-19 17:29 ` Alexandre-Xavier Labonté-Lamoureux
2018-02-19 19:10 ` Laurent Pinchart
2018-02-25 8:19 ` Alexandre-Xavier Labonté-Lamoureux
2018-02-25 11:41 ` Laurent Pinchart
2018-03-05 2:55 ` Alexandre-Xavier Labonté-Lamoureux
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=dd70c226-e7db-e55e-e467-a6b0d1e7849d@ideasonboard.com \
--to=kieran.bingham@ideasonboard.com \
--cc=axdoomer@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@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