From: Christian <crich-ml@beronet.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Way how frames are read in pppd
Date: Mon, 30 Oct 2006 13:44:54 +0000 [thread overview]
Message-ID: <454601D6.5040109@beronet.com> (raw)
In-Reply-To: <4540C35F.9010104@beronet.com>
Hello James,
>It's still not at all clear to me what you're trying to do, or why
>you're doing it.
>
>You're using async devices here -- ptys -- so why are you expecting
>synchronous behavior?
>
>
>
OK, maybe i do not understand everything correctly, let me in short
explain what i have:
I have a device which gives me a function to transmit data in a hdlc
frame, so i can just call some function like:
tx_frame(char *p, int l);
and i can be sure the data will come out on the other side in exactly 1
hdlc frame with size l.
on the other hand i have installed a callback like
rx_frame(char *p, int l);
where i receive the data from exactly 1 hdlc frame with length l.
It means i'm handling data directly without any knowledge of hldc,
because the controller supports hdlc coding/decoding.
then i tried to use pppd with stdin/stdout, but this obviously did not
work, because there is no boundaries in stdin/stdout so it will fail
when data packets increase in size or in speed, also i needed to enable
the sync option which made it work for a few small slowly coming packets.
I assume sync=no hdlc, and when not using the sync option pppd will do
hdlc on stdin/stdout, maybe you can enlighten that to me a bit?
I have read that i can set a pty end into N_HDLC mode, so that each read
returns exactly 1 packet, do you think i can handle my task in that way ?
I hope very much you can help me,
Christian
next prev parent reply other threads:[~2006-10-30 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 14:17 Way how frames are read in pppd Christian
2006-10-30 12:48 ` James Carlson
2006-10-30 13:44 ` Christian [this message]
2006-10-30 13:56 ` James Carlson
2006-10-30 14:11 ` Christian
2006-10-30 14:49 ` James Carlson
2006-10-30 15:06 ` Christian
2006-10-30 15:13 ` James Carlson
2006-10-30 23:15 ` Paul Mackerras
2006-10-31 17:21 ` Christian
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=454601D6.5040109@beronet.com \
--to=crich-ml@beronet.com \
--cc=linux-ppp@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.