[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091009094306.4671ef33.randy.dunlap@oracle.com>
Date: Fri, 9 Oct 2009 09:43:06 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: sjur.brandeland@...ricsson.com
Cc: netdev@...r.kernel.org, stefano.babic@...ic.homelinux.org,
randy.dunlap@...cle.com, kim.xx.lilliestierna@...ricsson.com,
christian.bejram@...ricsson.com, daniel.martensson@...ricsson.com
Subject: Re: [PATCH] [CAIF-RFC 5/8-v2] CAIF Protocol Stack
On Fri, 09 Oct 2009 15:39:28 +0200 sjur.brandeland@...ricsson.com wrote:
> From: Sjur Braendeland <sjur.brandeland@...ricsson.com>
>
> Change-Id: I205c5b3baf1542e1593637ce896d8684870415be
> Signed-off-by: Sjur Braendeland <sjur.brandeland@...ricsson.com>
> ---
> net/caif/Kconfig | 61 ++
> net/caif/Makefile | 56 ++
> net/caif/caif_chnlif.c | 219 +++++++
> net/caif/caif_chr.c | 374 ++++++++++++
> net/caif/caif_config_util.c | 167 ++++++
> net/caif/chnl_chr.c | 1393 +++++++++++++++++++++++++++++++++++++++++++
> net/caif/chnl_net.c | 492 +++++++++++++++
> 7 files changed, 2762 insertions(+), 0 deletions(-)
> create mode 100644 net/caif/Kconfig
> create mode 100644 net/caif/Makefile
> create mode 100644 net/caif/caif_chnlif.c
> create mode 100644 net/caif/caif_chr.c
> create mode 100644 net/caif/caif_config_util.c
> create mode 100644 net/caif/chnl_chr.c
> create mode 100644 net/caif/chnl_net.c
>
> diff --git a/net/caif/Kconfig b/net/caif/Kconfig
> new file mode 100644
> index 0000000..7fb9e9c
> --- /dev/null
> +++ b/net/caif/Kconfig
> @@ -0,0 +1,61 @@
> +#
> +# CAIF net configurations
> +#
> +
> +#menu "Caif Support"
> +comment "CAIF Support"
> +
> +menuconfig CAIF
> + tristate "Enable Caif support"
> + default n
> + ---help---
> + Say Y here if you need to use a phone modem that uses CAIF as transport
end above with period ('.').
> + You will also need to say yes to any caif physical devices that your platform
> + supports.
> + This can be either built-in or as a loadable module, if you select to build it as module
s/,/;/
> + the other CAIF also needs to built as modules
the other CAIF {options or drivers or some other word here} also need ... modules.
(end with period)
> + See Documentation/CAIF for a further explanation on how to use and configure.
> +
> +if CAIF
> +
> +config CAIF_CHARDEV
> + tristate "CAIF character device"
> + default CAIF
> + ---help---
> + Say Y if you will be using the CAIF AT type character devices.
> + This can be either built-in or as a loadable module,
> + If you select to build it as a built in then the main caif device must also be a builtin.
> + If unsure say Y.
> +
> +config CAIF_NETDEV
> + tristate "CAIF Network device"
> + default CAIF
> + ---help---
> + Say Y if you will be using the CAIF based network device.
> + This can be either built-in or as a loadable module,
> + If you select to build it as a built in then the main caif device must also be a builtin.
> + If unsure say Y.
> +
> +
> +config CAIF_USE_PLAIN
> + bool "Use plain buffers instead of SKB in caif"
> + default n
> + ---help---
> + Use plain buffer to transport data,
s/,/./
> + Select what type of internal buffering CAIF should use,
> + skb or plain.
> + If unsure say N hre.
> +
> +config CAIF_DEBUG
> + bool "Enable Debug"
> + default n
> + --- help ---
> + Enable the inclusion of debug code in the caif stack,
> + be aware that doing this will impact performance.
> + If unsure say N here.
> +
> +# Include physical drivers
> +# source "drivers/net/caif/Kconfig"
Drop the above line.
> +source "drivers/net/caif/Kconfig"
> +endif
> +#endmenu
---
~Randy
--
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
Powered by blists - more mailing lists