Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Paul Bame <bame@endor.fc.hp.com>
To: Sam Creasey <sammy@sammy.net>
Cc: willy@thepuffingroup.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] new binutils/gcc
Date: Tue, 29 Feb 2000 16:06:35 -0700	[thread overview]
Message-ID: <E12Pvit-0003UI-00@endor.fc.hp.com> (raw)
In-Reply-To: Your message of "Sun, 27 Feb 2000 13:26:55 EST." <Pine.LNX.4.21.0002271322290.365-100000@sammyville.sammy.net>

= 
= There is, in fact, a relationship there.  r8 isn't set properly at any
= time, it's kludged.  r8 needs to be set to 
= (load addr of .text) & 0xfff00000.   Basically this is used as a pointer
= to the stub table for long branching.  (so, it should be a jump to
= 0xc010049c, which ought to be a stub for start_parisc())

Don't "be" branches cause a pipeline flush?  It might be faster to
do two "bl" branches instead?

= Yeah, it's kinda ugly...  the linker and crt0.S both need to be
= taught about this too.

Ok, I fixed head.S and interruption.S.  After hacking on vmlinux.lds
and a couple small other things, the elf kernel boots to the point
where I need a ramdisk or NFS root to go further, so that's my plan.
Sources are in CVS with the ELF_BRANCH tag.

Things to do:

    The init_task_union alignment is in both vmlinux.lds and
    is known by setup.c and #defined yet another place.  This ought
    to be cleaned up if possible.

    The init_task_union printf in setup.c should be fixed.

    It's probably time to start using the __setup stuff we hacked
    around for SOM.

    Fix 'make Image' or nuke it.  'make palo' works (for me anyway)

    Sammy said, and I didn't touch these (though others have in the
    main line):

	I guarantee that launching som/elf binaries won't work.  page faulting
	looks messed up somewhere.

	execve() might not work in this one..   I played with the assembler for
	it, but good things never happened, so no changes included.


			-Paul Bame

  reply	other threads:[~2000-03-01  0:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-15  8:09 [parisc-linux] new binutils/gcc willy
2000-02-25 21:12 ` Paul Bame
2000-02-27 18:26   ` Sam Creasey
2000-02-29 23:06     ` Paul Bame [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-15  4:02 willy

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=E12Pvit-0003UI-00@endor.fc.hp.com \
    --to=bame@endor.fc.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=sammy@sammy.net \
    --cc=willy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox