All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] specific bluetooth configuration
Date: Thu, 03 Feb 2005 00:41:10 +0100	[thread overview]
Message-ID: <1107387670.11944.23.camel@pegasus> (raw)
In-Reply-To: <4201644B.5050302@ynet.sk>

Hi Kevin,

> In my kernel (2.6.9) are this bluetooth settings:
> CONFIG_BT=y
> CONFIG_BT_L2CAP=y
> # CONFIG_BT_SCO is not set
> # CONFIG_BT_RFCOMM is not set
> CONFIG_BT_BNEP=y
> # CONFIG_BT_BNEP_MC_FILTER is not set
> # CONFIG_BT_BNEP_PROTO_FILTER is not set
> # CONFIG_BT_HIDP is not set
> #
> # Bluetooth device drivers
> #
> CONFIG_BT_HCIUART=y
> CONFIG_BT_HCIUART_H4=y
> # CONFIG_BT_HCIUART_BCSP is not set
> # CONFIG_BT_HCIVHCI is not set
> # CONFIG_NETDEVICES is not set
> 
> My question is, if with this configuration is possible to make stable 
> bluetooth communications(f.g. with mobile phone).And if Yes, how?

only if your mobile phone supports the PAN profile and your host adapter
is using the H:4 transport protocol.

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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-02-02 23:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 23:37 [Bluez-users] specific bluetooth configuration kevin_m
2005-02-02 23:41 ` Marcel Holtmann [this message]
2005-02-03  0:23   ` kevin_m
2005-02-03 11:07     ` 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=1107387670.11944.23.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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.