From: Stefan Bauer <stefan.bauer@cs.tu-chemnitz.de>
To: Janne Grunau <j@jannau.net>
Cc: Jarod Wilson <jwilson@redhat.com>,
linux-kernel@vger.kernel.org,
Christoph Bartelmus <lirc@bartelmus.de>
Subject: Re: [PATCH 02/18] lirc serial port receiver/transmitter device driver
Date: Fri, 26 Sep 2008 21:42:01 +0200 [thread overview]
Message-ID: <200809262142.01801.stefan.bauer@cs.tu-chemnitz.de> (raw)
In-Reply-To: <200809200210.33597.j@jannau.net>
Hi,
On Saturday 20 September 2008 02:10, Janne Grunau wrote:
> but lirc serial still doesn't work after
> bc2039245c6390bd414a61c9395604c4155a58c6. I'll look at it tomorrow.
just to tell you that I'm still there... :) Todays git
(a842c8095aad7b71ffcd1e426185e53661d758c7) is also giving me this at first
access to the device by lircd:
------------[ cut here ]------------
WARNING: at drivers/input/lirc/lirc_dev.h:37
lirc_buffer_clear+0x2c/0x30 [lirc_dev]()
calling lirc_buffer_clear on an uninitialized lirc_buffer
Modules linked in: lirc_serial lirc_dev ves1820 arc4 ecb crypto_blkcipher
cryptomgr crypto_algapi rt61pci rt2x00pci rt2x00lib led_class dvb_ttpci
saa7146_vv saa7146 videobuf_dma_sg mac80211 videobuf_core videodev ehci_hcd
uhci_hcd ttpci_eeprom cfg80211 eeprom_93cx6 [last unloaded: lirc_dev]
Pid: 5144, comm: lircd Not tainted 2.6.27-rc5 #7
[<c01151ce>] warn_slowpath+0x61/0x84
[<c015971f>] __d_lookup+0x8b/0xbf
[<c0151f26>] do_lookup+0x40/0x92
[<c0158f6d>] dput+0x15/0x8d
[<c0153533>] __link_path_walk+0x7ad/0x8b4
[<c0153533>] __link_path_walk+0x7ad/0x8b4
[<c01de0c1>] kobject_get+0xf/0x13
[<c014dfbb>] cdev_get+0x1b/0x2d
[<c014dfd4>] exact_lock+0x7/0xd
[<c0242154>] kobj_lookup+0xda/0x104
[<ca9fa15a>] lirc_buffer_clear+0x2c/0x30 [lirc_dev]
[<ca9fa4f4>] lirc_dev_fop_open+0x9e/0x135 [lirc_dev]
[<c014e15c>] chrdev_open+0xc1/0xf6
[<c014e09b>] chrdev_open+0x0/0xf6
[<c014b052>] __dentry_open+0xf2/0x1da
[<c014b156>] nameidata_to_filp+0x1c/0x2c
[<c01544ae>] do_filp_open+0x28b/0x545
[<c015bc37>] alloc_fd+0x46/0xad
[<c014ae8d>] do_sys_open+0x42/0xb6
[<c014af45>] sys_open+0x1e/0x23
[<c010297d>] sysenter_do_call+0x12/0x25
[<c02f0000>] ioctl_standard_iw_point+0x12d/0x200
=======================
---[ end trace 6c8eb5cbb580deaf ]---
Regards,
Stefan
next prev parent reply other threads:[~2008-09-26 19:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 19:49 Stefan Bauer
2008-09-12 16:24 ` Jarod Wilson
2008-09-13 0:26 ` Janne Grunau
2008-09-13 8:41 ` Stefan Bauer
2008-09-15 3:55 ` Jarod Wilson
2008-09-15 18:20 ` Jarod Wilson
2008-09-16 4:08 ` Jarod Wilson
2008-09-18 14:00 ` Jarod Wilson
2008-09-19 18:05 ` Stefan Bauer
2008-09-19 18:26 ` Janne Grunau
2008-09-19 18:53 ` Stefan Bauer
2008-09-19 19:24 ` Janne Grunau
2008-09-20 0:10 ` Janne Grunau
2008-09-26 19:42 ` Stefan Bauer [this message]
2008-09-19 18:54 ` Jarod Wilson
2008-09-19 19:12 ` Stefan Bauer
2008-09-13 7:09 ` Christoph Bartelmus
-- strict thread matches above, loose matches on Subject: below --
2008-09-09 4:05 [PATCH 0/18] linux infrared remote control drivers Jarod Wilson
2008-09-09 4:05 ` [PATCH 01/18] lirc core device driver infrastructure Jarod Wilson
2008-09-09 4:05 ` [PATCH 02/18] lirc serial port receiver/transmitter device driver Jarod Wilson
2008-09-09 16:14 ` Jonathan Corbet
2008-09-09 19:51 ` Stefan Lippers-Hollmann
2008-09-09 19:56 ` Jarod Wilson
2008-09-10 17:40 ` Jarod Wilson
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=200809262142.01801.stefan.bauer@cs.tu-chemnitz.de \
--to=stefan.bauer@cs.tu-chemnitz.de \
--cc=j@jannau.net \
--cc=jwilson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirc@bartelmus.de \
/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
Powered by JetHome