From: John Hesterberg <jh@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] SGI SN patches
Date: Thu, 07 Feb 2002 20:37:28 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698806021@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
Attached are patches that allow building and booting SGI SNIA systems.
Most people probably don't care, as SGI SNIA systems are not
available outside of SGI.
patch-sn-2.4.17-3 is limited to SN-specific files. This has been
sent to David, and should show up in the next ia64 patch.
patch-snconfig-2.4.17.bz2 is a defconfig-sn1 file to use with the
above patch-sn-2.4.17-3. This has also been sent to David, and
should show up in a new arch/ia64/configs/ directory (but that's not
the path in this patch).
patch-sgi-2.4.17 includes some of our changes to other files that
are not SN-specific. For various reasons, these changes either
haven't yet been submitted to the various open source maintainers,
or haven't been accepted. We're working on that...
The following builds for SNIA, but doesn't boot:
2.4.17 + ia64 patch
+ patch-sn-2.4.17-3
+ patch-snconfig-2.4.17
+ discontig-2.4.17(sans SN files)
The following builds and boots on SNIA.
2.4.17 + ia64 patch
+ patch-sn-2.4.17-3
+ discontig-2.4.17(sans SN files)
+ patch-sgi-2.4.17
Note that in this second case you don't need patch-snconfig-2.4.17,
an updated defconfig file is included in patch-sgi-2.4.17.
John Hesterberg
jh@sgi.com
[-- Attachment #2: patch-sn-2.4.17-3.bz2 --]
[-- Type: application/x-bzip2, Size: 52290 bytes --]
[-- Attachment #3: patch-snconfig-2.4.17.bz2 --]
[-- Type: application/x-bzip2, Size: 3940 bytes --]
[-- Attachment #4: patch-sgi-2.4.17.bz2 --]
[-- Type: application/x-bzip2, Size: 35645 bytes --]
reply other threads:[~2002-02-07 20:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590698806021@msgid-missing \
--to=jh@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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