netdev - RE: [RFC] 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] [day] [month] [year] [list]

Message-ID: <61D8D34BB13CFE408D154529C120E07902DF9765@eseldmw101.eemea.ericsson.se>
Date:	Fri, 18 Sep 2009 15:38:50 +0200
From:	Sjur Brændeland <sjur.brandeland@...ricsson.com>
To:	Rémi Denis-Courmont <remi@...lab.net>,
	<netdev@...r.kernel.org>
Subject: RE: [RFC] CAIF Protocol Stack

> -----Original Message-----
> From: Rémi Denis-Courmont
> Sent: 18. september 2009 14:32
>     Hello,
> 
> On Wed, 16 Sep 2009 14:30:34 +0200, Sjur Brændeland 
> <sjur.brandeland@...ricsson.com> wrote:
> > The Implementation of CAIF is divided into:
> > * CAIF Devices: Character Device, Net Device and Kernel API.
> > * CAIF Protocol Implementation
> > * CAIF Link Layer
> 
> I'm a bit confused here. What do you call a CAIF Device?
> 
> Do you mean a GPRS context is a network device, and an AT 
> command interface is a character device? Or is the CAIF modem 
> a device? or what?

What I meant was:
* "Net Device" - a "struct net_device" with one instance for each GPRS PDP context.
* "Character Device" - a chr device, with one instance for each AT channel towards the modem.

BR/Sjur Brændeland
--
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