public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] 1/5: cmd_boot
Date: Mon, 31 Mar 2003 17:03:55 +0200	[thread overview]
Message-ID: <20030331150355.GK7702@pengutronix.de> (raw)
In-Reply-To: <20030331144737.38C11C587C@atlas.denx.de>

On Mon, Mar 31, 2003 at 04:47:32PM +0200, Wolfgang Denk wrote:
> You patch does not delete code, but  it  adds  code,  increasing  the
> size:

We are talking about this piece of code, right? 

> +
> +	/*
> +	 * Gather any trailing characters (for instance, the ^D which
> +	 * is sent by 'cu' after sending a file), and give the
> +	 * box some time (100 * 1 ms)
> +	 */
> +	for (i=0; i<100; ++i) {
> +		if (serial_tstc()) {
> +			(void) serial_getc();
> +		}
> +		udelay(1000);
> +	}
> +

Exactly this code sniplet was located directly after the call to
load_serial_bin() in cmd_boot.c:do_load_serial_bin() before I started
looking for the problems. When I sent my first patch which _removed_
this code I somehow forgot to send you the hunk which adds it at the
right place. So this patch does not add new code, it only re-adds the
hunk which was removed instead of re-located to the right place.

Before: 
	load_serial_bin();
		download via kermit
		say "I'm finished"
	throw away garbage characters
	go on

Now: 
	load_serial_bin();
		download via kermit
		throw away garbage characters
		say "I'm finished"
	go on. 

I hope you understand what I mean... 

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Braunschweiger Str. 79,  31134 Hildesheim, Germany
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
    Phone: +49-5121-28619-0 |  Fax: +49-5121-28619-4

  reply	other threads:[~2003-03-31 15:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31  9:28 [U-Boot-Users] [PATCH] 1/5: cmd_boot Robert Schwebel
2003-03-31 10:12 ` Wolfgang Denk
2003-03-31 10:33   ` Robert Schwebel
2003-03-31 10:55     ` Wolfgang Denk
2003-03-31 11:12       ` Robert Schwebel
2003-03-31 11:38         ` Wolfgang Denk
2003-03-31 11:45           ` Robert Schwebel
2003-03-31 12:31             ` Wolfgang Denk
2003-03-31 12:43               ` Robert Schwebel
2003-03-31 14:03                 ` Wolfgang Denk
2003-03-31 14:16                   ` Robert Schwebel
2003-03-31 14:47                     ` Wolfgang Denk
2003-03-31 15:03                       ` Robert Schwebel [this message]
2003-03-31 18:10                         ` Wolfgang Denk
2003-03-31 18:20                           ` Robert Schwebel
  -- strict thread matches above, loose matches on Subject: below --
2003-03-31 12:13 Chris Elston
2003-03-31 12:34 ` Wolfgang Denk
2003-03-31 12:32 Chris Elston
     [not found] <000263AC.C22236@radstone.co.uk>
2003-03-31 13:18 ` Jerry Van Baren
2003-03-31 13:41   ` Robert Schwebel
2003-03-31 14:39     ` Holger Schurig
2003-03-31 14:06   ` Wolfgang Denk
     [not found] <0002649B.C22236@schwebel.de>
2003-03-31 14:00 ` Jerry Van Baren
2003-03-31 15:17   ` Robert Schwebel
2003-03-31 15:57     ` Wolfgang Denk
     [not found] <000265CA.C22236@denx.de>
2003-03-31 15:21 ` Jerry Van Baren
2003-03-31 15:40   ` Wolfgang Denk

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=20030331150355.GK7702@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=u-boot@lists.denx.de \
    /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