From: Nathan Bryant <nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
To: "Georg C. F. Greve" <greve-mXXj517/zsQ@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: acpi-20040715: functional regression on ASUS M2N
Date: Mon, 02 Aug 2004 12:45:16 -0400 [thread overview]
Message-ID: <410E6F9C.2040904@optonline.net> (raw)
> I added your suggested patch to
>
> arch/i386/kernel/i8259.c
>
> and recompiled.
>
> Problem persists, no difference I could tell.
I don't know why the patch masks out the reserved interrupts. None of
the other code that sets ELCR is masking out those bits, and it all
works fine. Possibly some chipsets use different edge/level behavior for
these, and the save code is forcing them back to edge. Does the problem
persist if you go into arch/i386/kernel/i8259.c and change:
static void save_ELCR(char *trigger)
{
/* IRQ 0,1,2,8,13 are marked as reserved */
trigger[0] = inb(0x4d0) & 0xF8;
trigger[1] = inb(0x4d1) & 0xDE;
}
to:
static void save_ELCR(char *trigger)
{
/* IRQ 0,1,2,8,13 are marked as reserved */
trigger[0] = inb(0x4d0);
trigger[1] = inb(0x4d1);
}
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next reply other threads:[~2004-08-02 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 16:45 Nathan Bryant [this message]
[not found] ` <410E6F9C.2040904-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-04 0:23 ` acpi-20040715: functional regression on ASUS M2N Georg C. F. Greve
-- strict thread matches above, loose matches on Subject: below --
2004-08-31 8:45 Li, Shaohua
[not found] ` <B44D37711ED29844BEA67908EAF36F03AC6ACF-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-31 13:38 ` Georg C. F. Greve
[not found] ` <m3zn4bbf6x.fsf-eMhNhoSsuh6q92djB/mqZw@public.gmane.org>
2004-09-01 15:16 ` Georg C. F. Greve
2004-08-09 8:10 Li, Shaohua
2004-08-05 18:49 Nathan Bryant
[not found] ` <4112814C.2070808-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-06 11:21 ` Georg C. F. Greve
[not found] ` <m37jsc3424.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-08-06 13:36 ` Nathan Bryant
[not found] ` <41138944.3060309-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-06 16:54 ` Georg C. F. Greve
[not found] ` <m3u0vgurzy.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-08-06 17:07 ` Nathan Bryant
[not found] ` <4113BAD5.1030909-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-06 20:50 ` Georg C. F. Greve
2004-08-31 8:15 ` Georg C. F. Greve
2004-08-06 15:23 ` Matthew Garrett
2004-08-06 15:50 ` Nathan Bryant
2004-08-06 16:38 ` Nate Lawson
2004-08-06 19:32 ` Nathan Bryant
2004-07-27 12:24 Li, Shaohua
[not found] ` <B44D37711ED29844BEA67908EAF36F036BCD7C-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-07-27 13:42 ` Georg C. F. Greve
2004-07-19 23:31 Georg C. F. Greve
[not found] ` <m3d62rzi9a.fsf-eMhNhoSsuh6q92djB/mqZw@public.gmane.org>
2004-07-20 19:03 ` Matthew Garrett
[not found] ` <1090350197.4828.5.camel-myFlNLNQP+Q@public.gmane.org>
2004-07-21 8:17 ` Georg C. F. Greve
[not found] ` <m3acxthizw.fsf-eMhNhoSsuh6q92djB/mqZw@public.gmane.org>
2004-07-27 11:14 ` Georg C. F. Greve
[not found] ` <m3oem1u2gg.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-07-27 11:24 ` Matthew Garrett
[not found] ` <1090927462.4412.26.camel-myFlNLNQP+Q@public.gmane.org>
2004-07-27 13:40 ` Georg C. F. Greve
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=410E6F9C.2040904@optonline.net \
--to=nbryant-p32f3xycuykqczcgjluoxw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=greve-mXXj517/zsQ@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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