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: Fri, 04 Feb 2005 16:51:07 +0100 [thread overview]
Message-ID: <1107532267.6921.46.camel@pegasus> (raw)
In-Reply-To: <420393FA.2070509@web.de>
Hi Andreas,
> I have checked the bluez-utils/libs versions and it doesn't depend on
> it. The Kernel I have tested with is a vanilla kernel with bootsplash,
> subfs and tiocgdev patches. The 2.6.11-rc2 is a Kernel-of-the-Day kernel
> from Suse. I attach the card with hciattach ttyS16 csr. That is H4,
> isn't it? Isn't the problem there with other cards? I will check with a
> clean vanilla-kernel.
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.
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-04 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 15:25 [Bluez-devel] Re: Re: Re: Re: hciattach problem Andreas Millinger
2005-02-04 15:51 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-05 18:49 Andreas Millinger
2005-02-05 19:18 ` 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=1107532267.6921.46.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 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.