Hi Guys,
(I'm copying Ezequial on this because of the work he has done on the
stk1160).
My colleague (a Doctor) had this to say on the medical images I posted
earlier (see below):
The impactVCB-e image is redder and less clear. The dvc100 and
easycap seem similar to me and both of them
Doh, HTML cause vger to drop it. Resending.
On Fri, Apr 25, 2014 at 8:47 AM, Steven Toth st...@kernellabs.com wrote:
On Fri, Apr 25, 2014 at 8:19 AM, Steve Cookson i...@sca-uk.com wrote:
Hi Guys,
Hello again.
(I'm copying Ezequial on this because of the work he has done on the
stk1160).
I looked at the pictures as well and I noticed a few things:
The aspect ratio of the impactvcb-e isn't right, it's too narrow. What width
and height did you specify when capturing? I can't test this myself as I'm
abroad, but try 720x480 or 768x480.
I also noticed that the cx23885 driver selects
On Apr 25, Steve Cookson wrote:
[..]
If the DVC100 and ImpactVCB-e had had the same love and attention that
Ezequial has shown the EasyCap would they outperform it?
I really appreciate the kind words and I'm happy to see the driver is being
used and works well.
However, to be fair, the
vb2_get_vma() copy the content of the vma to a new structure but set
some of its pointers to NULL.
One of this pointer is used by follow_pte() called by follow_pfn()
on io memory.
This can lead to a NULL pointer derreference.
The version of vma that has not been cleared must be used.
[
ivtv_yuv_init() is used in atomic context,
so memory allocation should be done keeping that in mind.
Call graph for ivtv_yuv_init() is as follows:
- ivtv_yuv_next_free()
- ivtv_yuv_prep_frame() [ioctl handler]
- ivtv_yuv_setup_stream_frame()
- ivtv_irq_dec_data_req() - ivtv_irq_handler()
I have an Elgato Eye TV V2 USB device USB ID 0fd9:002c which reading here
https://github.com/mirrors/linux-2.6/blob/master/drivers/staging/media/as102/as102_usb_drv.h
Looks like it should be supported (it looks like Devin wrote some of
the code?)..it gets recognised in dmesg and indeed
On Fri, Apr 25, 2014 at 2:31 PM, Another Sillyname
anothersn...@googlemail.com wrote:
I have an Elgato Eye TV V2 USB device USB ID 0fd9:002c which reading here
https://github.com/mirrors/linux-2.6/blob/master/drivers/staging/media/as102/as102_usb_drv.h
Looks like it should be supported
Thanks Devin
Is the as102 tree ever likely to go mainline?
Regards
Tony
On 25 April 2014 19:40, Devin Heitmueller dheitmuel...@kernellabs.com wrote:
On Fri, Apr 25, 2014 at 2:31 PM, Another Sillyname
anothersn...@googlemail.com wrote:
I have an Elgato Eye TV V2 USB device USB ID 0fd9:002c
Is the as102 tree ever likely to go mainline?
The only reason it's in staging is because it doesn't meet the coding
standards (i.e. whitespace, variable naming, etc). Somebody needs to
come along and expend the energy to satisfy the whitespace gods.
Seems like a fantastically stupid reason to
OK, I'm not a coder these days but I'll look and see if I can work it out.
Regards and have a good weekend.
Tony
On 25 April 2014 19:54, Devin Heitmueller dheitmuel...@kernellabs.com wrote:
Is the as102 tree ever likely to go mainline?
The only reason it's in staging is because it doesn't
Hi,
Am 24.04.2014 23:26, schrieb Mauro Carvalho Chehab:
Em Thu, 24 Apr 2014 15:24:20 -0400
Devin Heitmueller dheitmuel...@kernellabs.com escreveu:
[...]
What can do, instead, is to sniff the traffic at the USB port, and get
the proper GPIO, XCLK and I2C speed settings for this device.
My
On Fri, 25 Apr 2014, Oleg Nesterov wrote:
And I forgot to mention, there is another reason why I would like to
change uprobes to follow the same convention. I still think it would
be better to kill __replace_page() and use gup(FOLL_WRITE | FORCE)
in uprobe_write_opcode().
Oh, please please
Guys,
I’m trying to compile most recent Siano drivers with old kernel tree (3.4.75
linux-sunxi). The module seems compile but final linker (?) give me a few
errors.
smsendian_handle_tx_message is in media/common/siano/smsendian.c as expected.
All tips are appreciated ;-)
Thank you !
-
On Apr 17, Ezequiel Garcia wrote:
Currently stk1160_read_reg() uses a stack-allocated char to get the
read control value. This is wrong because usb_control_msg() requires
a kmalloc-ed buffer.
This commit fixes such issue by kmalloc'ating a 1-byte buffer to receive
the read value.
While
On Fri, Apr 11, 2014 at 7:56 AM, Jacek Anaszewski
j.anaszew...@samsung.com wrote:
Some LED devices support two operation modes - torch and
flash.
Do we have a method to look up the capabilities from LED devices driver?
For example, the LED device supports Torch/Flash then LED device
driver
16 matches
Mail list logo
