[parisc-linux] Progress

[Philipp Rumpf]

> If interrupts can happen (and get serviced), a CR16 loop is inherently
> unreliable.  If you're looping until CR16 becomes >= some value, X, then
> you might find that CR16 goes:   n, n+2, n+3, n-10000, n-9998, ...
> 
> I.e., the interrupt servicing could take enough time that the value in
> CR16 becomes misleading.  If the new CR16 is < the last seen one, is it
> simply because it "rolled over", or because an interrupt came in and 
> you've spent an unknown amount of time doing other things?

Look at the loop.  What we do is basically

	cr16 = mfctl(16);
	while(((cr16+loops)-mfctl(16))>0);

Which works well, unless CR16 suddenly changes by 2^31 or more.  This
would correspond to 10-20 seconds spent in an interrupt handler which
is unlikely (and will have negative effects on our timer interrupt as
well).

> OTOH, I like the idea of using a drastic change to CR16 as a signal
> that "something happened", and consider using that as a clue 
> to prematurely exit a counter-based loop.  In that scenario, I'd
> expect a routine like:   delay (int loops,  int premature_exit_ok),
> which would let the caller decide if a premature (CR16 change based)
> exit was allowable.

And what exactly would be the advantage ?

	Philipp Rumpf

X-From-Line: hppa-linux@thepuffingroup.com  Wed Mar 10 14:51:30 1999
Return-Path: <hppa-linux@thepuffingroup.com>
Received: from merlin.pcj.primenet.com (pcj@merlin.pcj.primenet.com [192.168.111.10])
	by merlin.pcj.primenet.com (8.8.7/8.8.7) with ESMTP id OAA03715
	for <pcj@merlin.pcj.primenet.com>; Wed, 10 Mar 1999 14:51:29 -0800
Resent-From: hppa-linux@thepuffingroup.com
Received: from pop.primenet.com
	by merlin.pcj.primenet.com (fetchmail-4.4.7 POP3)
	for <pcj/merlin.pcj.primenet.com> (single-drop); Wed, 10 Mar 1999 14:51:29 PST
Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133])
	by primenet.com (8.8.8/8.8.5) with ESMTP id HAA02680
	for <pcj@smtp-local.primenet.com>; Wed, 10 Mar 1999 07:38:22 -0700 (MST)
Received: (from daemon@localhost)
	by smtp03.primenet.com (8.8.8/8.8.8) id HAA10178
	for <pcj@primenet.com>; Wed, 10 Mar 1999 07:39:29 -0700 (MST)
Received: from SOD.RES.CMU.EDU(128.2.91.30)
 via SMTP by smtp03.primenet.com, id smtpd010163; Wed Mar 10 07:39:23 1999
Received: (from listserv@localhost)
	by sod.res.cmu.edu (8.8.7/8.8.7) id JAA02127;
	Wed, 10 Mar 1999 09:06:14 -0500
Resent-Date: Wed, 10 Mar 1999 09:06:14 -0500
X-Authentication-Warning: sod.res.cmu.edu: listserv set sender to hppa-linux-request@thepuffingroup.com using -f
Delivered-To: thepuffi-hppa-linux@thepuffingroup.com
Message-ID: <19990310090611.M27177@cmu.edu>
Date: Wed, 10 Mar 1999 09:06:11 -0500
From: Phil Schwan <pschwan@cmu.edu>
To: hppa-linux@thepuffingroup.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91i
Subject: [hppa-linux] New cross compiling RPMs
Resent-Message-ID: <"IQFEx1.0.9X.Lndvs"@sod.res.cmu.edu>
Reply-To: hppa-linux@thepuffingroup.com
X-Mailing-List: <hppa-linux@thepuffingroup.com> archive/latest/159
X-Loop: hppa-linux@thepuffingroup.com
Precedence: list
Resent-Sender: hppa-linux-request@thepuffingroup.com
X-UIDL: 8d5765b337395793ff76953a72029da1
Lines: 19
Xref: merlin.pcj.primenet.com palinux:129

Mike Shaver just rebuilt Alex's cross compiling RPMs against glibc 2.0
rather than 2.1, and they're now available on sod:

ftp://sod.res.cmu.edu/pub/parisc/tools/egcs-x-hppa-linux-1.1.1-4.i386.rpm
ftp://sod.res.cmu.edu/pub/parisc/tools/binutils-x-hppa-2.9.1-4.i386.rpm

Note that the revision number is still 4, but these are in fact new. 

-Phil

------------------------------------------------------------------
"In film you will find four basic story lines. Man versus man, man
versus nature, nature versus nature, and dog versus vampire."
        - Steven Spielberg

-------------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@thepuffingroup.com with
`unsubscribe' as the subject.