From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Missing files in to-linus-2.5 BK tree; build problems
Date: Thu, 30 May 2002 05:49:57 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905619@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905608@msgid-missing>
>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:
David> Note that the to-linus-2.5 tree is intended for Linus only.
David> It's not complete in any fashion (well, some day it will
David> be...). I am working on the latest 2.5 patch, but keep getting
David> delayed (and of course Linus keeps cranking out new
David> versions...).
Doesn't he just!
It seems to me that there are several categories of things in the
patches you've been cranking out.
1. Support for devices not in the main tree (e.g., the i460GX, the
qlogic 2200, etc)
2. Extra features (like the early printk support) that in their
current form are too ugly to go into the mainline, but are really
useful for IA64.
3. Changes in architecture specific code for
-- matching changes in mainline code (e.g., the scatterlist change,
the TLB shootdown change, etc)
-- enhancements to IA64-specific code (like the new perfmon support)
-- New subarchitectures (e.g., SN1, ZX1)
4. Changes in mainline to fix things that break on IA64.
(e.g., ACPI)
It seems to me that it *should* be possible to get all except category
2 synced into the mainline code. One of the things I've been trying
to do occasionally is to compile a ia64-patched kernel on different
architectures to see what breaks. Surprisingly little does.
BTW, I upgraded the BIOS on lemon.gelato.unsw.edu.au, the machine that
had the time haring off into the future. It seems OK now.
One of the BIOS notes said that the AGP aperture for the I460GX was
fixed not to overlap the PCI space. Does this mean that some of the
hacks in the DRM are no longer necessary?
--
Peter C peterc@gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories, all almost the same.
next prev parent reply other threads:[~2002-05-30 5:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 3:56 [Linux-ia64] Missing files in to-linus-2.5 BK tree; build problems Peter Chubb
2002-05-29 8:05 ` [Linux-ia64] Missing files in to-linus-2.5 BK tree; build Andreas Schwab
2002-05-29 19:29 ` [Linux-ia64] Missing files in to-linus-2.5 BK tree; build problems Grant Grundler
2002-05-30 4:01 ` David Mosberger
2002-05-30 4:56 ` Peter Chubb
2002-05-30 5:49 ` Peter Chubb [this message]
2002-05-30 5:58 ` David Mosberger
2002-05-31 1:00 ` Grant Grundler
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-105590701905619@msgid-missing \
--to=peter@chubb.wattle.id.au \
--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