Linux bluetooth development
 help / color / mirror / Atom feed
From: "shy" <shyboysby@hotmail.com>
To: "'Gustavo F. Padovan'" <gustavo@las.ic.unicamp.br>
Cc: "'Kartikey Parmar'" <kartikey2781@gmail.com>,
	<linux-bluetooth@vger.kernel.org>
Subject: RE: OBEX profile support
Date: Mon, 16 Feb 2009 14:24:46 +0800	[thread overview]
Message-ID: <BAY114-DS16A8C9E600F64096D25D4B1B70@phx.gbl> (raw)
In-Reply-To: <6b53b1990902152203r4fa9e50ajcc5d050c2ee3b5b8@mail.gmail.com>

Hi,
You need openobex compiled firstly, and then you could use obexftp to do
file transfer. Openobex and obexftp support bluetooth channel.
Brs
Shi Buyun

-----Original Message-----
From: linux-bluetooth-owner@vger.kernel.org
[mailto:linux-bluetooth-owner@vger.kernel.org] On Behalf Of Gustavo F.
Padovan
Sent: 2009年2月16日 14:04
To: shy
Cc: Kartikey Parmar; linux-bluetooth@vger.kernel.org
Subject: Re: OBEX profile support

Hi,

2009/2/16 shy <shyboysby@hotmail.com>:
> Hi, Kartikey
> You can use obexftp to do your task. You can find obexftp in folder 
> /obexftp/apps.

I have the same doubt: how to transfer files. I find out obexftp, but does
it support BlueZ 4.x? Version 0.22 of obexftp not even compile with BlueZ 4.
x.
And what folder is that? Where can I find it?

> Brs
> Shi Buyun
>
> -----Original Message-----
> From: linux-bluetooth-owner@vger.kernel.org
> [mailto:linux-bluetooth-owner@vger.kernel.org] On Behalf Of Kartikey 
> Parmar
> Sent: 2009年2月14日 20:05
> To: linux-bluetooth@vger.kernel.org
> Subject: OBEX profile support
>
> hi
>
> I want to support file transfer between two bluetooth devices (say 
> mobile phone & desktop pc) in my application...
> Is there any utility bluez provides on which I can test first whether 
> it is working or not! like
>
> hcitool, sdptool etc...or I will have to work on some utility to 
> implement OBEX???
>
> pls reply if somebody has done this...
>
> --
> Kartikey Parmar
> President AAECC
> 09879095390 (M)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
> in the body of a message to majordomo@vger.kernel.org More majordomo 
> info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe 
> linux-bluetooth" in the body of a message to majordomo@vger.kernel.org 
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



--
Gustavo F. Padovan

Computer Engineering Student
Institute of Computing - IC
University of Campinas - UNICAMP

email: gustavo@las.ic.unicamp.br
gtalk: gfpadovan@gmail.com
mobile: +55 19 81030803
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
in the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2009-02-16  6:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14 12:05 OBEX profile support Kartikey Parmar
2009-02-16  4:57 ` shy
2009-02-16  6:03   ` Gustavo F. Padovan
2009-02-16  6:24     ` shy [this message]
2009-02-16 12:13       ` Kartikey Parmar
2009-02-16 12:46       ` Gustavo F. Padovan
2009-02-17  1:05         ` Yao Ye
2009-02-17  2:20           ` Gustavo F. Padovan

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=BAY114-DS16A8C9E600F64096D25D4B1B70@phx.gbl \
    --to=shyboysby@hotmail.com \
    --cc=gustavo@las.ic.unicamp.br \
    --cc=kartikey2781@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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