From: johannes hoerhan <jhoe@aon.at>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] rfcomm kernel 2.6.19 probs
Date: Wed, 13 Dec 2006 16:04:44 +0100 [thread overview]
Message-ID: <4580168C.2060806@aon.at> (raw)
I am using bluetooth to conntect my laptop and my palm for browsing the
web to my linux workstation. Everything were working perfect untill I
updated to kernel 2.6.19.
The devices could not connect to my workstation anymore - got a timeout
error. Currently I am running:
Workstation:
gentoo-2006.1,
kernel 2.6.19-r2
bluez-libs 2.25
bluez-utils 2.25-r1
In my workstation's log I found:
kernel message: rfcomm_tty_ioctl: TIOCGSERIAL is not supported.
and the /dev/rfcommX device is not created.
For troubleshooting I had a look at you patch 2.6.18-mh8 and found out
that this patches tty.c. I found out that "reversing" the patch at
net/bluetooth/rfcomm/tty.c
In function:
static struct device *rfcomm_get_device(struct rfcomm_dev *dev)
....
/*tty_register_device(rfcomm_tty_driver, dev->id,
rfcomm_get_device(dev));*/
tty_register_device(rfcomm_tty_driver, dev->id, NULL);
is enough to get everything working again.
So my questions: is this a bug or do I have to change my setup? Is there
any other solution than patching the file each time updating the kernel?
regards,
johoe
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-12-13 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 15:04 johannes hoerhan [this message]
2006-12-17 12:47 ` [Bluez-devel] rfcomm kernel 2.6.19 probs Marcel Holtmann
2006-12-18 21:04 ` Markus Uhr
2006-12-19 0:25 ` Johannes Hoerhan
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=4580168C.2060806@aon.at \
--to=jhoe@aon.at \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.