From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: 2.5.75 out
Date: Thu, 10 Jul 2003 23:54:43 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105788133314878@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105788013113852@msgid-missing>
>>>>> On Thu, 10 Jul 2003 16:45:52 -0700, "Luck, Tony" <tony.luck@intel.com> said:
>> There is good and bad news: the bad news is that 2.5.75 doesn't work
>> out-of-the-box on ia64. The good news it _does_ compile. The thing
>> that keeps it from working are a few (late) per-CPU related changes.
>> Hopefully, we can iron those out before pre-2.6 comes out so that it
>> will build _and_ work. Probably wishful thinking though. There
>> always seems to be that last-minute patch that breaks things...
Tony> Compiles, but doesn't link for me ... Linus's tree is missing
Tony> this patch:
Ah, I have the AGP stuff configured as modules so I didn't notice
(didn't build the modules).
Tony> diff ~/BK/david2.5/drivers/char/agp/i460-agp.c drivers/char/agp/i460-agp.c
Tony> 611c611
>> .remove = agp_intel_i460_remove,
Tony> ---
Tony> < .remove = __exit_p(agp_intel_i460_remove),
Tony> -
Tony> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
Can you submit this directly to Dave Jones? Have you actually tried i460
AGP recently? Does it still work?
--david
next prev parent reply other threads:[~2003-07-10 23:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 23:34 2.5.75 out David Mosberger
2003-07-10 23:45 ` Luck, Tony
2003-07-10 23:54 ` David Mosberger [this message]
2003-07-11 0:05 ` Luck, Tony
2003-07-11 2:53 ` Peter Chubb
2003-07-11 7:30 ` Andrew Morton
2003-07-11 17:58 ` Chen, Kenneth W
2003-07-11 18:30 ` David Mosberger
2003-07-16 3:16 ` Yu, Luming
2003-07-16 4:29 ` David Mosberger
2003-07-16 11:13 ` Matthew Wilcox
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-105788133314878@msgid-missing \
--to=davidm@napali.hpl.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.