linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Проклов Александр Валерьевич" <ProklovAV@zabzd.ru>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Algorithm for create serial connection without rfcomm
Date: Fri, 27 Apr 2018 13:56:09 +0800	[thread overview]
Message-ID: <5AE2BB79.30003@zabzd.ru> (raw)
In-Reply-To: <CAAu3APYXpqO77M0AhAVD-EnOapXAOXsAD4e26x5ULTVCxfSreg@mail.gmail.com>

Thank you Barry Byford,

Your example is more understandable for me, but I do not know python.
If I understand correctly, the algorithm is as follows:
1. Connect to device (pair, connect)
2. "Release" profile
3. "RegisterProfile" with parameters. profile_path - path for new 
profile on Dbus?

After RegisterProfile device port /dev/rfcomm created automatic or need 
more operation?

4. For disconnect make RequestDisconnection



26.04.2018 21:39, Barry Byford пишет:
> Hello Aleksandr ,
>
> I believe that the following example in the tree is intended to serve
> the purpose.
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/test/test-profile
>
> I couldn't workout the correct command line switches to get this
> working so I did my own experiment and came up with the follow gist
> for Serial Port Profile:
> https://gist.github.com/ukBaz/217875c83c2535d22a16ba38fc8f2a91
>
> I hope that helps.
>
> Regards,
> Barry
>
>
> On 25 April 2018 at 08:53, Проклов Александр Валерьевич
> <ProklovAV@zabzd.ru> wrote:
>> Hi all,
>>
>> The rfcomm command is deprecated, what is the use of the algorithm to create
>> serial connections?
>>
>> Whether it is possible to create /dev/rfcomm not using rfcomm command
>> through Dbus or another utility from Bluez5?
>>
>> In many forums, people also ask this question, and everything is decided by
>> adding rfcomm command.
>>
>> --------------
>> Best regards,
>> Aleksandr Proklov
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  parent reply	other threads:[~2018-04-27  5:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000301d347db$df1dd300$9d597900$@com>
     [not found] ` <6B2D6FC09217DA4280D35175FA16A620688418CA@msceml521-mbx.china.huawei.com>
     [not found]   ` <457BA4F48509464E9000537839AF501857261694@msceml521-mbx.china.huawei.com>
     [not found]     ` <59E7EBF9.3050705@zabzd.ru>
     [not found]       ` <457BA4F48509464E9000537839AF501857261990@msceml521-mbx.china.huawei.com>
     [not found]         ` <7CC793D56C5DD04ABFAFBF59EB0D4A3650F1DDAB@msceml522-mbx.china.huawei.com>
     [not found]           ` <59E946F9.1060501@zabzd.ru>
     [not found]             ` <7CC793D56C5DD04ABFAFBF59EB0D4A3650F1E01D@msceml522-mbx.china.huawei.com>
     [not found]               ` <59ED2E3D.7030809@zabzd.ru>
     [not found]                 ` <7CC793D56C5DD04ABFAFBF59EB0D4A3650F1E6D0@msceml522-mbx.china.huawei.com>
     [not found]                   ` <59F92B55.0@zabzd.ru>
     [not found]                     ` <7CC793D56C5DD04ABFAFBF59EB0D4A3650F23FDB@msceml522-mbx.china.huawei.com>
     [not found]                       ` <480C9E29A742984996B50276401889F36B33E940@msceml521-mbx.china.huawei.com>
2018-04-25  7:53                         ` Algorithm for create serial connection without rfcomm Проклов Александр Валерьевич
     [not found]                           ` <CAAu3APYXpqO77M0AhAVD-EnOapXAOXsAD4e26x5ULTVCxfSreg@mail.gmail.com>
2018-04-27  5:56                             ` Проклов Александр Валерьевич [this message]
2018-04-28  3:28                             ` Проклов Александр Валерьевич
2019-08-01  5:35                         ` May be 'bluetoothctl devices' not right? Проклов Александр Валерьевич
2019-08-05  5:09                           ` Проклов Александр Валерьевич

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=5AE2BB79.30003@zabzd.ru \
    --to=proklovav@zabzd.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).