All of lore.kernel.org
 help / color / mirror / Atom feed
From: Barry Byford <31baz66@gmail.com>
To: Bluez mailing list <linux-bluetooth@vger.kernel.org>
Subject: Re: Serial Port connection with DBus API
Date: Fri, 21 Apr 2017 21:54:10 +0100	[thread overview]
Message-ID: <CAAu3APahskA_b2Ydt8TzUWBQnkuC10UwjZ37RaOyhAt4s1iyiQ@mail.gmail.com> (raw)
In-Reply-To: <20170408071834.GA12144@x1c>

On 8 April 2017 at 08:18, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> Hi Barry,
>
> On Fri, Apr 07, 2017, Barry Byford wrote:
>> = bluetoothd: Invalid value for profile option Channel
>
> Let's look at your code:
>
>> >             'Channel': GLib.Variant('i', 1),
>
> Yep, that's wrong. The expected D-Bus type for 'Channel' is UINT16,
> which is 'q' and not 'i'.
>
>> = bluetoothd: RFCOMM server failed for SerialPort: socket(STREAM,
>> RFCOMM): Protocol not supported (93)
>
> That usually means that your kernel is incorrectly configured and
> lacking RFCOMM support.

You were spot on with this!!!  I now have the kernel patched and I'm
past this error.

However I'm now seeing this error appear in btmon when I try to bind
to the RFCOMM socket:

= bluetoothd: RFCOMM server failed for SerialPort: rfcomm_bind:
Address already in use (98)

Has anyone seen this kind of error before?

Thanks in advance,
Barry

>
> Johan

  parent reply	other threads:[~2017-04-21 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 13:47 Serial Port connection with DBus API Barry Byford
2017-04-07 21:56 ` Barry Byford
2017-04-08  7:18   ` Johan Hedberg
2017-04-08  7:57     ` Barry Byford
2017-04-21 20:54     ` Barry Byford [this message]
2017-04-22  5:26       ` Johan Hedberg
2017-04-22 20:46         ` Barry Byford
2017-04-25 21:48           ` Barry Byford
2017-04-26 19:07             ` Johan Hedberg
2017-04-26 22:47               ` Barry Byford

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=CAAu3APahskA_b2Ydt8TzUWBQnkuC10UwjZ37RaOyhAt4s1iyiQ@mail.gmail.com \
    --to=31baz66@gmail.com \
    --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.