From: Andreas Millinger <andreas.millinger@web.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Re: Re: Re: hciattach problem
Date: Fri, 04 Feb 2005 16:25:46 +0100 [thread overview]
Message-ID: <420393FA.2070509@web.de> (raw)
Hello Marcel,
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.
Regards
Andreas
>Hi Andreas,
>
>
>>> I will check that with the the different bluez-utils/lib versions. But the Card is using H4. I have tried BCSP, too, but there is a Timeout error.
>>
>
>I can't remember a change between -mh1 and -mh2 that would affect the
>H:4 part of the hci_uart driver. Are you sure that these are clean
>vanilla kernels with only my patch applied?
>
>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 reply other threads:[~2005-02-04 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 15:25 Andreas Millinger [this message]
2005-02-04 15:51 ` [Bluez-devel] Re: Re: Re: Re: hciattach problem Marcel Holtmann
-- 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=420393FA.2070509@web.de \
--to=andreas.millinger@web.de \
--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