Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Christoph Martin <martin@uni-mainz.de>
Cc: Dave Gilbert <gilbertd@treblig.org>, linux-mips@oss.sgi.com
Subject: Re: Trying to boot an Indy
Date: Tue, 23 Jan 2001 09:02:51 -0800	[thread overview]
Message-ID: <20010123090250.B945@bacchus.dhis.org> (raw)
In-Reply-To: <wwgofwyckov.fsf@arthur.zdv.Uni-Mainz.DE>; from martin@uni-mainz.de on Tue, Jan 23, 2001 at 05:11:44PM +0100

On Tue, Jan 23, 2001 at 05:11:44PM +0100, Christoph Martin wrote:

> > 1) I tried bootp - bootp()vmlinux - it says 'no server for vmlinux'.  The
> > bootp server is a Linux/Alpha box running 2.4.0-ac9 - I've already done
> > the trick with no_pmtu.  tcpdump shows bootp sending a packet with
> > apparently the correct mac address.
> > 
> 
> I have the same problem serving bootp from my i386 2.4.0 box. bootp
> with kernel 2.2.x on the same box works. And it is only the bootp from
> the command console that is failing. the bootp part later on in the
> kernel is working from the 2.4.0 box.
> 
> Weird.

Not weired at all.  The firmware bootp()... does bootp and then uses tftp
to download the kernel; the kernel then only uses bootp to figure out it's
network configuration.  So the two are not only doing different things,
they're also two are not only two independant and completly different
implementations.

  Ralf

      parent reply	other threads:[~2001-01-23 17:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-21  2:01 Trying to boot an Indy Dave Gilbert
2001-01-21  4:37 ` Ralf Baechle
2001-01-21 13:27   ` Dave Gilbert
2001-01-23 16:11 ` Christoph Martin
2001-01-23 16:34   ` Dr. David Gilbert
2001-01-23 16:34     ` Dr. David Gilbert
2001-01-23 17:23     ` Wills
     [not found]       ` <3A84E2C4.112F8B2F@cotw.com>
2001-02-10 13:14         ` Patch for Philips Nino Steven J. Hill
2001-01-23 17:02   ` Ralf Baechle [this message]

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=20010123090250.B945@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=gilbertd@treblig.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=martin@uni-mainz.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