f curiosity: Do you have CONFIG_HAVE_ARCH_SECCOMP_FILTER,
CONFIG_SECCOMP_FILTER
and CONFIG_SECCOMP enabled?
Forthermore, does this:
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
CONFIG_KERNEL_LZO=y
work for you ?
--
Ruediger "Rudi" Ihle
--
=y, which is not enabled in
sun4i_defconfig. It looks like there were some changes in that area
between 3.4.103 and 3.4.104. But I have not found the time to dig deeper.
--
Ruediger "Rudi" Ihle
--
You received this message because you are subscribed to the Google Groups
merged for some reason. I'm asking, because
this driver hooks into the rc-core subsystem and therefore works with any
protocol
driver present in the kernel. Not just NEC.
--
Ruediger Rudi Ihle
--
You received this message because you are subscribed to the Google Groups
linux-sunxi group
was against 3.4 ?)
I carefully put it aside ;-). Find a patch that hooks it into 3.4.79 here:
https://github.com/OpenBricks/openbricks/blob/master/config/platforms/arm/a10/packages/linux/patches/0002-ir-core-support.diff
--
Ruediger Rudi Ihle
--
You received this message because you
of the new LZO code, which
was in
3.4.67. I'm not 100% sure, but it may be related to the newly introduced
unaligned data
access feature. Could it be that the alignment checking is not disabled in the
CPU at
the time this code is run?
--
Ruediger Rudi Ihle
--
You received this message because
Hi folks,
starting with version 3.4.67 I get a crash on starting up the kernel when the
image uses
LZO compression (CONFIG_KERNEL_LZO=y). It seems to be related to unaligned data
access.
Anyone else seen this ?
--
Ruediger Rudi Ihle
--
You received this message because you
does not allow rates below
32kHz.
So if that works, it's just good luck. My Yamaha AVR for example would not
accept
anything these rates. Not even on S/PDIF.
--
Ruediger Rudi Ihle
--
You received this message because you are subscribed to the Google Groups
linux-sunxi group.
To unsubscribe
