Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@cobaltmicro.com>
To: adevries@engsoc.carleton.ca (Alex deVries)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Arch specific initramdisk?
Date: Thu, 9 Oct 1997 18:27:02 -0700 (PDT)	[thread overview]
Message-ID: <199710100127.SAA10165@dull.cobaltmicro.com> (raw)
In-Reply-To: <Pine.LNX.3.95.971009185152.20315W-100000@lager.engsoc.carleton.ca> from "Alex deVries" at Oct 9, 97 06:57:29 pm

Hi,

> I'm trying to do kernel modifications so that initrd is supported, which
> will make installations easier.
> 
> I was a bit surprised that these weren't architecture neutral to begin
> with.  Why is this dependant on the arch? The code I've found for other
> archs is in arch/*/kernel/setup.c.
> 
> How safe is it for me to replicate the code from, say, the sparc port?  Is
> there anything I should be aware of?

The only difference between the architectures is where in memory the
initrd is being stored.  I haven't check how things work on a Sparc but
basically what we need should be at least very similar to for example
the i386 code - as far as setup.c is affected.

  Ralf

WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@cobaltmicro.com>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Arch specific initramdisk?
Date: Thu, 9 Oct 1997 18:27:02 -0700 (PDT)	[thread overview]
Message-ID: <199710100127.SAA10165@dull.cobaltmicro.com> (raw)
Message-ID: <19971010012702.y1RjaBdlF2K-2eM6ywh5OGSAzFBC52FSkZnjwHwWDO8@z> (raw)
In-Reply-To: <Pine.LNX.3.95.971009185152.20315W-100000@lager.engsoc.carleton.ca> from "Alex deVries" at Oct 9, 97 06:57:29 pm

Hi,

> I'm trying to do kernel modifications so that initrd is supported, which
> will make installations easier.
> 
> I was a bit surprised that these weren't architecture neutral to begin
> with.  Why is this dependant on the arch? The code I've found for other
> archs is in arch/*/kernel/setup.c.
> 
> How safe is it for me to replicate the code from, say, the sparc port?  Is
> there anything I should be aware of?

The only difference between the architectures is where in memory the
initrd is being stored.  I haven't check how things work on a Sparc but
basically what we need should be at least very similar to for example
the i386 code - as far as setup.c is affected.

  Ralf

  reply	other threads:[~1997-10-10  1:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-09 22:57 Arch specific initramdisk? Alex deVries
1997-10-10  1:27 ` Ralf Baechle [this message]
1997-10-10  1:27   ` Ralf Baechle
1997-10-10 23:41 ` make zImage, and initrd Alex deVries
1997-10-11  0:58   ` Ralf Baechle
1997-10-11  0:58     ` Ralf Baechle
1997-10-11  6:11     ` Warner Losh
1997-10-11  6:11       ` Warner Losh

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=199710100127.SAA10165@dull.cobaltmicro.com \
    --to=ralf@cobaltmicro.com \
    --cc=adevries@engsoc.carleton.ca \
    --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