All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Katz <billk@sr.hp.com>
To: hppa-linux@thepuffingroup.com
Subject: Re: [hppa-linux] Another bootstrap test
Date: Fri, 26 Feb 1999 16:47:23 -0800 (PST)	[thread overview]
Message-ID: <199902270047.QAA27829@meow.sr.hp.com> (raw)
In-Reply-To: <199902262352.RAA13983@equator.com> from Jason Eckhardt at "Feb 26, 1999  5:52: 6 pm"

> I would appreciate it if a few people would try out this updated bootstrap
> code on their systems (same directions as last time). This is basically
> complete, it loads and executes a "dummy" kernel. It has only been tested on
> a C160 so far.
> This is a debug version and prints a lot of noise. It would be useful if
> you would capture the output and email it to me. Or at least send the numbers 
> for:
>  P0_IMM_max_mem, P0_BOOTCPU_10msec, P0_COUT_class, P0_CIN_class, and
>  P0_BOOTDEV_class.
> 
> If it works completely, you'll see a message from the dummy kernel image
> folloed by "It is now safe to reboot." Let me know if it makes it that far
> on your system.
> 
> Thanks, Jason Eckhardt.
> 

Jason,
	I tried this on a board I use here at work, it is very similar
to a B32/B160.  It gets through a bunch of stuff, and then dies:

PARISC/Linux Bootstrap Version 0.1 (non-interactive)
By Jason Eckhardt
Built Fri Feb 26 17:19:38 CST 1999 by jason@bimbo

IPL_DEBUG: Page zero parameters:
  P0_IMM_max_mem:          167772160 (160MB)
  P0_IMM_spa_size:         167772160
  P0_MC_cont_size:         167772160
  P0_MC_phys_size:         167772160
  P0_MC_ad_size:           167772160
  P0_BOOTCPU_mem_free:     0x00008000
  P0_BOOTCPU_hpa:          xFFFBE000
  P0TCPU_pdc:       0x00004800
  P0_BOOTCPU_10msec:       1200000
  P0_COUT_iodc_io:         0x00008000
  P0_CIN_iodc_io:          0x00008000
  P0_BOOTDEV_iodc_io:      0x00012000
  P0_COUT_class:           0x00000007
  P0_CIN_class:            0x00000007
  P0_BOOTDEV_class:        0x00001002
Reading parameters...done.
(kerneÿÐpLoading kernel..done.
Transferring contrFLT  1009

The FLT1009 is a chassis code that means "Unexpected interrupt".  You did
get the speed correct at 120 MHz.  I booted over LAN via tftp.

	-Bill


-------------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@thepuffingroup.com with
`unsubscribe' as the subject.

  reply	other threads:[~1999-02-27  0:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-26 23:52 [hppa-linux] Another bootstrap test Jason Eckhardt
1999-02-27  0:47 ` Bill Katz [this message]
1999-03-01 19:29   ` Heiko Christian Jakob
1999-02-27  2:14 ` Kevin Vajk
1999-02-27  5:43 ` Alex deVries
1999-02-27 22:34 ` Paul J.Y. Lahaie
  -- strict thread matches above, loose matches on Subject: below --
1999-02-27  1:10 Markus Döhr
1999-02-28 17:00 ` Grant Grundler
1999-03-02  0:34   ` Steven Beattie
1999-02-28  4:23 Jason Eckhardt
1999-03-01 21:26 Mandachi, Dorin (Omaha)

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=199902270047.QAA27829@meow.sr.hp.com \
    --to=billk@sr.hp.com \
    --cc=hppa-linux@thepuffingroup.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.