Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Frank Rowand <frank_rowand@hp.com>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: frowand@cup.hp.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] arch/parisc/kernel/realmode_setup.c Question
Date: Mon, 15 Nov 1999 15:02:47 -0800	[thread overview]
Message-ID: <38309117.3707D5FB@hp.com> (raw)
In-Reply-To: 382F3C94.BFF3EB9D@uswest.net

Ryan Bradetich wrote:
> 
> Paul,
> 
> I have started working on getting the kernel to boot on the PA2.0
> architecture again, and I see the you and others have been doing
> lots of work with the initialization code.  (Nice job to everyone btw,
> the code is a lot easier to figure out for a newbie like me! :)
> 
> I was looking at the following section of code and I have a
> discrepancy that I wanted to make you aware of.  I don't know how
> to fix it yet, but I will continue to look.
> 
> I am working on a C200+ which has the PA2.0 processor, so in the
> the following section of code it should give me an error during the
> BTLB initialization, but during the PDC_BTLB_INSERT pret is set
> to 0, so the check for non-PA1.1 architecture's fail.
> 
> I will continue to look through the documentation that has been
> previously pointed out, and the devresource page  pointed out by
> Frank Rowand to see if I can find a solution to the problem.
> 
> Thanks,
> 
> Ryan Bradetich
> 
> [Taken from arch/parisc/kernel/realmode_setup.c]
> 
>  /* This whole VM setup stuff may be removed ultimately.  It seems
>    * to me that once the TLB miss handlers are ready, we just switch
>    * to VM and let them handle TLB population -PB
>    */
> 
>   pret = (*PAGE0->mem_pdc)(
>   PDC_BLOCK_TLB,
>   PDC_BTLB_INSERT,
>   0x00000000,  /* MS bits, virt page number */
>   0xc0000,  /* LS bits, virt page number */
>   0x00000000,  /* Physical page number */
>   4096,   /* # pages to map */
>   0x03000000,  /* access rights, etc... */
>   0);   /* slot number */
> 
>   if (pret != 0)
>  {
>        mprintf("PDC_BTLB_INSERT returned %d\n", pret);
>       if (pret == -1)
>      {
>         mprintf("Looks like there's no BTLB on this box, so it's
> probably\n"
>                        "either PA1.0 or PA2.0.  In any case we're
> screwed for now\n");
>         led_flash();
>      }
> }


Ryan,


This might not solve your problem, but it's worth checking out.  The
procedure calling convention for PA 2.0 PDC is different than for 1.0.
See http://thepuffingroup.com/parisc/documentation.html, pdc.pdf,
p 2-8 defines the return status as a 64-bit, not 32 bit.  You might
also want to look at the neighboring pages of the document for other
changes (eg, arg4 through arg7 are passed in registers).

I don't know if your system has wide or narrow PDC - you have to call
PDC_MODEL(Return Capabilities), and check bit 63 of caps (the field
called OS64).

-Frank

  parent reply	other threads:[~1999-11-15 23:02 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
1999-11-15 23:02 ` Frank Rowand [this message]
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=38309117.3707D5FB@hp.com \
    --to=frank_rowand@hp.com \
    --cc=frowand@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=rbradetich@uswest.net \
    /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