From: Jonathan Larmour <jifl@eCosCentric.com>
To: John Paul King <jpking@advantexmail.net>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: PPP Stack
Date: Mon, 07 Jun 2004 16:37:00 -0000 [thread overview]
Message-ID: <40C499CE.1070707@eCosCentric.com> (raw)
In-Reply-To: <NGBBKHJJOLGADEKDNFJFOEPACAAA.jpking@advantexmail.net>
John Paul King wrote:
> (BTW, sorry if I've sent this repeatedly--having problems w/ Ximian
> Evolution)
>
> I'm not sure if anyone else had this problem, but I thought that I would
> pass along the information. I was using the eCos PPP stack in conjunction
> with an EB40A, and I was able to establish a link w/ a Linux peer flawlessly
> (btw, thanks for the cool stack--I was able to create a program in Linux and
> have it immediately work in eCos!); however, when trying to connect to
> another device (in particular, a Kyocera 1xRTT module), a link never
> occurred (i.e., the Kyocera module never even tried to respond to PPP
> packets sent). Further inspection showed that the eCos stack did not send
> out an initial "flag sequence", and I assume the module timed out before the
> next frame was sent (i.e., wasn't able the use the previous ending "flag
> sequence" as the beginning "flag sequence" of the new frame). I modified
> the code in "pppasyncstart" such that the "flag sequence (0x7e)" is sent
> before every frame, and this seemed to worked great for my application;
> however, I'm not sure this would be best for all users since a "NULL frame"
> would possibly have to be digested by all possible peers. Anyhow, let me
> know if this is the right way to go. Thanks for the great operating system.
I don't know PPP/LCP off the top of my head, but I suggest you have a look
at the relevant RFCs as that's the only way to know what's correct and
allowed. If you find something relevant in there, feel free to post
something in our bugzilla database (see the website).
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
prev parent reply other threads:[~2004-06-07 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 3:37 John Paul King
2004-06-07 16:37 ` Jonathan Larmour [this message]
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=40C499CE.1070707@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=jpking@advantexmail.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).