All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Crane <steve.crane@rococosoft.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] New Bluetooth kernel patches available
Date: 16 Dec 2003 09:40:18 +0000	[thread overview]
Message-ID: <1071567617.26094.457.camel@baroque.rococosoft.com> (raw)
In-Reply-To: <1071528118.6526.126.camel@pegasus>

Hi Marcel,

On Mon, 2003-12-15 at 22:41, Marcel Holtmann wrote:
> 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?

They don't have one explicitly. BlueZ works fine though!

> 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 :(

Yeah, it might be an idea just to forget about Sharp's and move to
Familiar.

Steve
-- 
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)

  parent reply	other threads:[~2003-12-16  9:40 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
2003-12-16  9:22     ` Matthias Thomae
2003-12-16  9:40     ` Stephen Crane [this message]
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=1071567617.26094.457.camel@baroque.rococosoft.com \
    --to=steve.crane@rococosoft.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.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 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.