From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] error while making call to ioctl for releasing a device
Date: Sat, 03 Mar 2007 12:33:57 +0100 [thread overview]
Message-ID: <1172921637.24446.15.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <57c68ddc0702280423h737f8190n1fa76f35ea4413@mail.gmail.com>
Hi Siddhant,
> I am trying to obex push a file through rfcomm channel. Everything
> goes fine (including sending of file) until i try to release the
> device via call to ioctl
>
> exact call is
>
> ioctl(sock,RFCOMMRELEASEDEV,&req)
>
> with error " Bad File Descriptor".
>
> Can anyone give me a hint abt why can this happen..
> Waiting for some reply
without looking at the code, I can't tell you anything. However you
should use the RFCOMM socket directly and not the virtual TTY. It is not
needed to put another kernel layer in between.
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-03-03 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 12:23 [Bluez-users] error while making call to ioctl for releasing a device siddhant tewari
2007-03-03 11:33 ` 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=1172921637.24446.15.camel@aeonflux.holtmann.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox