From: Justin Karneges <justin-qt@affinix.com>
To: "Xavier Garreau" <x.garreau@prim-time.fr>,
Stephen Crane <steve.crane@rococosoft.com>
Cc: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [ANN] Zaurus BlueZ kernel packages for ROM v3.10
Date: Sat, 28 Jun 2003 20:05:08 -0700 [thread overview]
Message-ID: <200306282005.08403.justin-qt@affinix.com> (raw)
In-Reply-To: <005f01c3302e$ca3537a0$0181a8c0@zaz1>
Hi,
I'm working towards easy Bluetooth on the Zaurus. I have a bluez GUI tool and
qtopia dialer plugin in the works.
However, getting bluez installed was never easy. In the past, I was using the
ipks available at bluez.sf.net, which were never very complete.
Today, I sought to remedy this, and tried cross compiling modules and the
libs/utilities. I ran into a heap of trouble, and then discovered this
thread. I'm glad someone else is looking into this stuff too. :)
My original goal was to get this working with kernel 2.4.6, but I'm not sure
how realistic that is. I didn't know about the new sharp ROM until today,
which I have now installed. I guess it is acceptable to work with this as a
target, and considering it comes with kernel 2.4.18, it should make a lot of
things easier.
Xavier's package looks good. The only flaw I think is that it does not set up
/etc/bluetooth.
I'd like to see some secrets shared. Could Steve or Xavier respond to me here
or on the list, so that we can make something more official?
-Justin
On Wednesday 11 June 2003 08:33 am, Xavier Garreau wrote:
> > > 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.
>
> Not in this release.
>
> > 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?
>
> I did it : http://fichiers.xgarreau.org/zaurus/bluez_2.4.18_arm.ipk
>
> It installs the files in the right directories, make the symlinks, try to
> guess what card it is and bring device up.
>
> Please keep me informed of new builds so that i keep the package up to
> date.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-06-29 3:05 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
2003-06-11 15:33 ` Xavier Garreau
2003-06-11 15:36 ` Xavier Garreau
2003-06-29 3:05 ` Justin Karneges [this message]
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=200306282005.08403.justin-qt@affinix.com \
--to=justin-qt@affinix.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=justin-qt-dated-1058094956.869933@affinix.com \
--cc=steve.crane@rococosoft.com \
--cc=x.garreau@prim-time.fr \
/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