public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@cogenit.fr>
To: Krzysztof Halasa <khc@intrepid.pm.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: configuring net interfaces
Date: Thu, 29 Mar 2001 11:25:47 +0200	[thread overview]
Message-ID: <20010329112547.A23947@se1.cogenit.fr> (raw)
In-Reply-To: <m3itkuq6xt.fsf@intrepid.pm.waw.pl> <20010328182729.A16067@se1.cogenit.fr> <m34rwd8pj2.fsf@intrepid.pm.waw.pl>
In-Reply-To: <m34rwd8pj2.fsf@intrepid.pm.waw.pl>; from khc@intrepid.pm.waw.pl on Thu, Mar 29, 2001 at 01:03:29AM +0200

Krzysztof Halasa <khc@intrepid.pm.waw.pl> écrit :
[...]
> That's a physical interface like V.35 or RS232.

Ok.

[...]
> > * n200, t200 ?
> 
> What's that?

Parameters for retransmission of a trame specified in Q922. t200 is the
timeout value and n200 the maximal number of retransmissions. They can
be negocied and default to t200=1,5s, n200=3.

> > Do we put the crc type here ?
> 
> I don't think so. Frame Relay uses only standard CRC. Correct me if I'm
> wrong.

Ok.

[...]
> > While we're here, could we agree on the notion of raw hdlc, i.e. :
> > - no address, no command. crc present (ARPHRD_RAWHDLC ?);
> > - no address, no command, no crc (ARPHRD_PATHOLOGICHDLC ?).
> 
> Do we really need another ARPHRD for that?
> BTW: What protocol(s) use such CRC-less HDLC?

No protocol I know. Sometime one just want to verify how a driver performs
when he receives badly fscked data. One can live without it.

-- 
Ueimor

  parent reply	other threads:[~2001-03-29  9:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3itkuq6xt.fsf@intrepid.pm.waw.pl>
2001-03-28 21:24 ` RFC: configuring net interfaces Ivan Passos
2001-03-29  0:11   ` Jeff Garzik
2001-03-28 21:53     ` Ivan Passos
2001-03-29 11:29     ` Krzysztof Halasa
2001-03-30  5:43       ` Jeff Garzik
2001-03-31 22:41         ` Krzysztof Halasa
2001-04-01 22:18           ` Jeff Garzik
2001-04-02 19:10             ` Krzysztof Halasa
2001-04-03  8:27               ` Francois Romieu
2001-04-03 13:07                 ` Krzysztof Halasa
2001-04-04  8:18                   ` Francois Romieu
2001-03-29 11:24   ` Krzysztof Halasa
     [not found] ` <20010328182729.A16067@se1.cogenit.fr>
2001-03-28 23:03   ` Krzysztof Halasa
2001-03-29  0:13     ` Paul Fulghum
2001-03-29 10:34       ` Krzysztof Halasa
2001-03-29  9:25     ` Francois Romieu [this message]
2001-03-29 11:07       ` Krzysztof Halasa
2001-03-29 14:55         ` Paul Fulghum

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=20010329112547.A23947@se1.cogenit.fr \
    --to=romieu@cogenit.fr \
    --cc=khc@intrepid.pm.waw.pl \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox