Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] HCI-Uart Driver & Kernel 2.4.25 , Headset/Handsfree Profile
Date: Tue, 17 May 2005 13:25:42 +0200	[thread overview]
Message-ID: <1116329143.10063.38.camel@pegasus> (raw)
In-Reply-To: <OF9A811F48.3D259B3A-ONC1257004.002BB233-C1257004.002F049A@telemotive.de>

Hi Markus,

> I=B4m trying to get the Handsfree/Headset-Profile running on an embedde=
d
> power pc-platform using the 2.4.25 kernel and a bluetooth module=20
> which is connected to the host processor via UART-Interface. =20

first of all, about what kind of Bluetooth chip are we talking here?
What speed is the UART running?

> The strange thing is that all other profiles work fine (OBEX, DUN
> etc.)=20
> but when it comes to transfer synchronous data in both directions like
> the handsfree profile does, I got an error message from=20
> the kernel like "unkown HCI packet type 00 received".=20

The ACL link is protected by the HCI flow control and the SCO link is
not by default if I remember correctly.

> Although there were no additional error messages from the kernel like
> buffer overruns of the UART interface, the first thing I thought
> about =20
> was that there might by something wrong with the hardware handshake of
> the UART interface, but I managed to connect the bluetooth module =20
> via RS232 to a normal PC running linux kernel 2.6 even without RTS and
> CTS lines of the UART interface connected (only RXD & TXD). =20
> Here everything works fine, so the problem is surely not caused by a
> missing/buggy hardware handshake.=20

Don't mix 2.4 with 2.6 results on different hardware platforms. This
means nothing and the serial subsystem has been reworked within the 2.6
kernel series.

> It would be a hard work to upgrade from kernel 2.4  to 2.6 on our
> platform since we already applied many changes to the kernel (not
> concerning bluez),=20

You should really check if it is so hard to upgrade and if not all of
your applied patches are already merged into the 2.6 kernel. Sticking
with a 2.4 kernel is a bad idea. Even for the Bluetooth part, since I
stopped backporting things.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2005-05-17 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  8:33 [Bluez-devel] HCI-Uart Driver & Kernel 2.4.25 , Headset/Handsfree Profile Markus.Heininger
2005-05-17  9:26 ` gao.yingbin
2005-05-17 11:25 ` Marcel Holtmann [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=1116329143.10063.38.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