From: Stephen Crane <steve.crane@rococosoft.com>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [ANN] Zaurus BlueZ kernel packages for ROM v3.10
Date: 09 Jun 2003 11:56:48 +0100 [thread overview]
Message-ID: <1055156207.4791.301.camel@baroque.rococosoft.com> (raw)
In-Reply-To: <1054913828.26827.45.camel@pegasus>
Hi Marcel,
On Fri, 2003-06-06 at 16:37, Marcel Holtmann wrote:
> the current Zaurus packages are done by Joseph Ecker and the kernel
> modules are based on the deprecated bluez-kernel-2.3 package. It seems
> that it is really time to have up-to-date kernel modules for the Zaurus.
> Frist I don't like Joseph last choise to put the userspace tools and the
> kernel modules into one big package. I like to see the kernel stuff
> seperated from the userspace tools.
Yeah me too. Particularly because it's much easier to build the
user-space tools with a cross-compiler.
> However I have no Zaurus, so I can't
> help with that. But some time ago I put some scripts in the BlueZ kernel
> CVS repository which makes it possible to compile and install the
> Bluetooth modules outside the kernel source. Maybe you should take a
> look at it and provide some easy to install ipk packages.
I will think about doing this if I get some time. For now, I have
uploaded the latest basic user-space binaries separately to
ftp://rococosoft.com/pub/zaurus with instructions for installing them in
the right places. It would not be too hard to write packaging scripts
for them --- indeed this is something anyone could do using the
ipkg-build script; volunteers?
> The OpenZaurus project will use a 2.4.19 in future and hopefully they
> include my patch. Do anyone have details about this.
We only have 2 Zauruses here (one with the older Sharp ROM and the other
with the new one) so I can't try OpenZaurus :-(
Steve
--
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)
next prev parent reply other threads:[~2003-06-09 10:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 14:11 [Bluez-devel] [ANN] Zaurus BlueZ kernel packages for ROM v3.10 Stephen Crane
2003-06-06 15:37 ` Marcel Holtmann
2003-06-09 10:56 ` Stephen Crane [this message]
2003-06-11 15:33 ` Xavier Garreau
2003-06-11 15:36 ` Xavier Garreau
2003-06-29 3:05 ` Justin Karneges
2003-06-29 4:17 ` Justin Karneges
2003-06-30 12:46 ` Xavier Garreau
2003-06-30 20:14 ` Justin Karneges
2003-07-01 7:12 ` Xavier Garreau
2003-07-01 7:50 ` Justin Karneges
2003-07-01 9:12 ` Stephen Crane
2003-07-01 9:27 ` Justin Karneges
2003-07-01 11:45 ` Stephen Crane
2003-07-01 13:02 ` Marcel Holtmann
2003-07-01 11:50 ` Stephen Crane
2003-07-01 13:00 ` Marcel Holtmann
2003-07-01 21:38 ` Justin Karneges
2003-07-02 0:26 ` Marcel Holtmann
2003-07-02 1:10 ` Justin Karneges
2003-07-02 7:02 ` Xavier Garreau
2003-07-02 8:37 ` 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=1055156207.4791.301.camel@baroque.rococosoft.com \
--to=steve.crane@rococosoft.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@rvs.uni-bielefeld.de \
/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