Linux bluetooth development
 help / color / mirror / Atom feed
From: "Marcel J.E. Mol" <marcel@mesa.nl>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Harald Schmitt <linux@hschmitt.de>, linux-bluetooth@vger.kernel.org
Subject: Re: obexd 0.29 and N900 PC Suite
Date: Fri, 30 Jul 2010 22:49:43 +0200	[thread overview]
Message-ID: <20100730204943.GA15065@joshua.mesa.nl> (raw)
In-Reply-To: <AANLkTimKLcbg2d5Ev5AVBhQqRRrgV-aKKkTRfRzOFAK=@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset*=utf-8''%E2%80%9Cus-ascii, Size: 1827 bytes --]

On Fri, Jul 30, 2010 at 06:08:23PM +0300, Luiz Augusto von Dentz wrote:
> Hi,
> 
> On Fri, Jul 30, 2010 at 1:29 PM, Harald Schmitt <linux@hschmitt.de> wrote:
> > I have testes following command and it seems to work:
> > dbus-send --system --type=signal / com.meego.usb_moded.sig_usb_state_ind
> > string:'ovi_suite'
> > If one would just add this line to pcsuite-enable.sh under the SIGUSR1 then
> > both types of obexd would work?
> > Luiz could you confirm this? Do we also need a dbus-command for disconnect
> > with string:'USB disconnected' in pcsuite-disable.sh?
> 
> Hmm it may work with that but I would first just revert the patch I
> suggest other day since without that part there could be some other
> components still sending SIGUSR1 to obexd which might kill it, maybe I
> can just reintroduce SIGUSR1 and then have a config option saying
> which method to use for usb cable detection. What do you guys think?

Well, I just tested the dbus method on the n900 with an obexd 0.29 
(including the updates I already posted here plus a few other updates
including a basic IRMC server implementation) and pcsuite seems to 
work fine. But I did not test extensively (contact/calendar download
work file and file browsing too).

I don't know if there are other tools using signalling to obexd, maybe
people from the nokia n900/maemo group can tell...

-Marcel
-- 
     ======--------         Marcel J.E. Mol                MESA Consulting B.V.
    =======---------        ph. +31-(0)6-54724868          P.O. Box 112
    =======---------        marcel@mesa.nl                 2630 AC  Nootdorp
__==== www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____
 They couldn't think of a number,           Linux user 1148  --  counter.li.org
    so they gave me a name!  -- Rupert Hine  --  www.ruperthine.com

  reply	other threads:[~2010-07-30 20:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C4EC2B5.2030204@xxxxxxxxxxx>
     [not found] ` <AANLkTi=WSgMe86k-h=_HdzsPTZ=rK5ab5O9mYf8C6jnc@xxxxxxxxxxxxxx>
2010-07-29 18:16   ` obexd 0.29 and N900 PC Suite Marcel J.E. Mol
2010-07-30 10:29     ` Harald Schmitt
2010-07-30 15:08       ` Luiz Augusto von Dentz
2010-07-30 20:49         ` Marcel J.E. Mol [this message]
2010-07-27 11:27 Harald Schmitt
2010-07-27 13:03 ` Luiz Augusto von Dentz
2010-07-29 15:36   ` Harald Schmitt

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=20100730204943.GA15065@joshua.mesa.nl \
    --to=marcel@mesa.nl \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux@hschmitt.de \
    --cc=luiz.dentz@gmail.com \
    /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