public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Deresch <aderesch@fs.tum.de>
To: "Gary Martin" <gary_martin_au@yahoo.com.au>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Desperate newbie
Date: Wed, 31 Mar 2004 17:06:11 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.56L0.0403311642280.9869@localhost> (raw)
In-Reply-To: <20040331134502.35044.qmail@web21006.mail.yahoo.com>

On Wed, 31 Mar 2004, [iso-8859-1] Gary Martin wrote:

> Thank you for your support Andreas. Problems like this make me
> want to go back to Mac OS X, but there is something about Linux
> that draws me back. It has been a struggle --- I think a lot of
> the problems I have encountered with Linux have been the result of
> trying to run it on a PowerPC chip!!
As Marcel explained, this certainly does result in additional difficulties,
yes.

> Service Name: IrMC Synchronization
> Service RecHandle: 0x10006
> Service Class ID List:
>   "IrMCSync" (0x1104)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 11
>   "OBEX" (0x0008)
> Profile Descriptor List:
>   "IrMCSync" (0x1104)
>     Version: 0x0100
>
> [...]
>
> Yes --- there is an option in Multisync (IRMC-Bluetooth) to
> "search for units", and if found, "test connection" It just hangs
> during the search

Fine, so the only difference (apart from multisync itself) between our
phones is that "hcitool info <BDA>" does not work for you. The problem there
seems to arise at HCIGETCONNINFO and then hci_create_connection. Anybody
with BE hardware care to take a closer look at it? I unfortunately do not
own any (bluetooth capable).

ad


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2004-03-31 15:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200403301532.02494.thomas.chiverton@bluefinger.com>
2004-03-31 10:01 ` [Bluez-users] Desperate newbie Gary Martin
2004-03-31 11:37   ` Andreas Deresch
2004-03-31 13:45     ` Gary Martin
2004-03-31 14:19       ` Marcel Holtmann
2004-03-31 15:06       ` Andreas Deresch [this message]
2004-03-31 15:26         ` Marcel Holtmann
2004-04-01  9:09           ` Gary Martin
2004-03-31 14:12   ` Thomas Chiverton
2004-03-31 14:41     ` Gary Martin
2004-03-31 14:53       ` Thomas Chiverton
     [not found] <200403301050.08300.thomas.chiverton@bluefinger.com>
2004-03-30 10:56 ` Gary Martin
2004-03-27 13:47 Pering, Trevor
2004-03-28  0:46 ` Gary Martin
2004-03-28  0:58   ` Michal Semler (volny.cz)
2004-03-28  2:07     ` Gary Martin
2004-03-29  8:40       ` Andreas Deresch
2004-03-30  9:24         ` Gary Martin
  -- strict thread matches above, loose matches on Subject: below --
2004-03-27 11:25 Gary Martin

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=Pine.LNX.4.56L0.0403311642280.9869@localhost \
    --to=aderesch@fs.tum.de \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=gary_martin_au@yahoo.com.au \
    /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