From: Wim Osterholt <wim@djo.tudelft.nl>
To: jarod@wilsonet.com
Cc: wim@djo.tudelft.nl, linux-kernel@vger.kernel.org
Subject: lirc bug in kernel 4.10-rc1
Date: Thu, 29 Dec 2016 17:53:58 +0100 [thread overview]
Message-ID: <20161229165358.GA3410@djo.tudelft.nl> (raw)
L.S.,
after appearance of kernel-4.10-rc1 two days ago I was pleasantly surprised
to find a question about lirc_serial in 'make oldconfig':
Homebrew Serial Port Receiver (IR_SERIAL) [N/m/?] (NEW) m
Serial Port Transmitter (IR_SERIAL_TRANSMITTER) [Y/n/?] y
I was used to 'lirc_serial: module is from the staging directory, the quality
is unknown, you have been warned.'
This always worked perfectly fine with the last working version of lirc: 0.9.0-rc6.
Would things finally get better now? NO!
In kernel-4.10-rc1 lirc_serial has been removed from staging. It has vanished
completely. If it were only renamed to serial_ir there would be no problem.
I just change the modules parameters
options lirc_serial irq=4 io=0x3f8 type=0 txsense=0 softcarrier=0 debug=1
to
options serial_ir irq=4 io=0x3f8 type=0 txsense=0 softcarrier=0 debug=1
and it should work, isn't it?
(Oh, whell, the kernel stuff has no option 'debug'..)
Serial_ir loads without useful messages.
Lirc_dev does not get loaded with it. Loading it manually or not doesn't
make any difference.
Irsend will not work. 'hardware does not support sending'
There's another bug of which I don't know wether it is a kernel issue or a
lirc issue.
On kernel 4.9 (and below) lirc compiles modules lirc_serial and lirc_dev
which work equally well as the in-kernel modules lirc-serial and lirc_dev.
You may even exchange them independently. The only difference is that the
lirc version knows about the parameter 'debug'.
When I let /usr/src/linux point to 4.10-rc1, then the exact same source of
lirc does not compile the transmitter part and things don't work!
So using the lirc modules is not even an alternative anymore.
Did I miss something?
(For lirc-0.9.0 you'll need a missing patch for the vanished f_dentry stuff
in the kernel source.)
Regards, Wim.
next reply other threads:[~2016-12-29 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 16:53 Wim Osterholt [this message]
2017-01-07 16:11 ` lirc bug in kernel 4.10-rc2 Wim Osterholt
2017-01-10 18:55 ` lirc bug in kernel 4.10-rc3 Wim Osterholt
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=20161229165358.GA3410@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®