public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Nekrasov <andy@spylog.ru>
To: Peter Osterlund <petero2@telia.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	hch@infradead.org
Subject: Re: I/O-APIC not enabled in 2.4.19-pre8 on UP machines
Date: Mon, 20 May 2002 11:44:57 +0400	[thread overview]
Message-ID: <20020520074457.GA18329@spylog.ru> (raw)
In-Reply-To: <m2elg88k9g.fsf@ppro.localdomain>

Hello Peter Osterlund,


 Many thanks. The problem with AIC drivers has disappeared. An Intel appeared not
 and, L440GX AIC again works on one processor.  



Once you wrote about "I/O-APIC not enabled in 2.4.19-pre8 on UP machines":
> It looks like I/O-APIC setup was accidentally disabled in 2.4.19-pre7
> for UP machines.
> 
> Here is a patch to fix it:
> 
> --- linux/arch/i386/kernel/io_apic.c.orig	Sun May 19 12:58:40 2002
> +++ linux/arch/i386/kernel/io_apic.c	Sun May 19 12:58:24 2002
> @@ -191,11 +191,7 @@
>  #define MAX_PIRQS 8
>  int pirq_entries [MAX_PIRQS];
>  int pirqs_enabled;
> -#ifdef CONFIG_X86_UP_APIC
> -int skip_ioapic_setup=1;
> -#else
> -int skip_ioapic_setup=0;
> -#endif
> +int skip_ioapic_setup;
>  
>  static int __init noioapic_setup(char *str)
>  {
> 
> -- 
> Peter Osterlund - petero2@telia.com
> http://w1.894.telia.com/~u89404340
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
bye.
Andrey Nekrasov, SpyLOG.

  reply	other threads:[~2002-05-20  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-19 11:11 I/O-APIC not enabled in 2.4.19-pre8 on UP machines Peter Osterlund
2002-05-20  7:44 ` Andrey Nekrasov [this message]
2002-05-20 22:27 ` Marcelo Tosatti

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=20020520074457.GA18329@spylog.ru \
    --to=andy@spylog.ru \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=petero2@telia.com \
    /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