From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] updated kernel diff on kernel.org
Date: Mon, 17 Apr 2000 15:44:23 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205017@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205014@msgid-missing>
David-
(Sorry for the delay in getting back to you, I got stuck on some
other problems for a while.)
From what I can tell the IA32 support is working fine with this
patch.
On Mon, Apr 10, 2000 at 11:22:50PM -0700, David Mosberger wrote:
> OK, the latest kernel diff is now available as
> linux-2.3.51-ia64-000410.diff.gz from:
>
> ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/
>
> This is basically Friday's patch with the following additions:
>
> - Don's IA-32 updates (Don, please take a look at this
> diff as there were a few changes: I put the trap handler
> in ia32/ia32_traps.c and made some other small changes;
> e.g., send SIGTRAP via send_sig_info instead of
> force_sig_info).
>
> - Fix for SMP problem that Chuck found in the softirq handling
> code (Chuck, you may want to review this as I implemented
> this a bit differently and have not had a chance to test it
> on SMP).
>
> - The IA64_UL() change that fixes Jes's grief with the
> FPSR_DEFAULT macro
>
> That should be it. The irq debug printk's are still there, I'm
> afraid. They'll stay there as long as the IDE secondary channel
> continues to disfunction.
>
> Note: I suspect there is another signal-delivery related bug as
> building gcc with profiling enabled still fails for me. Stay tuned...
>
> --david
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838
prev parent reply other threads:[~2000-04-17 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 6:22 [Linux-ia64] updated kernel diff on kernel.org David Mosberger
2000-04-17 15:44 ` Don Dugger [this message]
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-105590678205017@msgid-missing \
--to=n0ano@valinux.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