public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: milstone reached: ia64 linux builds out of Linus' tree
Date: Mon, 04 Aug 2003 19:53:26 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106002696711502@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106001867501939@msgid-missing>

This code is taken from 2.4 kernel, which is enabled for all ia64
machines. The only difference is

        if (has_8259 && irq < 16)
                return isa_irq_to_vector(irq);

	return gsi_to_vector(irq);

instead of just

	return gsi_to_vector(irq);

I think bigsur is one of those uses 8259 and ISA. I don't believe any
new ia64 machines do that.

H.J.
---
On Mon, Aug 04, 2003 at 12:07:19PM -0700, David Mosberger wrote:
> Can someone look into/explain why this patch is needed for Big Sur?
> Either the old code is wrong for other machines, too, or the old code
> is broken and we just don't exercise it on the other ia64 machines?
> 
> 	--david
> 
> >>>>> On Mon, 4 Aug 2003 11:10:33 -0700, "H. J. Lu" <hjl@lucon.org> said:
> 
>   >> I just tried the latest on my big sur, and though I think modules work
>   >> (at least they build for other machines), big sur is broken because
>   >> non-ACPI based PCI enumeration has been removed from the tree.
> 
>   HJ> Can you try this patch for bigsur?
> 
> 
>   HJ> H.J.
>   HJ> ---
>   HJ> --- linux/drivers/acpi/osl.c.acpi	Mon Jul 28 11:41:53 2003
>   HJ> +++ linux/drivers/acpi/osl.c	Mon Jul 28 15:12:44 2003
>   HJ> @@ -250,7 +250,12 @@ acpi_os_install_interrupt_handler(u32 ir
>   HJ> irq = acpi_fadt.sci_int;
>  
>   HJ> #ifdef CONFIG_IA64
>   HJ> -	irq = gsi_to_vector(irq);
>   HJ> +	irq = acpi_irq_to_vector (irq);
>   HJ> +	if (irq < 0) {
>   HJ> +		printk(KERN_ERR PREFIX "SCI (IRQ%d/%d) not registerd\n",
>   HJ> +		       irq, acpi_fadt.sci_int);
>   HJ> +		return AE_OK;
>   HJ> +	}
>   HJ> #endif
>   HJ> acpi_irq_irq = irq;
>   HJ> acpi_irq_handler = handler;

  parent reply	other threads:[~2003-08-04 19:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 17:37 milstone reached: ia64 linux builds out of Linus' tree David Mosberger
2003-08-04 17:53 ` H. J. Lu
2003-08-04 18:00 ` Jesse Barnes
2003-08-04 18:10 ` H. J. Lu
2003-08-04 18:21 ` David Mosberger
2003-08-04 18:27 ` David Mosberger
2003-08-04 18:31 ` David S. Miller
2003-08-04 18:40 ` David Mosberger
2003-08-04 18:41 ` Jes Sorensen
2003-08-04 18:45 ` David S. Miller
2003-08-04 18:49 ` Jesse Barnes
2003-08-04 18:52 ` Jesse Barnes
2003-08-04 19:07 ` David Mosberger
2003-08-04 19:07 ` Alan Cox
2003-08-04 19:17 ` David S. Miller
2003-08-04 19:18 ` Andreas Schwab
2003-08-04 19:53 ` H. J. Lu [this message]
2003-08-04 23:06 ` Peter Chubb
2003-08-04 23:20 ` Jesse Barnes
2003-08-04 23:35 ` David Mosberger
2003-08-04 23:39 ` David Mosberger
2003-08-13  0:07 ` Ian Wienand
2003-09-10  0:53 ` Ian Wienand
2003-09-10  1:57 ` David Mosberger
  -- strict thread matches above, loose matches on Subject: below --
2004-03-30  0:30 Ian Wienand
2004-03-30  0:37 ` Duraid Madina
2004-03-30  1:03 ` Peter Chubb
2004-03-30  1:16 ` Jesse Barnes
2004-03-30  1:28 ` Al Stone
2004-03-30  1:57 ` Duraid Madina
2004-03-30  3:59 ` Al Stone
2004-03-30  7:51 ` Siddha, Suresh B
2004-03-30 17:39 ` Jesse Barnes

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-106002696711502@msgid-missing \
    --to=hjl@lucon.org \
    --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