All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Mort <gary@mort.net>
To: linux-bluetooth@vger.kernel.org
Subject: 3dsp sample app and Bluez v5
Date: Mon, 1 Jun 2015 17:05:44 -0400	[thread overview]
Message-ID: <556CC928.60503@mort.net> (raw)

I am trying to convert a pair of 3D bluetooth glasses into 'Joo Janta 
200 Super-Chromatic Peril Sensitive Sunglasses'  and so it seemed a 
small modification to 3dsp to play with different frequencies would fit 
the bill.

Following the command line help, I kept getting the message
  ' Failed to open HCI user channel' and since it was an extremely tiny 
c file, I tracked that down to a failure at line 642    hci_dev = 
bt_hci_new_user_channel(index);

I noticed that there was a different method of opening a socket right 
above it,    hci_dev = bt_hci_new_raw_device(index); and it was 
controlled via a command line arguement.

So adding -r to my command line, my server now seems to execute. 
However, when I try to run 3dsp in client mode from a second terminal 
window it does not connect[as well as my actual glasses not connecting]

I figured before spending too much time on this, I'd check to see if the 
code is supposed to work at this point - in which case it is my 
system..or if the bluez api has changed sufficiently that I need to 
modify the code to use some new api?
Konsole outFailed to open HCI user channel

             reply	other threads:[~2015-06-01 21:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 21:05 Gary Mort [this message]
2015-06-01 21:23 ` 3dsp sample app and Bluez v5 Marcel Holtmann
2015-06-02  0:09   ` Gary Mort
2015-06-02  1:13     ` Marcel Holtmann
2015-06-02  4:26       ` Gary Mort
2015-06-02  5:00         ` Marcel Holtmann
2016-08-08 15:50           ` Bastien Nocera
2016-08-17  3:03             ` Gary Mort
2016-08-17  3:33               ` Gary Mort

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=556CC928.60503@mort.net \
    --to=gary@mort.net \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.