From: "Xavier Garreau" <x.garreau@prim-time.fr>
To: "Justin Karneges" <justin-qt-dated-1058334576.aa81a3@affinix.com>,
"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: Wed, 2 Jul 2003 09:02:53 +0200 [thread overview]
Message-ID: <005b01c34067$f5469a80$0181a8c0@zaz1> (raw)
In-Reply-To: 200307011438.34033.justin-qt@affinix.com
> 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?
Laptops are affected as well, at least those using bc3c_cs...
BR
--
Xavier Garreau
next prev parent reply other threads:[~2003-07-02 7:02 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
2003-07-02 0:26 ` Marcel Holtmann
2003-07-02 1:10 ` Justin Karneges
2003-07-02 7:02 ` Xavier Garreau [this message]
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='005b01c34067$f5469a80$0181a8c0@zaz1' \
--to=x.garreau@prim-time.fr \
--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 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.