All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Thomae <thomae@ei.tum.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Stephen Crane <steve.crane@rococosoft.com>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] New Bluetooth kernel patches available
Date: Tue, 16 Dec 2003 10:22:21 +0100	[thread overview]
Message-ID: <3FDECECD.2050001@ei.tum.de> (raw)
In-Reply-To: <1071528118.6526.126.camel@pegasus>

Hi Stephen, Marcel, all,

Marcel Holtmann wrote:
>>2.4.18 is needed for the Sharp Zaurus (ROM 3.10) and actually using a BT
>>keyboard would be way cool :-)

I think so, too, especially when there are foldable keyboards available 
:), see http://www.heise.de/newsticker/data/dal-11.12.03-000/

> do you know what Bluetooth stack is used by Sharp in their ROM?

AFAIK, they have no built-in bluetooth support, but there is a variant 
of the Sharp ROM from theKompany 
(http://www.thekompany.com/embedded/rom/) which has BlueZ support 
(stemming from http://tumnus.zaurii.net/, please anyone correct me if I 
am wrong).

Also, the current testing version of OpenZaurus (3.3.5) 
(http://www.openzaurus.org/oz_website/content/news)
uses a 2.4.18 kernel, and bluez seems to run with the packages from 
tumnus and an Anycom CF card on my SL-5500.

However, the OZ developers see the 2.4.18 based OZ as an interim 
solution until they have their own port of the 2.4.21 kernel, see 
http://openzaurus.org/newsletters/2003.12/

So it would be nice if the 2.4.21 could also be maintained!

But maybe Marcel would want to contact the OZ developers directly (e.g. 
via openzaurus-devel@lists.sourceforge.net) to talk about their plans. I 
am sure they are interested in BlueZ support for OZ, especially with the 
coming Zaurus SL-6000 that has a built-in bluetooth module.

Regards.
Matthias

  reply	other threads:[~2003-12-16  9:22 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 [this message]
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=3FDECECD.2050001@ei.tum.de \
    --to=thomae@ei.tum.de \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --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.