Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Sep 2001 09:54:59 -0700
From:      Marcel Moolenaar <marcel@xcllnt.net>
To:        Doug Rabson <dfr@nlsystems.com>
Cc:        cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/ia64/ia64 sscclock.c
Message-ID:  <20010914095458.A465@dhcp01.pn.xcllnt.net>
In-Reply-To: <20010914092922.C398-100000@salmon.nlsystems.com>
References:  <20010913171854.A537@dhcp01.pn.xcllnt.net> <20010914092922.C398-100000@salmon.nlsystems.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 14, 2001 at 09:30:21AM +0100, Doug Rabson wrote:
> On Thu, 13 Sep 2001, Marcel Moolenaar wrote:
> 
> > On Thu, Sep 13, 2001 at 10:02:43PM +0100, Doug Rabson wrote:
> > > > >
> > > > > This causes large scale memory corruption. The SSC call bzero's a big
> > > > > chunk of the GOT :-(.
> > > >
> > > > Hmm... I haven't seen any strange behaviour by enabling it. I take a
> > > > look at it. If you prefer to disable the RTC call for now, feel free
> > > > to do so (if you haven't done it already) or otherwise let me know.
> > >
> > > I have disabled it locally for now. Perhaps I'm using a different version
> > > of xski? I have the Linux xski with version 0.8731 (EAS 2.5).
> >
> > Hmmm, I'm using my (partly finished) FreeBSD port of version 0.943
> > (EAS 2.6). I'll pick up version 0.8731 somewhere and experiment with
> > that.
> 
> Exactly how functional is your port? If it works well enough to run our
> loader and kernel code, they I would really like a copy...

I've been working on the batch mode first. That runs our kernel just
fine (pre skiloader). I got a coredump in xski that is likely to be
related to getting the source lines in the program window. I don't
expect mayor difficulties.

There's just one thing I want to really fix: the console handling.
The batched mode ski (bski) creates an xterm console by default, just
like ski (interactive; curses UI) and xski (interactive; Motif UI)
bski shouldn't create a console and the FreeBSD port happily uses
stdin and stdout as its console. For xski it's reasonable to create a
xterm based console. For the curses interface I like to have a seperate
curses window instead of a xterm console. The latter might be too much
window space wise.

What I don't have are the syscalls. I also implemented the SSC calls
on a need to have basis. So we're incomplete there as well.

I'll let you know when I have resolved the coredump and when I've
verified the skiloader.

NOTE1: I'm porting to Alpha at the same time. Both i386 and Alpha are
       in the same state.
NOTE2: The FreeBSD port of ski depends on OpenMotif.

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel@xcllnt.net

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010914095458.A465>