Return-Path: <x.garreau@prim-time.fr>
Message-ID: <005b01c34067$f5469a80$0181a8c0@zaz1>
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>
References: <1054908696.4791.157.camel@baroque.rococosoft.com>
	<200306301314.25320.justin-qt@affinix.com>
	<1057064408.15797.20.camel@pegasus>
	<200307011438.34033.justin-qt@affinix.com>
Subject: Re: [Bluez-devel] [ANN] Zaurus BlueZ kernel packages for ROM v3.10
Date: Wed, 2 Jul 2003 09:02:53 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
List-ID: <bluez-devel.lists.sourceforge.net>

> 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