netdev - RE: [PATCH net-next-2.6 00/13] net-caif: introducing CAIF protocol stack

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1264155561.3469.42.camel@violet>
Date:	Fri, 22 Jan 2010 11:19:21 +0100
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Sjur Brændeland 
	<sjur.brandeland@...ricsson.com>
Cc:	netdev@...r.kernel.org, davem@...emloft.net,
	stefano.babic@...ic.homelinux.org, randy.dunlap@...cle.com
Subject: RE: [PATCH net-next-2.6 00/13] net-caif: introducing CAIF protocol
 stack

Hi Sjur,

> >> This patch-set introduces the CAIF protocol Stack.
> >> 
> >> The "Communication CPU to Application CPU Interface" (CAIF) is a
> >> packet based connection-oriented MUX protocol developed by
> >> ST-Ericsson for use with its modems. 
> >> 
> >> * CAIF provides a socket interface which can be used to open virtual
> >>   AT channels, create and configure GPRS Data connections.
> >> 
> >> * A CAIF Network device is also provided for GPRS access.
> >>   This interface can be managed with socket IOCTLs or RTNL.
> >> 
> >> * A kernel interface is provided allowing Kernel modules to use CAIF.
> >> 
> >> * A serial link layer layer implemented as a line discipline is
> >>   currently implemented. Other link interfaces may be contributed at
> >> a later stage. 
> > 
> > any details on potential USB, SPI or SDIO drivers?
> 
> We have a SPI driver that we could contribute, 
> but I think it might need some more work before submitting it.
> Also I think it would be good to have this patch set accepted before we
> start on SPI.

personally I would like to see the SPI driver. So that we get a feeling
on how the low-level hardware abstraction has been done. And what are
the difference between the busses.

Also it doesn't have to be part of this patch set. Just send it as RFC
for review/reference. Submit early is always a good idea.

Regards

Marcel


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