[GIT PULL FOR v5.3] Various fixes/improvements
The following changes since commit 3a959dcd11a4b1f55bbb4a37d3bac685c4e106b1:
media: mt9m111: add regulator support (2019-06-21 17:56:39 -0400)
are available in the Git repository at:
git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.3s
for you to fetch changes up to 0fda628d1a97aec51e2120115f1a2adb7c56be5e:
hdpvr: fix locking and a missing msleep (2019-06-22 09:31:00 +0200)
Tag branch
André Almeida (1):
media: vimc: cap: check v4l2_fill_pixfmt return value
Boris Brezillon (1):
media: v4l2: Test type instead of cfg->type in v4l2_ctrl_new_custom()
Dmitry Osipenko (2):
staging: media: tegra-vde: Add IOMMU support
staging: media: tegra-vde: Defer dmabuf's unmapping
Eugen Hristev (1):
media: atmel: atmel-isc: fix i386 build error
Ezequiel Garcia (2):
media: hantro: Use vb2_get_buffer
media: v4l2-ctrl: Move compound control initialization
Hans Verkuil (2):
media/pci: set device_caps in struct video_device
hdpvr: fix locking and a missing msleep
Janusz Krzysztofik (3):
media: v4l2-subdev: Verify arguments in v4l2_subdev_call()
media: v4l2-subdev: Verify v4l2_subdev_call() pointer arguments
media: v4l2-subdev: Verify v4l2_subdev_call() pad config argument
Puranjay Mohan (1):
media: pci: cx88: Change the type of 'missed' to u64
drivers/media/common/saa7146/saa7146_fops.c| 9 +++
drivers/media/common/saa7146/saa7146_video.c | 18 +
drivers/media/pci/bt8xx/bttv-driver.c | 50 ++--
drivers/media/pci/cobalt/cobalt-v4l2.c | 14 ++--
drivers/media/pci/cx18/cx18-ioctl.c| 5 +-
drivers/media/pci/cx18/cx18-streams.c | 1 +
drivers/media/pci/cx23885/cx23885-417.c| 13 ++--
drivers/media/pci/cx23885/cx23885-video.c | 22 +++---
drivers/media/pci/cx25821/cx25821-video.c | 14 ++--
drivers/media/pci/cx88/cx88-blackbird.c| 4 +
drivers/media/pci/cx88/cx88-input.c| 4 +-
drivers/media/pci/cx88/cx88-video.c| 32
drivers/media/pci/dt3155/dt3155.c | 5 +-
drivers/media/pci/ivtv/ivtv-cards.h| 3 +-
drivers/media/pci/ivtv/ivtv-ioctl.c| 7 --
drivers/media/pci/ivtv/ivtv-streams.c | 14 +++-
drivers/media/pci/ivtv/ivtvfb.c| 10 +++
drivers/media/pci/meye/meye.c | 6 +-
drivers/media/pci/saa7134/saa7134-core.c | 15
drivers/media/pci/saa7134/saa7134-empress.c| 4 +
drivers/media/pci/saa7134/saa7134-video.c | 46 ++-
drivers/media/pci/saa7164/saa7164-encoder.c| 15 ++--
drivers/media/pci/saa7164/saa7164-vbi.c| 15 ++--
drivers/media/pci/solo6x10/solo6x10-v4l2-enc.c | 5 +-
drivers/media/pci/solo6x10/solo6x10-v4l2.c | 5 +-
drivers/media/pci/sta2x11/sta2x11_vip.c| 6 +-
drivers/media/pci/tw68/tw68-video.c| 8 +-
drivers/media/pci/tw686x/tw686x-video.c| 5 +-
drivers/media/platform/atmel/atmel-isc-base.c | 4 +-
drivers/media/platform/atmel/atmel-isc.h | 4 -
drivers/media/platform/vimc/vimc-capture.c | 5 +-
drivers/media/usb/hdpvr/hdpvr-video.c | 17 ++--
drivers/media/v4l2-core/v4l2-ctrls.c | 46 ++-
drivers/media/v4l2-core/v4l2-subdev.c | 268
+++
drivers/staging/media/hantro/hantro_drv.c | 8 +-
drivers/staging/media/tegra-vde/Kconfig| 1 +
drivers/staging/media/tegra-vde/Makefile | 1 +
drivers/staging/media/tegra-vde/dmabuf-cache.c | 226
+
drivers/staging/media/tegra-vde/iommu.c| 149
+++
drivers/staging/media/tegra-vde/trace.h| 2 +
drivers/staging/media/tegra-vde/{tegra-vde.c => vde.c} | 199
+++
drivers/staging/media/tegra-vde/vde.h | 105
+
include/media/v4l2-subdev.h| 6 ++
43 files changed, 942 insertions(+), 454 deletions(-)
create mode 100644 drivers/staging/media/tegra-vde/dmabuf-cache.c
create mode 100644 drivers/staging/media/tegra-vde/iommu.c
rename drivers/staging/media/tegra-vde/{tegra-vde.c => vde.c} (88%)
create mode 100644 drivers/staging/media/tegra-vde/vde.h
[GIT PULL for 5.3] More sensor and CSI-2 driver patches
Hi Mauro, Here's another set of CSI-2 and sensor driver patches for 5.3. The number appears large but the only driver receiving a significant amount of functional changes is the marvell-ccic. Please pull. The following changes since commit 3a959dcd11a4b1f55bbb4a37d3bac685c4e106b1: media: mt9m111: add regulator support (2019-06-21 17:56:39 -0400) are available in the git repository at: ssh://linuxtv.org/git/sailus/media_tree.git tags/for-5.3-4-signed for you to fetch changes up to e1f8eca499d2aac228bea702f361a0601dad5e94: staging: media: fix style problem (2019-06-22 10:36:59 +0300) sensor and CSI-2 driver patches for 5.3 Aliasgar Surti (1): staging: media: fix style problem Hugues Fruchet (4): media: st-mipid02: add support of V4L2_CID_LINK_FREQ media: st-mipid02: add support of RGB565 media: st-mipid02: add support of YUYV8 and UYVY8 media: st-mipid02: add support of JPEG Lubomir Rintel (9): Revert "[media] marvell-ccic: reset ccic phy when stop streaming for stability" marvell-ccic: drop unused stuff marvell-ccic/mmp: enable clock before accessing registers marvell-ccic: rename the clocks marvell-ccic/mmp: add devicetree support marvell-ccic: use async notifier to get the sensor marvell-ccic: provide a clock for the sensor media: marvell-ccic: only calculate the DPHY registers when needed media: marvell-ccic: mmp: don't chicken out w/o pdata Robert Jarzmik (1): media: mt9m111: fix fw-node refactoring Sakari Ailus (2): mt9m111: No need to check for the regulator mt9m111: Fix error handling in mt9m111_power_on Wolfram Sang (8): media: i2c: ak881x: simplify getting the adapter of a client media: i2c: mt9m001: simplify getting the adapter of a client media: i2c: mt9m111: simplify getting the adapter of a client media: i2c: ov2640: simplify getting the adapter of a client media: i2c: tw9910: simplify getting the adapter of a client staging: media: soc_camera: imx074: simplify getting the adapter of a client staging: media: soc_camera: mt9t031: simplify getting the adapter of a client staging: media: soc_camera: soc_mt9v022: simplify getting the adapter of a client drivers/media/i2c/ak881x.c| 2 +- drivers/media/i2c/mt9m001.c | 2 +- drivers/media/i2c/mt9m111.c | 37 ++- drivers/media/i2c/ov2640.c| 2 +- drivers/media/i2c/st-mipid02.c| 60 +++- drivers/media/i2c/tw9910.c| 3 +- drivers/media/platform/marvell-ccic/Kconfig | 2 + drivers/media/platform/marvell-ccic/cafe-driver.c | 58 +++- drivers/media/platform/marvell-ccic/mcam-core.c | 337 +++--- drivers/media/platform/marvell-ccic/mcam-core.h | 12 +- drivers/media/platform/marvell-ccic/mmp-driver.c | 238 --- drivers/staging/media/soc_camera/imx074.c | 2 +- drivers/staging/media/soc_camera/mt9t031.c| 2 +- drivers/staging/media/soc_camera/soc_mt9v022.c| 2 +- drivers/staging/media/soc_camera/soc_ov5642.c | 6 +- include/linux/platform_data/media/mmp-camera.h| 4 - 16 files changed, 424 insertions(+), 345 deletions(-) -- Sakari Ailus
Re: [GIT PULL for 5.3] More sensor and CSI-2 driver patches
On Sat, Jun 22, 2019 at 11:29:12AM +0300, Sakari Ailus wrote: > Hi Mauro, > > Here's another set of CSI-2 and sensor driver patches for 5.3. Oops! This should have been for 5.4, not 5.3! -- Sakari Ailus
[GIT PULL FOR v5.3] coda fixes and improvements
The following changes since commit 3a959dcd11a4b1f55bbb4a37d3bac685c4e106b1: media: mt9m111: add regulator support (2019-06-21 17:56:39 -0400) are available in the Git repository at: git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.3t for you to fetch changes up to f109771a576144a048e234c93a01f0f17a9fbf0f: media: coda: encoder parameter change support (2019-06-22 09:45:13 +0200) Tag branch Marco Felsch (2): media: coda: fix last buffer handling in V4L2_ENC_CMD_STOP media: coda: fix V4L2_DEC_CMD_STOP when all buffers are already consumed Michael Tretter (1): media: coda: implement CMD_START to restart decoding Philipp Zabel (25): media: coda: use mem2mem try_en/decoder_cmd helpers media: coda: fix mpeg2 sequence number handling media: coda: add coda_wake_up_capture_queue media: coda: split decoder sequence initialization out of start decoding media: coda: add sequence initialization work media: coda: implement decoder source change event media: coda: integrate internal frame metadata into a structure media: coda: make coda_bitstream_queue more versatile media: coda: pad first buffer with repeated MPEG headers to fix sequence init media: coda: do not enforce 512-byte initial bitstream payload on CODA960 media: coda: flush bitstream ring buffer on decoder restart media: coda: increment sequence offset for the last returned frame media: coda: allow flagging last output buffer internally media: coda: mark the last output buffer on decoder stop command media: coda: only set the stream end flags if there are no more pending output buffers media: coda: mark the last output buffer on encoder stop command media: coda: retire coda_buf_is_end_of_stream media: coda: only wake up capture queue if no pending buffers to encode media: coda: flag the last encoded buffer media: coda: lock capture queue wakeup against encoder stop command media: coda: mark last pending buffer or last meta on decoder stop command media: coda: mark last returned frame media: coda: store device pointer in driver structure instead of pdev media: coda: add coda_slice_mode() function media: coda: encoder parameter change support drivers/media/platform/coda/coda-bit.c| 403 drivers/media/platform/coda/coda-common.c | 244 +++--- drivers/media/platform/coda/coda-mpeg2.c | 43 + drivers/media/platform/coda/coda-mpeg4.c | 38 drivers/media/platform/coda/coda.h| 33 ++- drivers/media/platform/coda/coda_regs.h | 18 6 files changed, 637 insertions(+), 142 deletions(-)
Re: [GIT PULL for 5.3] More sensor and CSI-2 driver patches
Em Sat, 22 Jun 2019 11:39:09 +0300 Sakari Ailus escreveu: > On Sat, Jun 22, 2019 at 11:29:12AM +0300, Sakari Ailus wrote: > > Hi Mauro, > > > > Here's another set of CSI-2 and sensor driver patches for 5.3. > > Oops! This should have been for 5.4, not 5.3! > I already applied those yesterday. Should them be reverted? If so, why? Thanks, Mauro
Re: [GIT PULL for 5.3] More sensor and CSI-2 driver patches
Em Sat, 22 Jun 2019 06:58:44 -0300 Mauro Carvalho Chehab escreveu: > Em Sat, 22 Jun 2019 11:39:09 +0300 > Sakari Ailus escreveu: > > > On Sat, Jun 22, 2019 at 11:29:12AM +0300, Sakari Ailus wrote: > > > Hi Mauro, > > > > > > Here's another set of CSI-2 and sensor driver patches for 5.3. > > > > Oops! This should have been for 5.4, not 5.3! > > > > I already applied those yesterday. No, I didn't apply this series. I applied the last one. If this is not for 5.4, just mark the PR as rejected at patchwork. Thanks, Mauro
Re: [PATCH v2] media: v4l: ctrls: Add debug messages
On Sat, 2019-06-22 at 08:53 +0200, Hans Verkuil wrote:
> On 6/22/19 12:50 AM, Ezequiel Garcia wrote:
> > Currently, the v4l2 control code is a bit silent on errors.
> > Add debug messages on (hopefully) most of the error paths.
> >
> > Signed-off-by: Ezequiel Garcia
> > ---
> > Changes from v1:
> > * Drop changes in the debug parameter semantics.
> > * Drop new module debug parameter.
> > * Add documentation.
> > * Add a debug error in all places where control can fail.
> > * Reorder the vdev parameter, to make the patch less invasive.
> > ---
> > Documentation/media/kapi/v4l2-dev.rst | 1 +
> > drivers/media/platform/omap3isp/ispvideo.c | 2 +-
> > drivers/media/v4l2-core/v4l2-ctrls.c | 106 -
> > drivers/media/v4l2-core/v4l2-ioctl.c | 12 +--
> > drivers/media/v4l2-core/v4l2-subdev.c | 6 +-
> > include/media/v4l2-ctrls.h | 9 +-
> > include/media/v4l2-ioctl.h | 2 +
> > 7 files changed, 100 insertions(+), 38 deletions(-)
> >
> > diff --git a/Documentation/media/kapi/v4l2-dev.rst
> > b/Documentation/media/kapi/v4l2-dev.rst
> > index b359f1804bbe..4c5a15c53dbf 100644
> > --- a/Documentation/media/kapi/v4l2-dev.rst
> > +++ b/Documentation/media/kapi/v4l2-dev.rst
> > @@ -288,6 +288,7 @@ Mask Description
> > 0x08 Log the read and write file operations and the VIDIOC_QBUF and
> >VIDIOC_DQBUF ioctls.
> > 0x10 Log the poll file operation.
> > +0x20 Log error and messages in the control operations.
> > =
> >
> > Video device cleanup
> > diff --git a/drivers/media/platform/omap3isp/ispvideo.c
> > b/drivers/media/platform/omap3isp/ispvideo.c
> > index 175bbed9a235..abc945cc05c9 100644
> > --- a/drivers/media/platform/omap3isp/ispvideo.c
> > +++ b/drivers/media/platform/omap3isp/ispvideo.c
> > @@ -1028,7 +1028,7 @@ static int isp_video_check_external_subdevs(struct
> > isp_video *video,
> > ctrls.count = 1;
> > ctrls.controls = &ctrl;
> >
> > - ret = v4l2_g_ext_ctrls(pipe->external->ctrl_handler, NULL, &ctrls);
> > + ret = v4l2_g_ext_ctrls(pipe->external->ctrl_handler, &video->video,
> > NULL, &ctrls);
> > if (ret < 0) {
> > dev_warn(isp->dev, "no pixel rate control in subdev %s\n",
> > pipe->external->name);
> > diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c
> > b/drivers/media/v4l2-core/v4l2-ctrls.c
> > index 2d7525e2d9eb..4ee703e04ef2 100644
> > --- a/drivers/media/v4l2-core/v4l2-ctrls.c
> > +++ b/drivers/media/v4l2-core/v4l2-ctrls.c
> > @@ -6,6 +6,8 @@
> >
> > */
> >
> > +#define pr_fmt(fmt) "v4l2-ctrls: " fmt
> > +
> > #include
> > #include
> > #include
> > @@ -16,6 +18,12 @@
> > #include
> > #include
> >
> > +#define dprintk(vdev, fmt, arg...) do {
> > \
> > + if (vdev->dev_debug & V4L2_DEV_DEBUG_CTRL) \
>
> This isn't very robust if vdev is NULL. I know it shouldn't, but it's
> better to check for this.
>
> I'd use this instead:
>
> if (!WARN_ON(!vdev) && ((vdev)->dev_debug & V4L2_DEV_DEBUG_CTRL))
> \
>
> That way nothing crashes if vdev is NULL, and you get a warning as well in
> that case.
>
OK, no problem.
Thanks,
Eze
[PATCH v3] media: v4l: ctrls: Add debug messages
Currently, the v4l2 control code is a bit silent on errors.
Add debug messages on (hopefully) most of the error paths.
Signed-off-by: Ezequiel Garcia
---
Changes from v2:
* Check and noisy-warn if vdev is NULL.
Changes from v1:
* Drop changes in the debug parameter semantics.
* Drop new module debug parameter.
* Add documentation.
* Add a debug error in all places where control can fail.
* Reorder the vdev parameter, to make the patch less invasive.
---
Documentation/media/kapi/v4l2-dev.rst | 1 +
drivers/media/platform/omap3isp/ispvideo.c | 2 +-
drivers/media/v4l2-core/v4l2-ctrls.c | 106 -
drivers/media/v4l2-core/v4l2-ioctl.c | 12 +--
drivers/media/v4l2-core/v4l2-subdev.c | 6 +-
include/media/v4l2-ctrls.h | 9 +-
include/media/v4l2-ioctl.h | 2 +
7 files changed, 100 insertions(+), 38 deletions(-)
diff --git a/Documentation/media/kapi/v4l2-dev.rst
b/Documentation/media/kapi/v4l2-dev.rst
index b359f1804bbe..4c5a15c53dbf 100644
--- a/Documentation/media/kapi/v4l2-dev.rst
+++ b/Documentation/media/kapi/v4l2-dev.rst
@@ -288,6 +288,7 @@ Mask Description
0x08 Log the read and write file operations and the VIDIOC_QBUF and
VIDIOC_DQBUF ioctls.
0x10 Log the poll file operation.
+0x20 Log error and messages in the control operations.
=
Video device cleanup
diff --git a/drivers/media/platform/omap3isp/ispvideo.c
b/drivers/media/platform/omap3isp/ispvideo.c
index 175bbed9a235..abc945cc05c9 100644
--- a/drivers/media/platform/omap3isp/ispvideo.c
+++ b/drivers/media/platform/omap3isp/ispvideo.c
@@ -1028,7 +1028,7 @@ static int isp_video_check_external_subdevs(struct
isp_video *video,
ctrls.count = 1;
ctrls.controls = &ctrl;
- ret = v4l2_g_ext_ctrls(pipe->external->ctrl_handler, NULL, &ctrls);
+ ret = v4l2_g_ext_ctrls(pipe->external->ctrl_handler, &video->video,
NULL, &ctrls);
if (ret < 0) {
dev_warn(isp->dev, "no pixel rate control in subdev %s\n",
pipe->external->name);
diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c
b/drivers/media/v4l2-core/v4l2-ctrls.c
index 2d7525e2d9eb..1c8ae4501870 100644
--- a/drivers/media/v4l2-core/v4l2-ctrls.c
+++ b/drivers/media/v4l2-core/v4l2-ctrls.c
@@ -6,6 +6,8 @@
*/
+#define pr_fmt(fmt) "v4l2-ctrls: " fmt
+
#include
#include
#include
@@ -16,6 +18,12 @@
#include
#include
+#define dprintk(vdev, fmt, arg...) do {
\
+ if (!WARN_ON(!vdev) && ((vdev)->dev_debug & V4L2_DEV_DEBUG_CTRL)) \
+ printk(KERN_DEBUG pr_fmt("%s: %s: " fmt), \
+ __func__, video_device_node_name(vdev), ##arg); \
+} while (0)
+
#define has_op(master, op) \
(master->ops && master->ops->op)
#define call_op(master, op) \
@@ -3211,6 +3219,7 @@ static int v4l2_ctrl_request_bind(struct media_request
*req,
static int prepare_ext_ctrls(struct v4l2_ctrl_handler *hdl,
struct v4l2_ext_controls *cs,
struct v4l2_ctrl_helper *helpers,
+struct video_device *vdev,
bool get)
{
struct v4l2_ctrl_helper *h;
@@ -3228,20 +3237,28 @@ static int prepare_ext_ctrls(struct v4l2_ctrl_handler
*hdl,
if (cs->which &&
cs->which != V4L2_CTRL_WHICH_DEF_VAL &&
cs->which != V4L2_CTRL_WHICH_REQUEST_VAL &&
- V4L2_CTRL_ID2WHICH(id) != cs->which)
+ V4L2_CTRL_ID2WHICH(id) != cs->which) {
+ dprintk(vdev, "invalid which 0x%x or control id
0x%x\n", cs->which, id);
return -EINVAL;
+ }
/* Old-style private controls are not allowed for
extended controls */
- if (id >= V4L2_CID_PRIVATE_BASE)
+ if (id >= V4L2_CID_PRIVATE_BASE) {
+ dprintk(vdev, "old-style private controls not allowed
for extended controls\n");
return -EINVAL;
+ }
ref = find_ref_lock(hdl, id);
- if (ref == NULL)
+ if (ref == NULL) {
+ dprintk(vdev, "cannot find control id 0x%x\n", id);
return -EINVAL;
+ }
h->ref = ref;
ctrl = ref->ctrl;
- if (ctrl->flags & V4L2_CTRL_FLAG_DISABLED)
+ if (ctrl->flags & V4L2_CTRL_FLAG_DISABLED) {
+ dprintk(vdev, "control id 0x%x is disabled\n", id);
return -EINVAL;
+ }
if (ctrl->cluster[0]->ncontrols > 1)
have_clusters = true;
@@ -3251,10 +3268,16 @@ static int prepare_ext_ctrls(struct v4l2_ctrl_handler
*hdl,
Re: Unsupported Anysee version
Dear Jan Pieter, Thanks for your reply. I see that this has been quite a while ago already. In that case, I cannot use the hardware in this point of time. I can think of a few options: Either I borrow the hardware to someone who can and is willing to write a driver (I’m willing to ship it) Or I set up an isolated development machine with this hardware attached, with ssh access for someone to develop it remotely. Or, in a few months, I’ll try to fiddle with the drivers myself. Or I discard of it. Kind regards, Wytse Talsma > On 12 Jun 2019, at 15:56, JP wrote: > > > > On 6/8/19 4:03 PM, W. Talsma wrote: >> Dear, >> >> Today decided to dust off my Anysee E30 S2 Plus, and hope to get it to work >> with the Debian stretch tvheadend server. >> Once I plug it in however, I see the following: >> [27054.699829] usb 1-1.6: new high-speed USB device number 7 using ehci-pci >> [27055.224303] usb 1-1.6: device descriptor read/all, error -71 >> [27056.187821] usb 1-1.6: new high-speed USB device number 8 using ehci-pci >> [27057.180465] usb 1-1.6: config 1 interface 0 altsetting 0 bulk endpoint >> 0x1 has invalid maxpacket 64 >> [27057.180469] usb 1-1.6: config 1 interface 0 altsetting 0 bulk endpoint >> 0x81 has invalid maxpacket 64 >> [27057.180472] usb 1-1.6: config 1 interface 0 altsetting 1 bulk endpoint >> 0x1 has invalid maxpacket 64 >> [27057.180474] usb 1-1.6: config 1 interface 0 altsetting 1 bulk endpoint >> 0x81 has invalid maxpacket 64 >> [27057.180961] usb 1-1.6: New USB device found, idVendor=1c73, >> idProduct=861f, bcdDevice= 1.00 >> [27057.180964] usb 1-1.6: New USB device strings: Mfr=1, Product=2, >> SerialNumber=0 >> [27057.180966] usb 1-1.6: Product: anysee-S2(LP) >> [27057.180967] usb 1-1.6: Manufacturer: AMT.CO.KR >> [27057.194507] usb 1-1.6: dvb_usb_v2: found a 'Anysee' in warm state >> [27057.196058] usb 1-1.6: dvb_usb_anysee: firmware version 1.3 hardware id 11 >> [27057.197957] usb 1-1.6: dvb_usb_v2: will pass the complete MPEG2 transport >> stream to the software demuxer >> [27057.197974] dvbdev: DVB: registering new adapter (Anysee) >> [27057.197978] usb 1-1.6: media controller created >> [27057.198256] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' >> registered. >> [27057.204296] Invalid probe, probably not a CX24116 device >> [27057.204304] usb 1-1.6: dvb_usb_anysee: Unsupported Anysee version. Please >> report to . >> [27057.204718] usbcore: registered new interface driver dvb_usb_anysee >> >> lsusb gives me the following: >> Bus 001 Device 008: ID 1c73:861f AMT Anysee E30 USB 2.0 DVB-T Receiver >> >> uname -a >> Linux linsrv03 4.19.45 #1 SMP Fri May 24 00:31:25 CEST 2019 x86_64 GNU/Linux >> >> This reminded me that in the past, I never actually got the drivers fully to >> work under Linux. >> Since it states: Please report to ., here is my >> report. >> Is it possible to get it working? >> >> Kind regards, >> Wytse Talsma >> > This has been on this list before: > https://www.mail-archive.com/linux-media@vger.kernel.org/msg42569.html > > Jan Pieter
From:Miss: Fatima Yusuf.
From:Miss: Fatima Yusuf. For sure this mail would definitely come to you as a surprise, but do take your good time to go through it, My name is Ms. Fatima Yusuf,i am from Ivory Coast. I lost my parents a year and couple of months ago. My father was a serving director of the Agro-exporting board until his death. He was assassinated by his business partners.Before his death, he made a deposit of US$9.7 Million Dollars here in Cote d'ivoire which was for the purchase of cocoa processing machine and development of another factory before his untimely death. Being that this part of the world experiences political and crises time without number, there is no guarantee of lives and properties. I cannot invest this money here any long, despite the fact it had been my late father's industrial plans. I want you to do me a favor to receive this funds into your country or any safer place as the beneficiary, I have plans to invest this money in continuation with the investment vision of my late father, but not in this place again rather in your country. I have the vision of going into real estate and industrial production or any profitable business venture. I will be ready to compensate you with 20% of the total Amount, now all my hope is banked on you and i really wants to invest this money in your country, where there is stability of Government, political and economic welfare. My greatest worry now is how to move out of this country because my uncle is threatening to kill me as he killed my father,Please do not let anybody hear about this, it is between me and you alone because of my security reason. I am waiting to hear from you. Yours Sincerely, Miss.Fatima Yusuf.
Re: Remote "Mouse mode" buttons, Keycode choices, etc.
On Fri 2019-06-21 13:39:39, Bastien Nocera wrote: > On Sun, 2019-06-16 at 18:58 +0200, Pavel Machek wrote: > > Hi! > > > > > I dug out a fair bunch of remote controls I got around 10 years > > > ago[1], > > > and started trying them all out. > > > > > > I bumped into a couple of problems: > > > > > > - the Snapstream Firefly remote ([2] using the rc-snapstream- > > > firefly > > > keymap and the ati_remote protocol) creates 2 input device nodes, > > > one > > > for the remote keys, one for the mouse mode. The mouse button on > > > the > > > remote just sends KEY_MODE, and doesn't change the mode, nothing is > > > ever sent on the mouse device node > > > > > > - the Streamzap remote ([3]) uses KEY_NUMERIC_[0-9] keycodes, just > > > like > > > a small minority of other devices. Is there any reason for them not > > > to > > > use KEY_[0-9] instead? Or for all of them to use KEY_NUMERIC_*, for > > > consistencies' sake. I can send patches for those. > > > > This may be a bit of fun; consistency is good but this will change > > behaviour for people, > > right? > > > > So.. be careful :-). > > I'm not really sure how one can be "careful" doing that. You could do an config option and then pretend breakage is user decision, for example. Or better just change it and see what happens. > You can check this patch to lirc from 2008 to see what it might end up > looking like ;) > https://people.redhat.com/bnocera/lirc-fix-remote-keycodes.patch > > It doesn't really answer my question about whether this discrepancy was > intended though. Probably not intended. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html signature.asc Description: Digital signature
cron job: media_tree daily build: OK
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Sun Jun 23 05:00:14 CEST 2019 media-tree git hash:3a959dcd11a4b1f55bbb4a37d3bac685c4e106b1 media_build git hash: 8c181825fa4b157679e600565c310841be9f1890 v4l-utils git hash: 070a4d421778c313f79d840bf400a7d60dfe7dc9 edid-decode git hash: 15df4aebf06da579241c58949493b866139d0e2b gcc version:i686-linux-gcc (GCC) 8.3.0 sparse repo:https://git.linuxtv.org/mchehab/sparse.git sparse version: 0.6.1-rc1 smatch repo:https://git.linuxtv.org/mchehab/smatch.git smatch version: 0.5.1 build-scripts repo: https://git.linuxtv.org/hverkuil/build-scripts.git build-scripts git hash: 5b7e41d5bee1ef9274d548f945fb9ae3d8bb208a host hardware: x86_64 host os:4.19.0-4-amd64 linux-git-arm-at91: OK linux-git-arm-davinci: OK linux-git-arm-multi: OK linux-git-arm-pxa: OK linux-git-arm-stm32: OK linux-git-arm64: OK linux-git-i686: OK linux-git-mips: OK linux-git-powerpc64: OK linux-git-sh: OK linux-git-x86_64: OK Check COMPILE_TEST: OK Check for strcpy/strncpy/strlcpy: OK linux-3.10.108-i686: OK linux-3.10.108-x86_64: OK linux-3.11.10-i686: OK linux-3.11.10-x86_64: OK linux-3.12.74-i686: OK linux-3.12.74-x86_64: OK linux-3.13.11-i686: OK linux-3.13.11-x86_64: OK linux-3.14.79-i686: OK linux-3.14.79-x86_64: OK linux-3.15.10-i686: OK linux-3.15.10-x86_64: OK linux-3.16.63-i686: OK linux-3.16.63-x86_64: OK linux-3.17.8-i686: OK linux-3.17.8-x86_64: OK linux-3.18.136-i686: OK linux-3.18.136-x86_64: OK linux-3.19.8-i686: OK linux-3.19.8-x86_64: OK linux-4.0.9-i686: OK linux-4.0.9-x86_64: OK linux-4.1.52-i686: OK linux-4.1.52-x86_64: OK linux-4.2.8-i686: OK linux-4.2.8-x86_64: OK linux-4.3.6-i686: OK linux-4.3.6-x86_64: OK linux-4.4.167-i686: OK linux-4.4.167-x86_64: OK linux-4.5.7-i686: OK linux-4.5.7-x86_64: OK linux-4.6.7-i686: OK linux-4.6.7-x86_64: OK linux-4.7.10-i686: OK linux-4.7.10-x86_64: OK linux-4.8.17-i686: OK linux-4.8.17-x86_64: OK linux-4.9.162-i686: OK linux-4.9.162-x86_64: OK linux-4.10.17-i686: OK linux-4.10.17-x86_64: OK linux-4.11.12-i686: OK linux-4.11.12-x86_64: OK linux-4.12.14-i686: OK linux-4.12.14-x86_64: OK linux-4.13.16-i686: OK linux-4.13.16-x86_64: OK linux-4.14.105-i686: OK linux-4.14.105-x86_64: OK linux-4.15.18-i686: OK linux-4.15.18-x86_64: OK linux-4.16.18-i686: OK linux-4.16.18-x86_64: OK linux-4.17.19-i686: OK linux-4.17.19-x86_64: OK linux-4.18.20-i686: OK linux-4.18.20-x86_64: OK linux-4.19.28-i686: OK linux-4.19.28-x86_64: OK linux-4.20.15-i686: OK linux-4.20.15-x86_64: OK linux-5.0.15-i686: OK linux-5.0.15-x86_64: OK linux-5.1.1-i686: OK linux-5.1.1-x86_64: OK linux-5.2-rc1-i686: OK linux-5.2-rc1-x86_64: OK apps: OK spec-git: OK virtme: OK: Final Summary: 2165, Succeeded: 2165, Failed: 0, Warnings: 0 sparse: OK smatch: OK Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Sunday.log Detailed regression test results are available here: http://www.xs4all.nl/~hverkuil/logs/Sunday-test-media.log http://www.xs4all.nl/~hverkuil/logs/Sunday-test-media-dmesg.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Sunday.tar.bz2 The Media Infrastructure API from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/index.html
