public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Adrian Levi <adrian@lefty.dyndns.org>
Cc: alan@lxorguk.ukuu.org.uk, werner.almesberger@epfl.ch,
	linux-kernel@vger.kernel.org
Subject: Re: LILO and serial speeds over 9600
Date: Mon, 12 Feb 2001 22:12:59 -0800	[thread overview]
Message-ID: <3A88D06B.26453D40@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102131506230.30955-100000@lefty.dyndns.org>

Adrian Levi wrote:
> 
> I usually lurk on the list and don't contribute but I would like to
> place my 2 bob in to the fro. Would a modified X-Modem protocol stack suit
> this operation? No sliding window and don't send anything until you
> receive an ack back?
> 

Not particularly.  Xmodem and TFTP are very similar.

Anyway, I repeat what I said about there being too many cooks in the
kitchen at the moment...

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

       reply	other threads:[~2001-02-13  6:13 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0102131506230.30955-100000@lefty.dyndns.org>
2001-02-13  6:12 ` H. Peter Anvin [this message]
2001-02-12 15:45 LILO and serial speeds over 9600 Ivan Passos
2001-02-12 16:53 ` Ivan Passos
2001-02-12 18:47   ` H. Peter Anvin
2001-02-12 20:39     ` James Sutherland
2001-02-12 20:54       ` H. Peter Anvin
2001-02-12 22:55         ` James Sutherland
2001-02-14 11:45           ` Pavel Machek
2001-02-12 21:52       ` Alan Cox
2001-02-12 22:10         ` H. Peter Anvin
2001-02-12 22:25           ` Alan Cox
2001-02-12 23:11             ` Werner Almesberger
2001-02-12 23:16               ` Alan Cox
2001-02-12 23:20                 ` H. Peter Anvin
2001-02-12 23:27                   ` Alan Cox
2001-02-12 23:53                     ` H. Peter Anvin
2001-02-13  0:11                       ` Alan Cox
2001-02-13  0:17                         ` Tim Wright
2001-02-13  0:23                           ` H. Peter Anvin
2001-02-13 10:51                             ` Alan Cox
2001-02-13 10:57                               ` James Sutherland
2001-02-13 12:55                                 ` Russell King
2001-02-13 13:56                                   ` James Sutherland
2001-02-13  0:25                         ` H. Peter Anvin
2001-02-12 23:35                   ` James Sutherland
2001-02-12 23:51                     ` H. Peter Anvin
2001-02-13  0:24                       ` James Sutherland
2001-02-13  0:27                         ` H. Peter Anvin
2001-02-12 23:19             ` H. Peter Anvin
2001-02-12 23:23               ` Alan Cox
2001-02-14 11:53               ` Pavel Machek
2001-02-17 17:26                 ` Patrick Michael Kane
2001-02-17 17:40                   ` James Sutherland
2001-02-12 22:46         ` James Sutherland
2001-02-12 22:50           ` Alan Cox
2001-02-12 18:51   ` H. Peter Anvin
2001-02-12 19:49     ` Scott Laird
2001-02-12 23:17       ` Ivan Passos
2001-02-12 23:30         ` Chris Wedgwood
2001-02-12 23:39         ` David Weinehall
2001-02-13  2:52         ` Michael Rothwell

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=3A88D06B.26453D40@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=adrian@lefty.dyndns.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=werner.almesberger@epfl.ch \
    /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