Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Keith M Wesolowski <wesolows@foobazco.org>
To: Phil Thompson <Phil.Thompson@pace.co.uk>
Cc: "'Erik Mullinix'" <Hesp@rainworks.org>, linux-mips@oss.sgi.com
Subject: Re: Recommended toolchain
Date: Wed, 21 Mar 2001 14:06:16 -0800	[thread overview]
Message-ID: <20010321140616.A3956@foobazco.org> (raw)
In-Reply-To: <1402C4C025C4D311B50D00508B8B74E281B151@exchange1>; from Phil.Thompson@pace.co.uk on Wed, Mar 21, 2001 at 06:46:07PM -0000

On Wed, Mar 21, 2001 at 06:46:07PM -0000, Phil Thompson wrote:

> - compilation stops because loops_per_sec is undeclared as far as
> asm-mips/delay.h is concerned (although it seems fine in
> asm-mips64/delay.h).
> 
> This seems to imply that the mips architecture (as opposed to mips64) isn't
> being maintained. Is this the case? Should I be using mips64 - but what
> would be the point on an embedded CPU?

mips(32) is in fact being actively maintained.  It sounds like your
kernel sources may be out of date; I specifically remember removing
all references to loops_per_sec in favour of loops_per_jiffy in both
mips and mips64.

Ask again about fcntl.h after updating...

-- 
Keith M Wesolowski <wesolows@foobazco.org> http://foobazco.org/~wesolows
------(( Project Foobazco Coordinator and Network Administrator ))------
"I should have crushed his marketing-addled skull with a fucking bat."

  reply	other threads:[~2001-03-21 22:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 18:46 Recommended toolchain Phil Thompson
2001-03-21 22:06 ` Keith M Wesolowski [this message]
2001-03-22  7:49 ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2003-04-10 19:23 recommended toolchain carbonated beverage
2001-03-22  9:39 Recommended toolchain Phil Thompson
2001-03-22  9:43 ` Geert Uytterhoeven
2001-03-21 14:00 Phil Thompson
2001-03-21 12:11 ` Erik Mullinix
2001-03-21 16:06 ` Keith M Wesolowski
2001-03-20  3:06 Simon Gee
2001-03-20 20:12 ` Karel van Houten
2001-03-20 20:12   ` Karel van Houten
2001-03-20 20:37   ` Ralf Baechle
2001-03-20 20:37     ` Ralf Baechle
2001-03-27 19:02   ` Maciej W. Rozycki
2001-03-29 17:28     ` Houten K.H.C. van (Karel)
2001-03-29 17:28       ` Houten K.H.C. van (Karel)
2001-03-29 17:39       ` Karel van Houten
2001-03-29 17:39         ` Karel van Houten
2001-03-29 18:10         ` Maciej W. Rozycki
2001-04-01 14:39           ` Houten K.H.C. van (Karel)
2001-04-01 18:54             ` Florian Lohoff
2001-03-29 17:51       ` Maciej W. Rozycki

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=20010321140616.A3956@foobazco.org \
    --to=wesolows@foobazco.org \
    --cc=Hesp@rainworks.org \
    --cc=Phil.Thompson@pace.co.uk \
    --cc=linux-mips@oss.sgi.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