Hi Ian,
Le 06/10/2017 à 16:47, Ian W MORRISON a écrit :
<snip>
It seems normal to me that BCM2EA4 is no more enumerated at ACPI level as
this is moved to serdev.
When removing 'if (ares->data.common_serial_bus.type !=
ACPI_RESOURCE_SERIAL_TYPE_UART)' you stop the serdev module finding the
Serial UART information. In this case it will not register the device and it
will fall back to previous behavior needing to use btattach to setup
Bluetooth.
Can you share:
- btattach you are currently using,
- dmesg with with dynamic debug enabled for serdev and hci_uart modules
during boot (with Hans's patches, your MINIX Z83-4 patches and mine
patches).
Regards,
Fred
Hi Fred,
I've attached four (text) files:
1. btattach.txt - Details of the 'bluez' package that contains the
'btattach' I'm using.
2. dmesg.txt - 'dmesg' with with dynamic debug enabled for serdev and
hci_uart modules. This doesn't seem to show much so have I provided
what you wanted?
3. gitlog.txt - First few commits from the git log showing the kernel
patches used to build the kernel (sent just for clarity).
4. working.txt - An extract from 'dmesg' when BCM2EA4 is enumerated
from a kernel patched with the 'if' statement refered to above.
Regards,
Ian
Which tty is used for btattach?
Is this tty existing in /dev?
I took a look at dmesg.txt and I did not find any trace related to serdev.
On the T100, where ttyS4 is used for Bluetooth, I can see the following
traces:
[ 11.732347] serial serial0: allocated controller
0xffff880036229000 id 0
[ 11.732470] serial serial0-0: device serial0-0 registered
[ 11.732475] serial serial0: serdev0 registered: dev:ffff880036229000
[ 11.732478] serial serial0: tty port ttyS4 registered
If serdev registration failed you should at least get something like:
serdev0 no devices registered: of:<> acpi:<>
So, just to be sure, is SERIAL_DEV_BUS and SERIAL_DEV_CTRL_TTYPORT
enabled in your kernel?
Regards,
Fred
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
