From: "Paul Fulghum" <paulkf@microgate.com>
To: <linux-kernel@vger.kernel.org>,
"Krzysztof Halasa" <khc@intrepid.pm.waw.pl>
Cc: "Francois Romieu" <romieu@cogenit.fr>
Subject: Re: RFC: configuring net interfaces
Date: Wed, 28 Mar 2001 18:13:10 -0600 [thread overview]
Message-ID: <003101c0b7e5$0c53dbb0$0201a8c0@mojo> (raw)
In-Reply-To: LINKIFYFDJbdfbAEJCGeBJddfEcbcIIGFFHJeGeGHaHdAaALINKIFYCIJeBcdAEHDaBIDfBddHbccAbIAeafHJCGFDadBI <m34rwd8pj2.fsf@intrepid.pm.waw.pl>
From: "Krzysztof Halasa" <khc@intrepid.pm.waw.pl>
> +struct hdlc_physical /* 10 bytes */
> +{
> + unsigned int interface;
> + unsigned int clock_rate;
> + unsigned short clock_type;
> +};
What about encoding (NRZ/NRZI)?
Plus I think the CRC type would be a good idea for
raw HDLC mode. (CRC-16, CRC-32, no CRC)
Paul Fulghum
paulkf@microgate.com
next prev parent reply other threads:[~2001-03-29 0:15 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 [this message]
2001-03-29 10:34 ` Krzysztof Halasa
2001-03-29 9:25 ` Francois Romieu
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='003101c0b7e5$0c53dbb0$0201a8c0@mojo' \
--to=paulkf@microgate.com \
--cc=khc@intrepid.pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@cogenit.fr \
/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