Re: [PATCH 00/18] prevent bounds-check bypass via speculative execution

On Fri, Jan 5, 2018 at 6:22 PM, Eric W. Biederman wrote: > Dan Williams writes: > >> Quoting Mark's original RFC: >> >> "Recently, Google Project Zero discovered several classes of attack >> against speculative execution. One of these, known as

cron job: media_tree daily build: ERRORS

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: Sat Jan 6 05:00:17 CET 2018 media-tree git hash:e3ee691dbf24096ea51b3200946b11d68ce75361 media_build

Re: [PATCH 00/18] prevent bounds-check bypass via speculative execution

Dan Williams writes: > Quoting Mark's original RFC: > > "Recently, Google Project Zero discovered several classes of attack > against speculative execution. One of these, known as variant-1, allows > explicit bounds checks to be bypassed under speculation, providing an

[PATCH 07/18] [media] uvcvideo: prevent bounds-check bypass via speculative execution

Static analysis reports that 'index' may be a user controlled value that is used as a data dependency to read 'pin' from the 'selector->baSourceID' array. In order to avoid potential leaks of kernel memory values, block speculative execution of the instruction stream that could issue reads based

[PATCH 00/18] prevent bounds-check bypass via speculative execution

Quoting Mark's original RFC: "Recently, Google Project Zero discovered several classes of attack against speculative execution. One of these, known as variant-1, allows explicit bounds checks to be bypassed under speculation, providing an arbitrary read gadget. Further details can be found on the

[PATCH 4/4] cx23885: Add support for new Hauppauge QuadHD (885)

Add new QuadHD digital only PCIe boards to driver list. Differentiate them from 888 digital/analog QuadHD models. Signed-off-by: Brad Love --- drivers/media/pci/cx23885/cx23885-cards.c | 42 ++- drivers/media/pci/cx23885/cx23885-core.c | 8

[PATCH 1/4] cx23885: Enable new Hauppauge PCIe ImpactVCBe variant

Add ID of new card revision to driver list Analog PAL/NTSC capture. Signed-off-by: Brad Love --- drivers/media/pci/cx23885/cx23885-cards.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/media/pci/cx23885/cx23885-cards.c

[PATCH 2/4] cx23885: Add support for Hauppauge PCIe HVR1265 K4

Add new PCIe board to driver list and board register/configure functions cx23885 + lgdt3306a + si2157 digital/analog Signed-off-by: Brad Love --- drivers/media/pci/cx23885/cx23885-cards.c | 27 ++ drivers/media/pci/cx23885/cx23885-dvb.c | 46

[PATCH 3/4] cx23885: Add support for Hauppauge PCIe Starburst2

Add new PCIe DVB-S/S2. A single port Hauppauge HVR-5525 cx23885 + a8293 + m88rs6000t Signed-off-by: Brad Love --- drivers/media/pci/cx23885/cx23885-cards.c | 11 +++ drivers/media/pci/cx23885/cx23885-dvb.c | 18 ++

[PATCH 0/4] New Hauppauge PCIe devices

Included is support for the following four PCIe devices: - Hauppauge ImpactVCBe - analog PAL/NTSC - Hauppauge HVR1264K4 - ATSC/QAM + analog - Hauppauge Starburst2 - DVB-C/S/T/T2 + analog - Hauppauge digital only QuadHD models - ATSC/QAM|DVB-C/T/T2 Brad Love (4): cx23885: Enable new Hauppauge

Re: [PATCH] media: ov9650: support device tree probing

Hello Akinobu, On Sat, Jan 06, 2018 at 02:49:03AM +0900, Akinobu Mita wrote: > The ov9650 driver currently only supports legacy platform data probe. > This change adds device tree probing. > > There has been an attempt to add device tree support for ov9650 driver > by Hugues Fruchet as a part of

Re: [PATCH v5 3/5] media: dt-bindings: ov5640: refine CSI-2 and add parallel interface

On Wed, Jan 03, 2018 at 10:57:30AM +0100, Hugues Fruchet wrote: > Refine CSI-2 endpoint documentation and add bindings > for DVP parallel interface support. > > Signed-off-by: Hugues Fruchet > --- > .../devicetree/bindings/media/i2c/ov5640.txt | 46 >

Re: [PATCH] media: ov9650: support device tree probing

On Fri, Jan 5, 2018 at 11:49 AM, Akinobu Mita wrote: > The ov9650 driver currently only supports legacy platform data probe. > This change adds device tree probing. > > There has been an attempt to add device tree support for ov9650 driver > by Hugues Fruchet as a part of

Re: [PATCH v3 1/9] dt-bindings: media: Add Renesas CEU bindings

Hi Laurent, On Fri, Jan 05, 2018 at 12:28:03AM +0200, Laurent Pinchart wrote: > Hi Jacopo, > > Thank you for the patch. > > On Thursday, 4 January 2018 18:03:09 EET Jacopo Mondi wrote: > > Add bindings documentation for Renesas Capture Engine Unit (CEU). > > > > Signed-off-by: Jacopo Mondi

[PATCH] media: xilinx-video: support pipeline power management

This enables pipeline power management for Xilinx Video IP driver. Some V4L2 subdevices are put their power status into power down mode after their probe function, and require to be powered up by calling s_power() operation when the pipeline is in use. So this change is necessary if the video

[PATCH] media: ov9650: support device tree probing

The ov9650 driver currently only supports legacy platform data probe. This change adds device tree probing. There has been an attempt to add device tree support for ov9650 driver by Hugues Fruchet as a part of the patchset that adds support of OV9655 camera

Re: [PATCH] media: uvcvideo: support multiple frame descriptors with the same dimensions

Hi Laurent, On Fri, 2018-01-05 at 15:30 +0200, Laurent Pinchart wrote: > Hi Philipp, > > Thank you for the patch. > > On Friday, 5 January 2018 00:51:29 EET Philipp Zabel wrote: > > The Microsoft HoloLens Sensors device has two separate frame descriptors > > with the same dimensions, each with

Re: [PATCH v3 1/6] media: rc: update sunxi-ir driver to get base clock frequency from devicetree

On Tue, Dec 19, 2017 at 09:07:42AM +0100, Philipp Rossak wrote: > This patch updates the sunxi-ir driver to set the base clock frequency from > devicetree. > > This is necessary since there are different ir receivers on the > market, that operate with different frequencies. So this value could be

Mygica 230C defined in two drivers

Hi Stefan and all, I noticed that the Mygica 230C is currently defined in two different drivers. in dvbsky.c: { DVB_USB_DEVICE(USB_VID_CONEXANT, USB_PID_MYGICA_T230C, _t230c_props, "MyGica Mini DVB-T2 USB Stick T230C", RC_MAP_TOTAL_MEDIA_IN_HAND_02) }, in cxusb.c:

Re: [PATCH 2/9] em28xx: Bulk transfer implementation fix

On 2018-01-05 08:20, Devin Heitmueller wrote: > Hi Brad, > > My documents indicate that Register 0x5D and 0x5E are read-only, and > populated based on the eeprom programming. > > On your device, what is the value of those registers prior to you changing > them? > > If you write to those

Re: [PATCH v3 0/6] arm: sunxi: IR support for A83T

Hi, On Fri, Jan 05, 2018 at 12:02:53PM +, Sean Young wrote: > On Tue, Dec 19, 2017 at 09:07:41AM +0100, Philipp Rossak wrote: > > This patch series adds support for the sunxi A83T ir module and enhances > > the sunxi-ir driver. Right now the base clock frequency for the ir driver > > is a

[PATCH 0/2] lgdt3306a: fix bugs in usb disconnect/reconnect

There are a couple problems currently in this driver, when used as an i2c_device. This patch set addresses the issues one at a time. First during process of dvb frontend detach release is called, then if CONFIG_MEDIA_ATTACH is enabled, the usage count is decremented. Remove is then called,

[PATCH 2/2] lgdt3306a: Fix a double kfree on i2c device remove

Both lgdt33606a_release and lgdt3306a_remove kfree state, but _release is called first, then _remove operates on states members before kfree'ing it. This can lead to random oops/GPF/etc on USB disconnect. Signed-off-by: Brad Love ---

[PATCH 1/2] lgdt3306a: Fix module count mismatch on usb unplug

When used as an i2c device there is a module usage count mismatch on removal, preventing the driver from being used thereafter. dvb_attach increments the usage count so it is properly balanced on removal. On disconnect of Hauppauge SoloHD/DualHD before: lsmod | grep lgdt3306a lgdt3306a

[PATCH 2/2] media: rc: do not remove first bit if leader pulse is present

The rc5 protocol does not have a leading pulse or space, but we encode the first bit using a single leading pulse. For other protocols, the leading pulse or space does not represent any bit. So, don't remove the first bit if a leading pulse is present. Cc: Antti Seppälä

[PATCH 1/2] media: rc: clean up leader pulse/space for manchester encoding

The IR rc6 encoder sends the header using manchester encoding using 0 bits, which causes the following: UBSAN: Undefined behaviour in drivers/media/rc/rc-ir-raw.c:247:6 shift exponent 4294967295 is too large for 64-bit type 'long long unsigned int' So, allow the leader code to send a pulse and

Re: [PATCH 2/9] em28xx: Bulk transfer implementation fix

Hi Brad, My documents indicate that Register 0x5D and 0x5E are read-only, and populated based on the eeprom programming. On your device, what is the value of those registers prior to you changing them? If you write to those registers, do they reflect the new values if you read them back? Does

Re: [PATCH] media: uvcvideo: support multiple frame descriptors with the same dimensions

Hi Philipp, Thank you for the patch. On Friday, 5 January 2018 00:51:29 EET Philipp Zabel wrote: > The Microsoft HoloLens Sensors device has two separate frame descriptors > with the same dimensions, each with a single different frame interval: > > VideoStreaming Interface Descriptor: >

Re: [PATCH] media: staging: tegra-vde: select DMA_SHARED_BUFFER

On 05.01.2018 12:43, Arnd Bergmann wrote: > Without CONFIG_DMA_SHARED_BUFFER we run into a link error for the > dma_buf_* APIs: > > ERROR: "dma_buf_map_attachment" > [drivers/staging/media/tegra-vde/tegra-vde.ko] undefined! > ERROR: "dma_buf_attach" [drivers/staging/media/tegra-vde/tegra-vde.ko]

Re: [PATCH v3 0/6] arm: sunxi: IR support for A83T

On Tue, Dec 19, 2017 at 09:07:41AM +0100, Philipp Rossak wrote: > This patch series adds support for the sunxi A83T ir module and enhances > the sunxi-ir driver. Right now the base clock frequency for the ir driver > is a hard coded define and is set to 8 MHz. > This works for the most common ir

Re: [PATCH v2 8/9] lgdt3306a: QAM streaming improvement

On Thu, Jan 4, 2018 at 8:30 PM, Brad Love wrote: > Add some register updates required for stable viewing > on Cablevision in NY. Does not adversely affect other providers. > > Changes since v1: > - Change upper case hex to lower case. > > Signed-off-by: Brad Love

[PATCH] media: cobalt: select CONFIG_SND_PCM

The cobalt sound driver has a dependency on ALSA, but not on the PCM helper code, so this can lead to an extremely rare link error in randconfig builds: ERROR: "snd_pcm_period_elapsed" [drivers/media/pci/cobalt/cobalt.ko] undefined! ERROR: "_snd_pcm_stream_lock_irqsave"

[PATCH] media: staging: tegra-vde: select DMA_SHARED_BUFFER

Without CONFIG_DMA_SHARED_BUFFER we run into a link error for the dma_buf_* APIs: ERROR: "dma_buf_map_attachment" [drivers/staging/media/tegra-vde/tegra-vde.ko] undefined! ERROR: "dma_buf_attach" [drivers/staging/media/tegra-vde/tegra-vde.ko] undefined! ERROR: "dma_buf_get"

Re: [PATCH v3 1/9] dt-bindings: media: Add Renesas CEU bindings

On Thu, Jan 4, 2018 at 11:28 PM, Laurent Pinchart wrote: > On Thursday, 4 January 2018 18:03:09 EET Jacopo Mondi wrote: >> Add bindings documentation for Renesas Capture Engine Unit (CEU). >> +++ b/Documentation/devicetree/bindings/media/renesas,ceu.txt >> @@

Re: [RESEND PATCH 0/2] dw9714 fixes, cleanups

On Fri, Jan 05, 2018 at 01:22:54AM +, Mani, Rajmohan wrote: > > The two patches address a small bug in dw9714 driver and clean it up a > > little, > > too. > > > > Raj: could you let me know if they work for you? Thanks. > > > > These patches work fine. Thanks! I'll add: Tested-by: