From: "Pierre Savary" <pierre.savary@kerlink.fr>
To: "'Marcel Holtmann'" <marcel@holtmann.org>
Cc: "'BlueZ-Dev'" <bluez-devel@lists.sourceforge.net>,
<bluez-users@lists.sourceforge.net>,
<linux-bluetooth@vger.kernel.org>
Subject: RE: problems with kernel 2.6.23 + bluez 3.36 + SCO
Date: Wed, 29 Oct 2008 15:49:28 +0100 [thread overview]
Message-ID: <001701c939d5$8b94c590$a2be50b0$@savary@kerlink.fr> (raw)
In-Reply-To: <1224737867.9386.184.camel@californication>
I it possible to update only the bluez stack ???
Thanks in advance,
Regards
Pierre
-----Message d'origine-----
De=A0: linux-bluetooth-owner@vger.kernel.org
[mailto:linux-bluetooth-owner@vger.kernel.org] De la part de Marcel =
Holtmann
Envoy=E9=A0: jeudi 23 octobre 2008 06:58
=C0=A0: Pierre Savary
Cc=A0: BlueZ-Dev; bluez-users@lists.sourceforge.net;
linux-bluetooth@vger.kernel.org
Objet=A0: Re: problems with kernel 2.6.23 + bluez 3.36 + SCO
Hi Pierre,
> We develop an application for our board based on SCO. We use the =
kernel
> version 2.6.23 and the bluez-lib 3.36. However we have a lot of =
problems
and
> some "kernel panic". Below this message you will find some of these =
kernel
> messages.
> How can we stop it? Have you ever saw that?
switch to a 2.6.27 kernel.
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe =
linux-bluetooth"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-10-29 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 14:13 problems with kernel 2.6.23 + bluez 3.36 + SCO Pierre Savary
2008-10-23 4:57 ` Marcel Holtmann
2008-10-24 9:18 ` [Bluez-devel] " rakesh agarwal
2008-10-24 10:22 ` Marcel Holtmann
2008-10-29 14:49 ` Pierre Savary [this message]
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='001701c939d5$8b94c590$a2be50b0$@savary@kerlink.fr' \
--to=pierre.savary@kerlink.fr \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-users@lists.sourceforge.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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