Linux bluetooth development
 help / color / mirror / Atom feed
From: Ben Lau <benlau@linux.org.hk>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Basic Imaging  Profile support
Date: Thu, 31 Jul 2003 09:51:40 +0800	[thread overview]
Message-ID: <3F28762C.2010409@linux.org.hk> (raw)
In-Reply-To: <1059603308.1831.17.camel@pegasus>

Hi Marcel,

    Thanks you for answering me.

    I just want to be able to transfer image between the iPAQ (or any
linux device) , as I see it is getting move devices which is support BIP.

    How is the support of OBEX now?

    I have not read though the BIP specification yet, i read from the
Implementation Guide , it said :

"In principle, it's relatively simple for a device that already supports
one of the Generic
Object Exchange-basedprofiles to support the Basic ImagingProfile as
well. Indeed,
the Basic Imaging profile utilises the same protocol stack as the other
Generic
Object Exchange-based profiles, thus limiting the extra development
workrequired."

    BTW, I  found a website

http://oss.bdit.de/opd.html

    Do somebody here tried with it?

Marcel Holtmann wrote:
> Hi Ben,
> 
> 
>>    I need to do a project in a iPaq with bluetooth support. It required
>>the BIP(basic imaging profile) support.
>>Did bluez support this profile yet? Or any body are working on it? If it
>>is not  , do it difficult to write the profile
>>support for Bluez? I am interested to do so. Any documents in web can be
>>used for reference?
> 
> 
> the Basic Imaging Profile is very complex. What do you need? It exists
> an initial BIP push daemon and we have obex code in CVS.
> 
> Regards
> 
> Marcel
> 
> 

      reply	other threads:[~2003-07-31  1:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30  3:21 [Bluez-devel] Basic Imaging Profile support Ben Lau
2003-07-30 22:15 ` Marcel Holtmann
2003-07-31  1:51   ` Ben Lau [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=3F28762C.2010409@linux.org.hk \
    --to=benlau@linux.org.hk \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@rvs.uni-bielefeld.de \
    /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