Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] About 2.6 64bit on b2k?
Date: Sun, 01 Feb 2004 12:18:49 +0000	[thread overview]
Message-ID: <401CEEA9.3030500@tiscali.be> (raw)
In-Reply-To: <20040201050043.GC3730@colo.lackof.org>

HI Grant,


Grant Grundler wrote:
> On Sun, Feb 01, 2004 at 12:40:51AM +0000, Joel Soete wrote:
> 
>>I don't understand why it works on c3k and not on b2k.
>>Could it be because by b2k has only 256k of physical ram?
> 
> 
> No. And you meant 256MB.
Oops yes :)

> But c3k and b2k both supported the same DIMMs originally (128 and 256MB
> DIMMS). Minimum mem possible was thus 128MB and I thought 256MB was
> the minimum shipped with each box.
> 
> Sorry - I don't know why reverting that diff matters.
> 
Not more, I will try to objdump the two head64.o and see what the diff?

> 
>>Also, I notice that in head64.S there aren't .import like:
>>[snip]
>>        .import init_thread_union,data
>>        .import $global$                /* forward declaration */
>>        .import fault_vector_11,code    /* IVA parisc 1.1 32 bit */
>>        .import fault_vector_20,code    /* IVA parisc 2.0 32 bit */
>>[snip]
>>
>>as in its 32bit brother head.S
> 
> 
> head64.S only runs wide mode on PA20 HW.
> No need for any PA11 or narrow mode code.
I understand that but less '.import init_thread_union,data' when
[snip]
         /* And the stack pointer too */
         load32          PA(init_thread_union+THREAD_SZ_ALGN),%sp

[snip]
(never the less in the working 2.4 it was the same, so I trust that the problem is very well in the computed pointers?
But I don't have material right now to check ;) )
I am also curious to revert patch on the N (on which the patch works)?

> Look in the Makefile and see when head64.o is linked in.
> Then you'll *SMACK* yourself on the forehead and say "DOH!" :^)
> 
> 
> 
>>I don't yet find the meaning of '.import' but just in case ;)
> 
> 
> AFAIK, it's just telling the assembler where to expect global symbols.
> 
> grant
> 
Many thanks,
	Joel

  reply	other threads:[~2004-02-01 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040128060516.492DE4941AA@palinux.hppa>
2004-01-28 14:00 ` [parisc-linux] RE: [parisc-linux-cvs] linux-2.6 carlos Joel Soete
2004-01-28 23:11   ` Carlos O'Donell
2004-01-29  7:28     ` Joel Soete
2004-01-29  9:25       ` Joel Soete
2004-02-01  0:40         ` [parisc-linux] About 2.6 64bit on b2k? Joel Soete
2004-02-01  5:00           ` Grant Grundler
2004-02-01 12:18             ` Joel Soete [this message]
2004-02-01 20:05         ` [parisc-linux] RE: [parisc-linux-cvs] linux-2.6 carlos Randolph Chung
2004-02-02 10:25           ` Joel Soete
2004-02-02 17:50             ` Joel Soete

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=401CEEA9.3030500@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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