All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: HDLC frame timing
Date: Tue, 25 Aug 2015 12:04:36 +0000	[thread overview]
Message-ID: <55DC59D4.7050209@workingcode.com> (raw)
In-Reply-To: <CAHZee8gDhYwwub+cjFF=8RsDZiG=rFwVo7MrwWofvoJSyZrbdA@mail.gmail.com>

On 08/25/15 05:09, Vertical Limit wrote:
> Hi all,
> 
> I am currently working on a system using pppd over a special radio
> link. Would it be possible to insert a small time break (around 2ms)
> between two consecutive HDLC frames? I could imagine compiling a
> special customized pppd version for this purpose. I think there is no
> pppd option for achieving this. Could someone help me by pointing me
> to the right lines of codes or giving a better solution?

This isn't really under PPP's control.

First of all, the data path itself (the IP frames containing user data)
does not run through the user-space pppd daemon.  So, even if you did
modify it, you would be changing only the way pppd does its negotiation
and nothing about the normal operation once the link is established.

Secondly, there's no place in the kernel PPP driver I can see where you
could delay something.  I suppose, in theory, you could completely
rewrite it to include some sort of delay queue on the transmit side
along with a timer-driven mechanism, but I think that's barking up the
wrong tree.  Timing isn't this driver's job.

Instead, I think what you want to do is to create a custom HDLC
(synchronous serial port) driver that has the properties that you
desire, and then run unmodified PPP over that.

Good luck on your Aloha project.  ;-}

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

  reply	other threads:[~2015-08-25 12:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  9:09 HDLC frame timing Vertical Limit
2015-08-25 12:04 ` James Carlson [this message]
2015-09-09 14:34 ` Vertical Limit

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=55DC59D4.7050209@workingcode.com \
    --to=carlsonj@workingcode.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.