Hi Sjur,

quoted text
> >> +	 * The sock->type specifies the socket type to use. The CAIF
> >> socket is +	 * a packet stream in the sence that it is packet based.
> >> +	 * CAIF trusts the reliability of the link, no resending is
> >> implemented. +	 */ +	if (sock->type != SOCK_SEQPACKET)
> >> +		return -ESOCKTNOSUPPORT;
> > 
> > we came to an interesting detail here when testing with a STE modem.
> > Why is this SEQPACKET and not a STREAM.
> 
> The reason is that CAIF provides different services not just AT,
> and some of them are really packet oriented such as Utility links and
> Video. It would not be right to provide a stream based solution in this case.
> 
> > Especially with the AT
> > command channels it is kinda weird that you have an MTU. The AT
> > specification doesn't really have any defined behavior when using a
> > sequential packet transport. It is more a stream based socket.
> 
> Yes I see your point. In order to limit the effort and simplify
> caif_socket we ended up implementing only SEQPACKET. 

I think we need to split this. Use SEQPACKET for packet based services
and have STREAM for AT command channel.

So while this might cause internally some more code. It would take away
the complexity from userspace to turn it into a stream. And that is what
the userspace is expecting.

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html