| To: | adevries@engsoc.carleton.ca (Alex deVries) |
|---|---|
| Subject: | Re: Arch specific initramdisk? |
| From: | Ralf Baechle <ralf@cobaltmicro.com> |
| Date: | Thu, 9 Oct 1997 18:27:02 -0700 (PDT) |
| Cc: | linux@cthulhu.engr.sgi.com |
| 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 |
| Sender: | owner-linux@cthulhu.engr.sgi.com |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Arch specific initramdisk?, Alex deVries |
|---|---|
| Next by Date: | Re: Majordomo results: (no subject), Maciek Dyczkowski |
| Previous by Thread: | Arch specific initramdisk?, Alex deVries |
| Next by Thread: | make zImage, and initrd..., Alex deVries |
| Indexes: | [Date] [Thread] [Top] [All Lists] |