Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Ryan Bradetich <rbradetich@uswest.net>
To: Philipp Rumpf <Philipp.H.Rumpf@mathe.stud.uni-erlangen.de>
Cc: Alex deVries <adevries@thepuffingroup.com>,
	paul_bame@hp.com, Parisc Linux <parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] arch/parisc/kernel/realmode_setup.c Question
Date: Mon, 15 Nov 1999 07:15:19 -0700	[thread overview]
Message-ID: <38301576.C614F7FA@uswest.net> (raw)
In-Reply-To: 19991115082044.B30917@mathe.stud.uni-erlangen.de

Philipp Rumpf wrote:

> > > How far does it actually boot though?
>
> > Transferring control to kernel. (At entry point 0x00010000)
> > kernel(0x00148C80, 0x00504010, 0x00148C80, 0x00016640)
> > Clear BSS 0x0011B048 --> 0x0013D690
> > Boot loader: PA/Linux, maybe PALO
> > realmode_setup exiting
> >
> > ... At this point it hangs.  Before, it always used to hang at:
> > Transferring control to kernel. (At entry point 0x00010000)
> >
> > I still do not believe it ever successfully finished the rfi in head.S :(
> > I still need to do some more research to verify this, but that is my
> > gut feeling right now.
>
> This sounds right.  It is indeed possible we cannot install a BTLB entry on
> your CPU (and the firmware just reports success as it is free to according to
> the documentation) or the BTLB entry gets removed before we get the chance to
> do our first printk.

Ahh, ok.  I think I'm begining to understand what is happening now (finally).  Is
their
a way to check the BTLB entry and see if it is their right after we we insert the
entry?
or will th real-mode code take care of that?  (I would still like to know what is
happening, I've spent a lot of time tring to figure this out :))

>
> For both problems, the answer is within reach, and is called "a separate direc-
> tory for real-mode code".  Being able to debug unexpected TLB insertion handler
> calls is one of the immediate advantages of having this directory, and sure is
> going to be useful in the future (and would have been useful in the past).

Great!  Anything I can do to help?  I am just learning how this all works, but I
am very
interested in helping.

>
> Wanna bet we're going to get that machine to a sash prompt this week ?

Very, Very nice. Then hopefully I'll be able to contribute more.  I've been
wanting to get
this port to boot on this machine for a long time now :)  This is going to be a
great week!!

- Ryan


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

  parent reply	other threads:[~1999-11-15 14:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-14 22:49 [parisc-linux] arch/parisc/kernel/realmode_setup.c Question Ryan Bradetich
1999-11-15  0:59 ` Alex deVries
1999-11-15  1:01   ` Ryan Bradetich
1999-11-15  4:42     ` Alex deVries
1999-11-15  7:20     ` Philipp Rumpf
1999-11-15 13:28       ` Matthew Wilcox
1999-11-15 14:15       ` Ryan Bradetich [this message]
1999-11-15 23:02 ` Frank Rowand
1999-11-16  0:31   ` Alex deVries
1999-11-15 23:34     ` Frank Rowand
1999-11-16  0:48       ` Alex deVries
1999-11-15 23:42         ` Frank Rowand
1999-11-16 14:02           ` Ryan Bradetich
1999-11-16 21:32             ` Frank Rowand
1999-11-15 23:11 ` [parisc-linux] use of (*PAGE0->mem_pdc)() Frank Rowand
1999-11-17  4:49   ` Philipp Rumpf
  -- strict thread matches above, loose matches on Subject: below --
1999-11-15 18:33 [parisc-linux] arch/parisc/kernel/realmode_setup.c Question bame

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=38301576.C614F7FA@uswest.net \
    --to=rbradetich@uswest.net \
    --cc=Philipp.H.Rumpf@mathe.stud.uni-erlangen.de \
    --cc=adevries@thepuffingroup.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=paul_bame@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox