netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Babic <stefano.babic@babic.homelinux.org>
To: sjur.brandeland@stericsson.com
Cc: netdev@vger.kernel.org, randy.dunlap@oracle.com,
	kim.xx.lilliestierna@stericsson.com,
	christian.bejram@stericsson.com,
	daniel.martensson@stericsson.com
Subject: Re: [RFC PATCH v3 0/8] CAIF Protocol Stack
Date: Wed, 02 Dec 2009 18:02:40 +0100	[thread overview]
Message-ID: <4B169DB0.6010307@babic.homelinux.org> (raw)
In-Reply-To: <1259593252-2493-1-git-send-email-sjur.brandeland@stericsson.com>

sjur.brandeland@stericsson.com wrote:
> General:
> * Sockets has replaced the character device implementation,
>   when accessing the modem. AT channels has to open sockets.

Hi Sjur,

I would like to test your patches with real hardware (based on an ARM
processor), as I did last time before sending my comments.
I think it should easier if in the Documentation there is an example to
explain how to setup a connection, for example with AT protocol. I tried
and I get "Specified PHY type does not exists", probably because I have
not well understood the parameters.

There are some errors in the MAN page documentation (patch #7) and the
example reported does not compile (for example, CAIFSO_CHANNEL should be
CAIF_CHANNEL_OPT, and so on).

Can you provide an example for the user space to setup a connection ?

> Please check what you think of the asserts in this release and get back to be!

Yes, I will do it.

Best Regards,
Stefano

-- 
stefano <stefano.babic@babic.homelinux.org>
GPG Key: 0x55814DDE
Fingerprint 4E85 2A66 4CBA 497A 2A7B D3BF 5973 F216 5581 4DDE

  parent reply	other threads:[~2009-12-02 17:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 15:00 [RFC PATCH v3 0/8] CAIF Protocol Stack sjur.brandeland
2009-11-30 15:00 ` [RFC PATCH v3 1/8] " sjur.brandeland
2009-11-30 15:00   ` [RFC PATCH v3 2/8] " sjur.brandeland
2009-11-30 15:00     ` [RFC PATCH v3 3/8] " sjur.brandeland
2009-11-30 15:00       ` [RFC PATCH v3 4/8] " sjur.brandeland
2009-11-30 15:00         ` [RFC PATCH v3 5/8] " sjur.brandeland
2009-11-30 15:00           ` [RFC PATCH v3 6/8] " sjur.brandeland
2009-11-30 15:00             ` [RFC PATCH v3 7/8] " sjur.brandeland
2009-11-30 15:00               ` [RFC PATCH v3 8/8] " sjur.brandeland
2009-12-15 17:12               ` [RFC PATCH v3 7/8] " stefano babic
2009-11-30 16:41           ` [RFC PATCH v3 5/8] " Randy Dunlap
2009-12-10 13:05             ` Sjur Brændeland
2009-12-10 16:44               ` Randy Dunlap
2009-12-15 16:47         ` [RFC PATCH v3 4/8] " stefano babic
2009-12-16 16:16           ` Sjur Brændeland
2009-12-15 16:00       ` [RFC PATCH v3 3/8] " stefano babic
2009-12-16 16:15         ` Sjur Brændeland
2009-12-09  0:18     ` [RFC PATCH v3 2/8] " stefano babic
2009-12-10 11:20       ` Sjur Brændeland
2009-12-08 23:42   ` [RFC PATCH v3 1/8] " stefano babic
2009-12-10 11:11     ` Sjur Brændeland
2009-11-30 16:08 ` [RFC PATCH v3 0/8] " Patrick McHardy
2009-11-30 18:26   ` Sjur Brændeland
2009-12-02 17:02 ` Stefano Babic [this message]
2009-12-03 17:49   ` Sjur Brændeland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B169DB0.6010307@babic.homelinux.org \
    --to=stefano.babic@babic.homelinux.org \
    --cc=christian.bejram@stericsson.com \
    --cc=daniel.martensson@stericsson.com \
    --cc=kim.xx.lilliestierna@stericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sjur.brandeland@stericsson.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).