From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Re: Re: Re: hciattach problem
Date: Sat, 05 Feb 2005 20:18:18 +0100 [thread overview]
Message-ID: <1107631098.6921.187.camel@pegasus> (raw)
In-Reply-To: <42051547.5030301@web.de>
Hi Andreas,
> > please check 2.6.10-mh1 against 2.6.10-mh2, because otherwise we can't
> > find the problem. All your other kernels differ too much. The "csr"
> > option indicates H:4.
>
> I have compiled a kernel 2.6.10-mh1 and a -mh2. I have tested it, and
> now there's no problem. I don't know why, but now there is no freez.
> Maybe I have done something wrong with the compiling. Or do I have to
> compile the bluez-utils/libs now with each kernel?
no. The libs and utils will not change the behaviour of your kernel. I
think you had an experimental patch in one of the kernels that causes
your problem. May you wanna also check the 2.6.11-rc3 to be sure that
everything is fine.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-05 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 18:49 [Bluez-devel] Re: Re: Re: Re: hciattach problem Andreas Millinger
2005-02-05 19:18 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-04 15:25 Andreas Millinger
2005-02-04 15:51 ` 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=1107631098.6921.187.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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