All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Crane <steve.crane@rococosoft.com>
To: Justin Karneges <justin-qt@affinix.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
	marcel@rvs.uni-bielefeld.de
Subject: Re: [Bluez-devel] [ANN] Zaurus BlueZ kernel packages for ROM v3.10
Date: 01 Jul 2003 12:45:39 +0100	[thread overview]
Message-ID: <1057059939.523.34.camel@baroque.rococosoft.com> (raw)
In-Reply-To: <200307010227.38094.justin-qt@affinix.com>

See http://www.holtmann.org/linux/bluetooth/dtl1.html

It was only merged in 2.4.20 and 2.5.30. Perhaps Marcel needs to provide
it in his BlueZ patch for 2.4.18 and 2.4.19?

On Tue, 2003-07-01 at 10:27, Justin Karneges wrote:
> Excellent, Stephen. :)
> 
> What about the kernel modules?  By the way, is dtl1_cs meant to be separated 
> from the kernel?  I didn't see it in 2.4.18 even after applying 
> patch-2.4.18-mh7.
> 
> -Justin
> 
> On Tuesday 01 July 2003 02:12 am, Stephen Crane wrote:
> > Justin,
> > You can cross-compile the user-space parts of BlueZ as follows:
> >
> > export CC=arm-linux-gcc
> > export LD=arm-linux-ld
> > export NM=arm-linux-nm
> > export RANLIB=arm-linux-ranlib
> > export PATH=/opt/Embedix/tools/bin:$PATH
> > ./configure --prefix=/opt/Embedix/tools/arm-linux --host=arm-linux
> > make
> >
> > (This is how I do it anyway.)
> >
> > On Mon, 2003-06-30 at 21:14, Justin Karneges wrote:
> > > > > By the way, you may see my GUI package here:
> > > > >   http://www.affinix.com/~justin/zaurus-bluetooth-0.6.tar.gz
> > > >
> > > > This can be added in the utils package. I think we need a kernel
> > > > package, a libs package and a utils package. But it can be further
> > > > discussed...
> > >
> > > What I'd like is to have an official "zaurus bluetooth" CVS for all of
> > > this stuff, that can be periodically sync'ed with bluez.  Then we can
> > > generate packages however we wish.  Personally, I just want one package
> > > that has everything.  A newbie should be able to install the "Zaurus
> > > Bluetooth package" and be up and running, without touching the command
> > > line.
> >
> > I disagree about the need for an official Zaurus CVS. We can put the
> > scripts to build the Zaurus packages in the normal place (as is done for
> > the rpm spec files).
> >
> > > I'm willing to create builds too, as soon as I can figure out how to
> > > actually do it.  It seems I'm able to build the libs / utils by hand
> > > (running arm-linux-gcc on each file and taking what i need.  can't seem
> > > to use autotools correctly ...), but I've had no luck with building
> > > kernel modules (they just crash when used).  What is your secret?  Got
> > > any URLs?
> > >
> > > Also, I think I found a bug in dtl1_cs and/or bluez itself:  the card
> > > cannot survive a suspend.  Turning off / on the Zaurus, or simply running
> > > "cardctl suspend ; cardctl resume" will leave the driver in an unusable
> > > state. Running "cardctl eject ; cardctl insert" fixes the problem.  I'm
> > > willing to hack on the driver and remedy this, if I could just figure out
> > > how to cross-compile the modules...
> 
> 
> -------------------------------------------------------
> 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
-- 
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)

  reply	other threads:[~2003-07-01 11:45 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
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 [this message]
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=1057059939.523.34.camel@baroque.rococosoft.com \
    --to=steve.crane@rococosoft.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=justin-qt@affinix.com \
    --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 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.