From: Wim Osterholt <wim@djo.tudelft.nl>
To: jarod@wilsonet.com
Cc: linux-kernel@vger.kernel.org, Wim Osterholt <wim@djo.tudelft.nl>
Subject: lirc bug in kernel 4.10-rc3
Date: Tue, 10 Jan 2017 19:55:29 +0100 [thread overview]
Message-ID: <20170110185529.GA4645@djo.tudelft.nl> (raw)
In-Reply-To: <20170107161138.GA10065@djo.tudelft.nl>
On Sat, Jan 07, 2017 at 05:11:38PM +0100, Wim Osterholt wrote:
> On Thu, Dec 29, 2016 at 05:53:58PM +0100, Wim Osterholt wrote:
>
> L.S.,
> >
> > after appearance of kernel-4.10-rc1 two days ago...
>
> A quickly following release of 4.10-rc2 made sure that lirc_dev was loaded
> together with serial_ir. However, things still don't work.
Again no answer and another kernel release, but no fixes.
I just need to only send some codes.
I'm using (gentoo) lirc-0.9.0-rc6, which works fine up to kernel-4.9.2 .
In kernel-4.10-rc1/2/3 there are two bugs.
1) With the same setup - only the kernel has changed from 4.9 to 4.10 -
irsend does not work anymore. I get these logs:
> Jan 7 01:55:23 localhost kernel: serial_ir: unknown parameter 'debug' ignored
> Jan 7 01:55:24 localhost kernel: serial_ir serial_ir.0: auto-detected active high receiver
> Jan 7 01:55:24 localhost kernel: rc_core: IR keymap rc-rc6-mce not found
> Jan 7 01:55:24 localhost kernel: Registered IR keymap rc-empty
> Jan 7 01:55:24 localhost kernel: input: Serial IR type home-brew as /devices/platform/serial_ir.0/rc/rc0/input10
> Jan 7 01:55:24 localhost kernel: rc rc0: Serial IR type home-brew as /devices/platform/serial_ir.0/rc/rc0
> Jan 7 01:55:24 localhost kernel: input: MCE IR Keyboard/Mouse (serial_ir) as /devices/virtual/input/input11
> Jan 7 01:55:24 localhost kernel: lirc_dev: IR Remote Control driver registered, major 249
> Jan 7 01:55:24 localhost kernel: rc rc0: lirc_dev: driver ir-lirc-codec (serial_ir) registered at minor = 0
> Jan 7 01:55:24 localhost kernel: IR LIRC bridge handler initialized
> Jan 7 01:55:56 localhost lircd-0.9.0[2171]: lircd(default) ready, using /dev/lircd1
> Jan 7 01:56:52 localhost lircd-0.9.0[2171]: accepted new client on /dev/lircd1
> Jan 7 01:56:52 localhost lircd-0.9.0[2171]: write failed
> Jan 7 01:56:52 localhost lircd-0.9.0[2171]: Invalid argument
> Jan 7 01:56:52 localhost lircd-0.9.0[2171]: error processing command: SEND_ONCE bat KEY_1
> Jan 7 01:56:52 localhost lircd-0.9.0[2171]: transmission failed
> Jan 7 01:56:53 localhost lircd-0.9.0[2171]: removed client
2) lirc-0.9.0 compiled with '--with-transmitter' delivers no transmitter in lirc_serial.ko
Regards, Wim.
prev parent reply other threads:[~2017-01-10 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 16:53 lirc bug in kernel 4.10-rc1 Wim Osterholt
2017-01-07 16:11 ` lirc bug in kernel 4.10-rc2 Wim Osterholt
2017-01-10 18:55 ` Wim Osterholt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170110185529.GA4645@djo.tudelft.nl \
--to=wim@djo.tudelft.nl \
--cc=jarod@wilsonet.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®