On 26/04/2018 18:21, Linus Torvalds wrote:
On Thu, Apr 26, 2018 at 7:44 AM, Jef Driesen <[email protected]> wrote:
I also don't know the exact details on how these port numbers are assigned.
I guess it depends on the dive computer firmware and/or its bluetooth stack.
The valid range for rfcomm ports is 1-30 if I remember correctly.
The Petrel is certainly not the only one which is using a different port
number. I'm currently testing the divecomputer.eu and it seems to use port
6.
Ok, sounds like we should use port 0 too.
And that really makes most of the special cases just go away. So a
patch like the attached.
Dirk? Anybody with an rfcomm device? Willing to test the attached
"remove all the crazy crud" patch?
Linus
I tried this patch on V4.7.8-82
I get no download, errors.
Starting download from BT
Starting the thread 0
Failed to connect to device 00:13:43:5B:8F:BE . Device state
QBluetoothSocket::UnconnectedState . Error:
QBluetoothSocket::UnknownSocketError
[4.755321] ERROR: No such file or directory (2) [in
../../src/serial_posix.c:295 (dc_serial_open)]
Finishing the thread Unable to open %s %s (%s) dives downloaded 0
Hope this helps to solve the rfcomm issue.
Kind regards,
willem
--
This message and attachments are subject to a disclaimer.
Please refer to
http://upnet.up.ac.za/services/it/documentation/docs/004167.pdf
<http://upnet.up.ac.za/services/it/documentation/docs/004167.pdf> for
full
details.
_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
