Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problem setting the flush timeout
Date: Tue, 22 Nov 2005 12:09:05 +0100	[thread overview]
Message-ID: <1132657745.28644.7.camel@blade> (raw)
In-Reply-To: <43815F5F.8030402@masaka.cs.ohiou.edu>

Hi Jim,

> 	I have been pulling my hair for quite some time at the 
> set-flush-timeout.c code segment I was referred to use to set the flush 
> timeout for a bluetooth device.  The call to hci_get_route( bdaddr_t* ) 
> is failing, even though I directly cut-and-pasted the code.  I verified 
> that the address I'm passing does exist on the system.  It's setting 
> errno to 19 and claiming that the device doesn't exist even though I'm 
> 100% positive that it does (hcitool dev shows it's 00:11:95:4F:FD:22, 
> and cr -> bdaddr_t.b[5] through cr -> bdaddr_t.b[0] are the same values, 
> copied in using str2ba).  The device does definitely exist on the 
> system.  Any other idea why this might be happening?

if you wanna use hci_get_route() then use the code inside hcitool.c for
any reference, because its usage is known to work.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-11-22 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21  5:47 [Bluez-devel] Problem setting the flush timeout Jim Wyllie
2005-11-22 11:09 ` Marcel Holtmann [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=1132657745.28644.7.camel@blade \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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