From: Florian Echtler <floe@butterbrot.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] 2.4 Kernel hacking question
Date: Tue, 28 Mar 2006 09:15:19 +0200 [thread overview]
Message-ID: <1143530119.9151.5.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
Hello everybody,
as already mentioned in some earlier post, I've backported the most
recent BlueZ modules from kernel 2.4.31-mh1 to a custom kernel 2.4.20.
I know that the 2.4 branch is considered unsupported by now, but maybe
somebody can answer my question regardless:
in rfcomm/tty.c, line 592, a function tty_wakeup() is used that isn't
available in 2.4.20 yet. Can anybody tell me what exactly this function
is supposed to do so that I can look for a workaround? (*)
CU Florian
(*) I've already looked at the kernel source, of course. Still haven't
got a real clue, though.. :-/
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
reply other threads:[~2006-03-28 7:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1143530119.9151.5.camel@localhost \
--to=floe@butterbrot.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox