Linux bluetooth development
 help / color / mirror / Atom feed
From: Justin Karneges <justin-qt@affinix.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: Tue, 01 Jul 2003 14:38:34 -0700	[thread overview]
Message-ID: <200307011438.34033.justin-qt@affinix.com> (raw)
In-Reply-To: <1057064408.15797.20.camel@pegasus>

> the two big parts with BlueZ are the kernel modules and the userspace
> stuff. The kernel stuff is the essential and the most problematic part.
> And I think that we should have a package which only contains the BlueZ
> kernel modules. Maybe we need different builds from the same source for
> Sharp Kernel 2.4.6, 2.4.18 and OpenZaurus Kernel 2.4.18, 2.4.19.

This would be nice, if indeed we can support this on 2.4.6.  Although, I 
believe the earlier Sharp ROM has similar suspending issues related to 
cardmgr (this is what Max told me in January).  For bluetooth to work 
reliably here, we may need to offer a cardmgr upgrade.

> I don't have a Zaurus, so I can't help here. Who wants to volunteer for
> the Zaurus kernel package maintainer?

I would like to volunteer for this, when I get a build setup working (I will 
try Stephen's soon).

> The BlueZ CVS module "kernel" contains a build system for building the
> BlueZ kernel modules outside a kernel source tree. I am willing to
> extend this as needed.

What extensions do you suppose are needed?

> > 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 is a known problem, but I don't have a Zaurus and so I can't test
> it. On my development machine is this working without any problems.

Do you have any hint about where it may be?  Maybe the Zaurus does not send 
appropriate signals to the driver that it is shutting down?  I'd like to look 
into this, but I need some direction first.  For instance, if it affects all 
drivers, not just dtl1_cs, then either all drivers have the same "bug", or 
the bug is in the bluez core, right?

What is significant about cardctl suspend?  This will break the driver also, 
and perhaps it easier to look into this than the full pda suspend.

-Justin

  reply	other threads:[~2003-07-01 21:38 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
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 [this message]
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=200307011438.34033.justin-qt@affinix.com \
    --to=justin-qt@affinix.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=justin-qt-dated-1058334576.aa81a3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox