All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Longhaul - There are limits
Date: Thu, 6 Jul 2006 15:46:46 -0400	[thread overview]
Message-ID: <20060706194646.GN13168@redhat.com> (raw)
In-Reply-To: <44AA8E61.7030807@interia.pl>

On Tue, Jul 04, 2006 at 05:50:57PM +0200, Rafał Bilski wrote:
 > Hello!
 > 
 > There is no need to worry about local APIC.
 > There is need to worry about I/O APIC, because I/O APIC 
 > is replacing good old 8259. Acording to Nehemiah datasheet VIA is 
 > using 3-wire bus to connect local APIC to I/O APIC.
 > 
 > "[...] When IA32_APIC_BASE[11] is set to 0, processor APICs based on the 3-wire APIC
 >  bus cannot be generally re-enabled until a system hardware reset. The 3-wire bus
 >  looses track of arbitration that would be necessary for complete re-enabling. Certain
 >  (local) APIC functionality can be enabled. [...]"
 > 
 > So we must set disable bit for each interrupt in I/O APIC registers. 
 > Same situation as for PIC - we must poke registers direcly.
 > How to do this? I don't know. So at the moment it is better 
 > to fail.

Ok, I'll merge this up. We can revisit the APIC stuff later.

Thanks,

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-07-06 19:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 15:50 [PATCH] Longhaul - There are limits Rafał Bilski
2006-07-06 19:46 ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-03  5:18 Rafał Bilski
2006-07-03 14:11 ` Dave Jones
2006-07-03 16:00   ` Rafał Bilski
2006-07-03 16:52     ` Dave Jones
2006-07-03 17:39       ` Rafał Bilski
2006-07-03 18:37       ` Rafał Bilski
2006-07-03 19:14       ` Rafał Bilski

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=20060706194646.GN13168@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=rafalbilski@interia.pl \
    /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.