From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sophie Friedrich <lkml@flowerpot.me>
Cc: Jacopo Mondi <jacopo@jmondi.org>,
Pekka Paalanen <ppaalanen@gmail.com>,
linux-media@vger.kernel.org, libcamera-devel@lists.libcamera.org
Subject: Re: Potential integration of thermal cameras into v4l
Date: Tue, 10 Jan 2023 15:50:23 +0200 [thread overview]
Message-ID: <Y71tH5ZQT45MhHka@pendragon.ideasonboard.com> (raw)
In-Reply-To: <aa5ee8a1-e6cb-5573-8aa0-f583227cabcf@flowerpot.me>
Hi Sophie,
On Tue, Jan 10, 2023 at 02:33:17PM +0100, Sophie Friedrich wrote:
> Hello,
>
> Yeah the link was broken before, but I already fixed it. I'm not
> sure if my reply actually reached the mailing list (it accidentally
> mixed up my sending adress). At least from the libcamera I got a
> bounce, as I'm not a member.
I've accepted both e-mails manually, and added the two addresses to the
approved senders.
> On 10/01/2023 14:13, Laurent Pinchart wrote:
> > Sophie, could you please share the `lsusb -v` output for the device (you
> > can limit it to a specific device with `-d VID:PID`), running as root
> > (e.g. with `sudo`) if possible ?
>
> Note here that the idVendor and iManufacturer do not match. The
> camera uses the same USB VID:PID as the Netchip "Gadget Zero", because
> of course it does…
Of course... Thank you for the descriptors, even if they make me want to
cry...
> $ sudo lsusb -v -d 0525:a4a0
> Bus 001 Device 019: ID 0525:a4a0 Netchip Technology, Inc. Linux-USB
> "Gadget Zero"
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.01
> bDeviceClass 0
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x0525 Netchip Technology, Inc.
> idProduct 0xa4a0 Linux-USB "Gadget Zero"
> bcdDevice 2.00
> iManufacturer 1 Wuhan Guide Infrared Co., Ltd.
> iProduct 2 MobIR Air
> iSerial 3 ZX01A19
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 0x0040
> bNumInterfaces 2
> bConfigurationValue 1
> iConfiguration 4 MFI Configure
> bmAttributes 0xc0
> Self Powered
> MaxPower 100mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 240
> bInterfaceProtocol 0
> iInterface 5 iAP Interface
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x82 EP 2 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 1
> bAlternateSetting 0
> bNumEndpoints 0
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 240
> bInterfaceProtocol 1
> iInterface 6 com.guidesensmart.mobir-air
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 1
> bAlternateSetting 1
> bNumEndpoints 2
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 240
> bInterfaceProtocol 1
> iInterface 6 com.guidesensmart.mobir-air
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x01 EP 1 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 0
> Binary Object Store Descriptor:
> bLength 5
> bDescriptorType 15
> wTotalLength 0x000c
> bNumDeviceCaps 1
> USB 2.0 Extension Device Capability:
> bLength 7
> bDescriptorType 16
> bDevCapabilityType 2
> bmAttributes 0x00000002
> HIRD Link Power Management (LPM) Supported
> Device Status: 0x0001
> Self Powered
>
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2023-01-10 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 21:58 Potential integration of thermal cameras into v4l Sophie Friedrich
2023-01-10 8:46 ` Pekka Paalanen
2023-01-10 11:45 ` Jacopo Mondi
2023-01-10 12:14 ` Sophie Tyalie
2023-01-10 13:13 ` Laurent Pinchart
2023-01-10 13:33 ` Sophie Friedrich
2023-01-10 13:50 ` Laurent Pinchart [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=Y71tH5ZQT45MhHka@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=jacopo@jmondi.org \
--cc=libcamera-devel@lists.libcamera.org \
--cc=linux-media@vger.kernel.org \
--cc=lkml@flowerpot.me \
--cc=ppaalanen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.