Linux bluetooth development
 help / color / mirror / Atom feed
From: Imran Siddique <imran_stdu@yahoo.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluetooth devices connection problem
Date: Thu, 16 Nov 2006 08:13:19 -0800 (PST)	[thread overview]
Message-ID: <20061116161319.54202.qmail@web37710.mail.mud.yahoo.com> (raw)
In-Reply-To: <1163678809.5169.47.camel@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 1607 bytes --]

I know that is very easy to implement with L2CAP and RFCOMM, but my assignment is to be implement using HCI layer, and have to use these command ...
   
  Now, I have fix this problem ...
   
  Thanks for ur reply ...
   
  take care
  Regards,

Marcel Holtmann <marcel@holtmann.org> wrote:
  Hi,

> We are using Linux for tranfering a file on bluetooth devices. Connection create
> function on HCI layer i.e. (hci_create_connection(----)) can't procced and give
> error message.
> 
> Connection failed !
> : operation not permitted
> 
> kindly suggest is there any problem with linux kernal or else.

simply don't use this command. There is no need to deal with low-level
HCI command at all. The L2CAP and RFCOMM sockets full abstract from this
and for everything else we have a nice D-Bus based interface.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel



Imran Siddique 
MS Computing Science 
Umeå University, 
Sweden. 
--------------------------------
Cell: +46-762743152
 
---------------------------------
Sponsored Link

Mortgage rates near 39yr lows. $510,000 Mortgage for $1,698/mo -   Calculate new house payment

[-- Attachment #1.2: Type: text/html, Size: 2141 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-11-16 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 11:51 [Bluez-devel] Bluetooth devices connection problem Imran Siddique
2006-11-16 12:06 ` Marcel Holtmann
2006-11-16 16:13   ` Imran Siddique [this message]
2006-11-16 16:15     ` 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=20061116161319.54202.qmail@web37710.mail.mud.yahoo.com \
    --to=imran_stdu@yahoo.com \
    --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