Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] FB on c3k
Date: Thu, 7 Mar 2002 11:03:39 +0100	[thread overview]
Message-ID: <20020307110339.A1590@solo.franken.de> (raw)
In-Reply-To: <20020307073117.4C572482F@dsl2.external.hp.com>; from grundler@dsl2.external.hp.com on Thu, Mar 07, 2002 at 12:31:16AM -0700

On Thu, Mar 07, 2002 at 12:31:16AM -0700, Grant Grundler wrote:
> Thomas Bogendoerfer wrote:
> > No jsm is right, the U bit doesn't matter, if we set the right
> > physical address in the TLB. I really don't understand why it's
> > needed to supply more than 40bit,
> 
> B2600 has PA-8600. Maybe PA-8600 needs 44 bits of physical address?
> PA-8000 only needed 40-bits, iirc.
> I thought N-class (PA-8500) used 44-bits.

after sleeping over the problem, I believe we were short just one bit. We
extracted 32 bits from the PTE. The lower 5 bits are zeroed and will
be the 4 size bits and the one 0 bit in the TLB. That leaves 27 bits for
the physical page number. Adding the 12 offset bits for 4k pages gives us
just 39 bits, but we need 40. So instead of the change 32 -> 52 a
change from 32 -> 33 should do the same. On the other side using all
bits shouldn't matter and we are prepared for 44 bit and more. BTW.
isn't our current PDC space expansion wrong for "odd" sized address
spaces ? It should work for 48 and 56, but not for anything else.
Or do I miss something ?

I'm packing for Cebit at the moment, and will be away for 2 weeks. So
I can't check my theory in the next days. I will have a J6700 at Cebit
to play with, but I don't think I'll get spare time in the next couple
of days.

> I tried it with 32-bit kernel on c3k.  That hpmc'd.
> (Vis-EG, 1600x1200 8bit).
> Are you using 64-bit kernel?

yes,  with your last ioctl32 changes. I need to recheck my first entry.S
hack for the narrow mode pa2.0 tlb handler. I think my assembler code
just sucks and setting up the tlbs the same way as for wide mode,
should get us X with 32-bit kernels, too.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                 [ Alexander Viro on linux-kernel ]

  reply	other threads:[~2002-03-07 10:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06  8:01 [parisc-linux] FB on c3k Grant Grundler
2002-03-06 23:22 ` Thomas Bogendoerfer
2002-03-07  7:31   ` Grant Grundler
2002-03-07 10:03     ` Thomas Bogendoerfer [this message]
2002-03-10  6:56       ` Grant Grundler
2002-03-07 14:00     ` Carlos O'Donell Jr.
     [not found] <Pine.LNX.4.44.0203061421250.17588-100000@sal.ucc.ie>
2002-03-06 16:46 ` Grant Grundler
2002-03-06 22:19   ` M. Grabert

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=20020307110339.A1590@solo.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=grundler@dsl2.external.hp.com \
    --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