From: Stephen Crane <steve.crane@rococosoft.com>
To: bluez-announce@lists.sourceforge.net
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] [ANN] Zaurus BlueZ kernel packages for ROM v3.10
Date: 06 Jun 2003 15:11:37 +0100 [thread overview]
Message-ID: <1054908696.4791.157.camel@baroque.rococosoft.com> (raw)
Hi,
I don't want to preempt the official packager of the Zaurus BlueZ
distribution but I couldn't wait for Sharp to get around to distributing
the kernel source and needed to try out BlueZ on the new ROM.
So I built BlueZ kernel modules from a vanilla 2.4.18 plus Marcel's
2.4.18-mh6 patch-set and a bit of tweaking to the 2.4.6 kernel config
file.
>>From cursory testing, they seem to be ok: bluecard_cs is successfully
loaded and the latest versions of hciconfig, hcitool and sdptool all
work fine. (However YMMV, no warranty, don't blame me if your Z catches
fire, etc.)
I've uploaded them to our anonymous ftp area, along with the PCMCIA
configuration files, bluetooth and bluetooth.conf. Get them from
ftp://rococosoft.com/pub/zaurus
Installation:
* unpack the tar-ball in the /home/root/modules/2.4.18-rmk7-pxa3-embedix
directory
* run depmod -ae
* install bluetooth and bluetooth.conf in /etc/pcmcia
* run /etc/rc.d/init.d/pcmcia restart
Cheers,
Steve
--
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2003-06-06 14:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 14:11 Stephen Crane [this message]
2003-06-06 15:37 ` [Bluez-devel] [ANN] Zaurus BlueZ kernel packages for ROM v3.10 Marcel Holtmann
2003-06-09 10:56 ` Stephen Crane
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=1054908696.4791.157.camel@baroque.rococosoft.com \
--to=steve.crane@rococosoft.com \
--cc=bluez-announce@lists.sourceforge.net \
--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