Skip to contentSkip to conversation

oFono gets multiplexer support

DISCUSSION Denis Kenzior 2 participants 3 messages Oct 15, 2009

lore
Share & tools
lore
#0 lore raw

Hi All,

Just to let you know the initial support for multiplexing has been added to oFono. The multiplexer infrastructure is fully customizable through the use of drivers. Two drivers are currently supported, GSM 27.010 Basic and Advanced modes.

The multiplexer is implemented in gatmux in the gatchat library. GAtMux provides a simple interface, and returns a fully functional GIOChannel for each multiplexer port. Thus it can easily be integrated with the existing GAtChat functionality, or used to read / write raw information (e.g. ppp frames)

This will allow oFono to implement everything in the main oFono process, and not resort to a separate multiplexer daemon. The calypso modem plugin has been updated to take advantage of 4 multiplexer channels.

Regards,
-Denis

#1 lore raw
Quoted 6 lines

Hi All,

Just to let you know the initial support for multiplexing has been added to oFono. The multiplexer infrastructure is fully customizable through the use of drivers. Two drivers are currently supported, GSM 27.010 Basic and Advanced modes.

Is it a correct understanding that modem's that provide kernel drivers that provide multiple TTY's and do the multiplexing in kernel space will not need to integrate with any of this and can just create multiple GAtChat objects in their oFono modem driver?

I notice that g_at_mux_create_channel() doesn't take a DLC as argument. So when the calypso driver defines

	#define VOICE_DLC 0

the result will be that DLC 1 will be used for VOICE_DLC, correct?

Cheers,
Waldo

#2 lore raw

Hi Waldo,

Quoted 4 lines

Is it a correct understanding that modem's that provide kernel drivers that provide multiple TTY's and do the multiplexing in kernel space will not need to integrate with any of this and can just create multiple GAtChat objects in their oFono modem driver?

If the modem driver can take advantage of a kernel space multiplexer, that is fine.

Quoted 4 lines

I notice that g_at_mux_create_channel() doesn't take a DLC as argument. So when the calypso driver defines #define VOICE_DLC 0
the result will be that DLC 1 will be used for VOICE_DLC, correct?

The real assignment of DLC channels is done inside GAtMux. What you see in the driver is unrelated, but most likely will work like you outline by magic :)

Regards,
-Denis