From: Felix Seeger <felix.seeger@gmx.de>
To: Len Brown <len.brown@intel.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.3-rc4 (nforce2)
Date: Tue, 17 Feb 2004 07:49:48 +0100 [thread overview]
Message-ID: <200402170749.48575.felix.seeger@gmx.de> (raw)
In-Reply-To: <1076999506.2510.36.camel@dhcppc4>
On Tuesday 17 February 2004 07:31, Len Brown wrote:
> > Should NForce2 boards also work without patches and with acpi/apic ?
> > I saw a change in rc3.
>
> Some will, some will not. Note that Maciej's patch didn't address the
> nforce2 timer configuration issue, which I believe requires a
> platform-specific nforce2 patch.
>
> > It just hangs again, so I switched back to my patched kernel.
> > But of course this could be another problem, kernel 2.6.2-rc1 is
> > running very
> > stable here with the apictack-rd and the ioapic-rd patches.
>
> Dunno what those are, but if you still require ACPI-related patches,
> please let me know.
>From the nforce2-apictack-rd-2.6.0.patch:
/*
+ * Athlon nforce2 R.D.
+ * preset timer ack mode if desired
+ * e.g. static int apic_timerack = 2;
>From the nforce2-ioapic-rd-2.6.0.patch
+#if defined(CONFIG_ACPI_BOOT) && defined(CONFIG_X86_UP_IOAPIC)
+ /* for nforce2 try vector 0 on pin0
+ * Note 8259a is already masked, also by default
+ * the io_apic_set_pci_routing call disables the 8259 irq 0
+ * so we must be connected directly to the 8254 timer if this works
+ * Note2: this violates the above comment re Subtle but works!
+ */
I think I will need more patches, but I will test it today.
> thanks,
> -Len
Felix
prev parent reply other threads:[~2004-02-17 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F262D@hdsmsx402.hd.intel.com>
2004-02-17 6:31 ` Len Brown
2004-02-17 6:49 ` Felix Seeger [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=200402170749.48575.felix.seeger@gmx.de \
--to=felix.seeger@gmx.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®