Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ulf Carlsson <ulfc@thepuffingroup.com>
To: "Andrew R. Baker" <andrewb@uab.edu>
Cc: Linux SGI <linux@cthulhu.engr.sgi.com>
Subject: Re: Indigo2 patch
Date: Sun, 2 May 1999 20:53:47 +0200	[thread overview]
Message-ID: <19990502205347.A7346@thepuffingroup.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990502111429.14447B-200000@mdk187.tucc.uab.edu>; from Andrew R. Baker on Sun, May 02, 1999 at 11:24:54AM -0500

> OK, since this is my first time making a patch I am not sure I got
> everything quite right.  This will let people with an Indigo2 actually
> boot into Linux.  However, they probably won't be able to do much

Cool!

> thereafter (I get the kernel to die while doing a 'cat README' in the root
> directory).  Unfortunately, this won't print the console boot messages to
> the screen either.  To do this, I replaced the printk code in
> kernel/printk.c with the printf code in arch/mips/arc/printf.c.  I'm sure
> there is a better way, but I haven't found it yet.  These were made

Yes, there's a better way. A PROM console can be implemented. I have hacked some
code for this PROM console for this purpose. I can't get it to open the initial
console though. I'll send it to you, maybe you have time to figure out what's
wrong...

> -LINKFLAGS	= -static -N
> +# having -N in LINKFLAGS causes my Indigo2 not to boot
> +LINKFLAGS	= -static

This is a problem with the cross linker and not with the kernel itself, it's the
same for Indy's. The code in the CVS tree should remain as it is.

- Ulf

  reply	other threads:[~1999-05-02 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-02 16:24 Indigo2 patch Andrew R. Baker
1999-05-02 18:53 ` Ulf Carlsson [this message]
1999-05-03  1:31   ` Andrew R. Baker
1999-05-04 10:59     ` Ralf Baechle
1999-05-07 15:11 ` Andrew R. Baker
1999-05-07 17:43   ` Ulf Carlsson
  -- strict thread matches above, loose matches on Subject: below --
1999-06-03 19:57 Andrew R. Baker
1999-06-04 20:07 ` Andrew R. Baker

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=19990502205347.A7346@thepuffingroup.com \
    --to=ulfc@thepuffingroup.com \
    --cc=andrewb@uab.edu \
    --cc=linux@cthulhu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox