public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gary Martin" <gary_martin_au@yahoo.com.au>
To: bluez-users@lists.sourceforge.net
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Thomas Chiverton <thomas.chiverton@bluefinger.com>,
	Andreas Deresch <aderesch@fs.tum.de>
Subject: Re: [Bluez-users] Desperate newbie
Date: Thu, 1 Apr 2004 19:09:17 +1000 (EST)	[thread overview]
Message-ID: <20040401090917.60642.qmail@web21005.mail.yahoo.com> (raw)
In-Reply-To: <1080746814.2536.16.camel@pegasus>

Thank you to Andreas, Marcel and Tom for your assistance. I
assumed that the problems I am having connecting to my phone were
the result of me misconfiguring something eg. hcid.conf. But
Marcel and Andreas seem to intimate that it may be a problem in
Bluez for PowerPC. I find it hard to believe that there aren't
other Linux PPC users successfully using Bluez to synchronise
their phones.
Bluetooth connectivity is an important function for today's
computer users --- I can't be the only one!

> > 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.
Sometimes I have "object push" on the phone, and I can send files
to Linux. Sometimes I can't. This change appears after I have
connected the phone under Mac OS X. Does the Bluetooth adapter
retain information from one operating system to the other? Even
when I delete the device "Mac OS X" on the phone and pair it with
"debian-0", the phone retains services that aren't available in
Linus, and refreshing the services on the phone makes them
disappear


> Marcel wrote
> On the other side I think that the userspace part still have 
some
missing byteswap operations, so try to isolate them and I will try

to
fix them as soon as possible.
Am I to isolate missing byteswap operations? I'm afraid I don't
know how to do this?

Regards,

Gary Martin

Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com

  reply	other threads:[~2004-04-01  9:09 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
2004-03-31 15:26         ` Marcel Holtmann
2004-04-01  9:09           ` Gary Martin [this message]
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=20040401090917.60642.qmail@web21005.mail.yahoo.com \
    --to=gary_martin_au@yahoo.com.au \
    --cc=aderesch@fs.tum.de \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=thomas.chiverton@bluefinger.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