From: Helge Deller <Helge.Deller@ruhr-uni-bochum.de>
To: parisc-linux@thepuffingroup.com,
Alex deVries <adevries@thepuffingroup.com>,
phi@tcleur.france.hp.com
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 715/80 problems
Date: Fri, 24 Sep 1999 11:42:13 +0200 [thread overview]
Message-ID: <99092412012906.00271@P100> (raw)
In-Reply-To: 37E917A0.CEBD1D71@thepuffingroup.com
Am Wed, 22 Sep 1999 schrieb Alex deVries:
> phi@tcleur.france.hp.com wrote:
> >
> > With the regression that occured after 14 september 1999, or so (20
> > septembre is wrong, 14 setp is good), I can't use it anymore.
> >
> > I'm think about a newfs to regain the full HFS capacity unless one of
> > you can tell me this will be put back as it was before. For now I assume
> > the vmlinux is not supposed to boot from isl> hpux right?
>
> It's *supposed to* work, but it doesn't.
>
> Ah, okay. This means that we should just be able to see what changed on
> Sept. 14 and figure out what to fix.
>
> Is anyone interested in fixing this?
Hi Philippe,
Hi Alex.
I´m not really sure, but maybe I know why it doesn´t boot any longer.
Phi, could you look in the file arch/parisc/Makefile in the section
LDFLAGS=-R<yyy> if your working version has <yyy> as 0x10000 and your
non-working version has 0xC0010000. If yes, then it shows that the
hpux-bootloader isn´t able to load our kernel into the virtual space at
0xC0000000 and directly stops [segfaults?] without any message. One possible
solution could be, to patch the contents of the vmlinux-file at offsets 0x18,
(0x28??), 0x8A and 0x98 with &= 0xFFFFFFF (without C0). Please take a look in
the som.h-file, which contents have to be patched ! This way the hpux-loader
could load the kernel to the correct adress-room and the kernel
(already) automatically sets up the virtual adress-mapping.
In our own bootloader we read the contents of this header too and use the
"ADJ_LOW"-Function to get the correct adresses before loading the kernel.
Sure, maybe I´m totally wrong !
Helge Deller.
>
> - Alex
next prev parent reply other threads:[~1999-09-24 9:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-22 17:02 [Fwd: [parisc-linux] 715/80 problems] phi
1999-09-22 17:53 ` Alex deVries
1999-09-24 9:42 ` Helge Deller [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-16 21:58 [parisc-linux] 715/100 data page fault and msg output Grant Grundler
1999-09-22 11:48 ` [parisc-linux] 715/80 problems Hannu Martikka
1999-09-22 13:35 ` Philipp Rumpf
1999-09-22 14:27 ` Hannu Martikka
1999-09-22 14:29 ` Philipp Rumpf
1999-09-22 14:31 ` Grant Grundler
1999-09-22 15:15 ` Hannu Martikka
1999-09-22 17:00 ` Alex deVries
1999-09-22 13:42 ` Grant Grundler
1999-09-22 15:18 ` Hannu Martikka
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=99092412012906.00271@P100 \
--to=helge.deller@ruhr-uni-bochum.de \
--cc=adevries@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=phi@tcleur.france.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.