This patch series adds support for herolte (Samsung Galaxy S7) devices
to libsamsung-ipc.

CURRENT STATUS:

 - the modem boots successfully

 - it WILL NOT interact with userland unless something opens
   /dev/umts_rfs0 at the same time as /dev/umts_ipc0 is open (see uses
   of "rild_ready()" in the kernel source code)

 - one way to get by for now is to repeatedly `cat /dev/umts_rfs0
   >/dev/null` in another terminal

 - once it starts talking, things look great until, running
   `ipc-modem --debug start`, we soon get into the following tightish
   loop:

...
[D] xmm626_kernel_smdk4412_fmt_recv: Message: aseq=0x00, 
command=IPC_SMS_DEVICE_READY, type=IPC_TYPE_NOTI, size=1
[5] Modem is fully ready
[D] xmm626_kernel_smdk4412_fmt_send: Message: mseq=0xb6, 
command=IPC_SMS_DEVICE_READY, type=IPC_TYPE_SET, size=0
[D] xmm626_kernel_smdk4412_fmt_recv: Message: aseq=0x00, 
command=IPC_SMS_MEM_STATUS, type=IPC_TYPE_NOTI, size=2
[D] xmm626_kernel_smdk4412_fmt_recv: Message: aseq=0xb6, 
command=IPC_GEN_PHONE_RES, type=IPC_TYPE_RESP, size=5
...

 - it looks to me like each SET is triggering another NOTI. I haven't
   investigated too far; it could be a bug in libsamsung-ipc, a bug in
   ipc-modem, or a bug in my understanding of the situation!

OPEN QUESTIONS:

 1. What should be done about the phone's need for /dev/umts_rfs0 to
    be open at the same time as /dev/umts_ipc0 is open?

 2. What's going on with that IPC_SMS_DEVICE_READY loop?

Regards,
  Tony


Tony Garnock-Jones (2):
  Remove reference to absent file that prevents doxygen from running
  Initial commit of herolte support

 samsung-ipc/Makefile.am               |   3 +-
 samsung-ipc/devices/herolte/herolte.c | 488 ++++++++++++++++++++++++++
 samsung-ipc/devices/herolte/herolte.h |  37 ++
 samsung-ipc/devices/ipc_devices.c     |  10 +
 samsung-ipc/devices/ipc_devices.h     |   1 +
 5 files changed, 538 insertions(+), 1 deletion(-)
 create mode 100644 samsung-ipc/devices/herolte/herolte.c
 create mode 100644 samsung-ipc/devices/herolte/herolte.h

-- 
2.28.0

_______________________________________________
Replicant mailing list
[email protected]
https://lists.osuosl.org/mailman/listinfo/replicant

Reply via email to