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: Mon Jun 27 04:00:31 CEST 2016
git branch: test
git hash: 59f0bc11848f8f3242bc1fefae670e745929cd7b
gcc
Hi Mauro,
On Fri, 24 Jun 2016 12:31:54 -0300
Mauro Carvalho Chehab wrote:
> Those tables are currently unused, so comment them out:
We actually could remove these tables. It is very, very unlikely that
this device will ever be used for S-Band in the future.
Extremely
According to the datasheet of Meson8b (S805) and GXBB (S905) the
decoding mode is configured in AO_MF_IR_DEC_REG2 (offset 0x20) using
bits 0-3.
The "duration" field may not be set correctly when any of the hardware
decoding modes. This can happen while a "default" decoding mode
(either set by the
According to the reference driver (and the datasheet of the newer
Meson8b/S805 and GXBB/S905 SoCs) there are 14 registers, each 32 bit
wide.
Adjust the register size to reflect that, as register offset 0x20 is
now also needed by the meson-ir driver.
Signed-off-by: Martin Blumenstingl
The meson-ir driver uses the wrong offset (at least according to
Amlogic's reference driver as well as the datasheets of the
Meson8b/S805 and GXBB/S905).
This means that we are getting incorrect durations (REG1_TIME_IV)
reported from the hardware.
This problem was also noticed by some people
According to the datasheet of Meson8b (S805) and GXBB (S905) the
decoding mode is configured in AO_MF_IR_DEC_REG2 (offset 0x20) using
bits 0-3.
The "duration" field may not be set correctly when any of the hardware
decoding modes. This can happen while a "default" decoding mode
(either set by the
The meson-ir driver uses the wrong offset (at least according to
Amlogic's reference driver as well as the datasheets of the
Meson8b/S805 and GXBB/S905).
This means that we are getting incorrect durations (REG1_TIME_IV)
reported from the hardware.
This problem was also noticed by some people
On 2016-06-26 17:07, Hans Verkuil wrote:
On 06/26/2016 04:29 PM, Torbjorn Jansson wrote:
Hello
if i use media_build and modprobe cx23885 i get:
# modprobe cx23885
modprobe: ERROR: could not insert 'cx23885': Exec format error
and on dmesg i get:
frame_vector: exports duplicate symbol
On 06/26/2016 04:29 PM, Torbjorn Jansson wrote:
> Hello
>
> if i use media_build and modprobe cx23885 i get:
> # modprobe cx23885
> modprobe: ERROR: could not insert 'cx23885': Exec format error
>
> and on dmesg i get:
> frame_vector: exports duplicate symbol frame_vector_create (owned by
Hello
if i use media_build and modprobe cx23885 i get:
# modprobe cx23885
modprobe: ERROR: could not insert 'cx23885': Exec format error
and on dmesg i get:
frame_vector: exports duplicate symbol frame_vector_create (owned by kernel)
any idea whats causing this?
this prevents one of my cards
When the rc_map table is created the char pointer of the name of the keymap
is copied to the rc_map->name field. However, this pointer points to memory
from the keymap module itself.
Since these keymap modules are not refcounted, that means anyone can call
rmmod to unload that module. Which is
--
Job title: Escrow Officer #216
An-gang Steel Company Limited
China Anshan Iron and Steel Co. Ltd.
www.ansteel.com.cn
It is my pleasure to announce to you the vacancy for the post of an
Escrow Online Officer for An-gang Steel Company Limited China. if you
are interested, please reply for
12 matches
Mail list logo