From: Marcel Holtmann <marcel@holtmann.org>
To: Stephen Crane <steve.crane@rococosoft.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] New Bluetooth kernel patches available
Date: Mon, 15 Dec 2003 23:41:59 +0100 [thread overview]
Message-ID: <1071528118.6526.126.camel@pegasus> (raw)
In-Reply-To: <1071507511.26243.452.camel@baroque.rococosoft.com>
Hi Stephen,
> 2.4.18 is needed for the Sharp Zaurus (ROM 3.10) and actually using a BT
> keyboard would be way cool :-)
do you know what Bluetooth stack is used by Sharp in their ROM?
I hope that until CeBIT I get a demo with ISDN and HID running on my
iPAQ and make some people google.
> I'd say maintain it and 2.4.23.
The 2.4.18 is the one that takes the most time :(
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-12-15 22:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 16:30 [Bluez-devel] New Bluetooth kernel patches available Marcel Holtmann
2003-12-15 16:58 ` Stephen Crane
2003-12-15 22:41 ` Marcel Holtmann [this message]
2003-12-16 9:22 ` Matthias Thomae
2003-12-16 9:40 ` Stephen Crane
2003-12-18 14:57 ` Aaron Klish
2003-12-18 16:16 ` Marcel Holtmann
2003-12-18 17:49 ` Aaron Klish
2003-12-18 17:53 ` Aaron Klish
2003-12-18 18:03 ` Marcel Holtmann
2003-12-19 18:00 ` Daryl Van Vorst
-- strict thread matches above, loose matches on Subject: below --
2004-03-15 23:30 Marcel Holtmann
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=1071528118.6526.126.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=steve.crane@rococosoft.com \
/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.