All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@Julia.DE>
To: ariel@sgi.com
Cc: linux@yon.engr.sgi.com
Subject: Re: hardware independent hinv
Date: Wed, 28 May 1997 18:03:20 +0200 (MET DST)	[thread overview]
Message-ID: <199705281603.SAA31716@kernel.panic.julia.de> (raw)
In-Reply-To: <199705281517.IAA10342@yon.engr.sgi.com> from "Ariel Faigon" at May 28, 97 08:17:44 am

> Just forwarding since it sounds someone hopes that Linux/MIPS
> will some day have a HW independent hinv... - Ariel

Larry has shown me a perl script on his Linux/i386 box which does just
this.  I intend to supply the information required by such a script
via the proc filesystem.

  Ralf

> ----- Forwarded message from Dave Olson -----
> 
> >From olson@anchor  Mon May 12 13:50:21 1997
> Date: Mon, 12 May 1997 13:50:18 -0700
> From: olson@anchor (Dave Olson)
> Message-Id: <199705122050.NAA26767@anchor.engr.sgi.com>
> To: olson@anchor (Dave Olson), scotth@sgi.com
> Subject: Re: missing machfile
> Cc: swmgr@swmgr, breyer@swmgr, ariel@cthulhu
> References: <199705121525.IAA23143@swmgr.engr.sgi.com>
>     <199705121714.KAA23773@anchor.engr.sgi.com>
>     <199705121854.LAA18312@anchor.engr.sgi.com>
> 
> |  I would assume that hinv is hardware-dependent, because of the
> |  mapping issues?  Or is it table driven off of an analogue of the machtab?
> 
> Still all compiled in.  Bug/rfe open for years now about making it table
> driven.
> 
> |  Unfortunately, nothing better is generally available across
> |  platforms and releases.
> 
> Yes, and that's something that would be nice to fix.  Maybe linux will
> do it, and we can copy them.
> 
> |  D> Lots, for any non-trivial app.  They don't have to, but often want to.
> |  
> |  ???  Non-trivial as in "big and powerful", or as in "gets close to
> |  the hardware"?  I would argue that emacs and perl both fit the
> 
> Both/either.  Not all  big apps, of course.
> 
> |  I was looking at the options to uname, specifically "-p".  Based
> |  upon the man page, shouldn't `uname -p` return "mips3" instead of
> |  "mips" for my IP22?  That is one obvious meaning for:

Q: what exactly does that IP?? notation stand for?  Internal model names,
CPU modules, ???

> Yes, but then you break even more of the configure scripts.  Again,
> a no-win situation.

You're absolutely right.  For just that reason I changed the output for
little endian MIPS boxes from mipsel to mips a long time ago though
mipsel is logic when thinking of the generic GNU configuration names.

> |  I was just curious is there was somehow we could make life easier
> |  for configure scripts to port software for IRIX...  On the other
> |  hand, we generally only get bad comments about /bin/install, and at
> |  least we *don't* get comments like:

After the last few days I can say that porting to IRIX is a quite boring
job; most things just work.  Only ssh makes problem.  Solved by using
GCC (snapshot) instead of SGI's cc.

> Using cpp is a horrible solution...

Tell the people who invented imake ...

> |  It is hard to add functionality without breaking stuff.
> 
> A programmer's lament, if I ever heard one!

Or break what's broken ...

  Ralf

  parent reply	other threads:[~1997-05-28 16:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-28 15:17 hardware independent hinv Ariel Faigon
1997-05-28 15:17 ` Ariel Faigon
1997-05-28 15:35 ` Mike Shaver
1997-05-28 17:42   ` Miguel de Icaza
1997-05-28 18:18     ` David S. Miller
1997-05-28 19:49       ` Miguel de Icaza
1997-05-30  7:14     ` Martin Knoblauch
1997-05-28 16:03 ` Ralf Baechle [this message]
1997-06-12  1:10   ` My first project on the Indy Miguel de Icaza
  -- strict thread matches above, loose matches on Subject: below --
1997-05-28 19:12 hardware independent hinv Larry McVoy
1997-05-28 19:12 ` Larry McVoy
1997-05-28 19:19 ` Mike Shaver
1997-05-28 19:19   ` Mike Shaver
1997-05-29  2:26 Dave Olson
1997-05-29  2:26 ` Dave Olson
1997-05-30  9:56 ` Raj Mathur
1997-05-30  9:56   ` Raj Mathur

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=199705281603.SAA31716@kernel.panic.julia.de \
    --to=ralf@julia.de \
    --cc=ariel@sgi.com \
    --cc=linux@yon.engr.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 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.