From: Andrew Morton <akpm@osdl.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/14] kexec: i8259-sysfs.x86_64
Date: Sat, 21 Aug 2004 16:24:17 -0700 [thread overview]
Message-ID: <20040821162417.7bad0b08.akpm@osdl.org> (raw)
In-Reply-To: <m1zn4p66c2.fsf@ebiederm.dsl.xmission.com>
ebiederm@xmission.com (Eric W. Biederman) wrote:
>
> The i8259 does not yet have sysfs support on x86_64
umm, yes it does. It went into Linus's tree post 2.6.8.1.
I added the below make-it-compile patch. Please check it.
--- 25/arch/x86_64/kernel/i8259.c~kexec-x86_64-i8259-fixes 2004-08-21 16:22:54.833282048 -0700
+++ 25-akpm/arch/x86_64/kernel/i8259.c 2004-08-21 16:23:42.330061440 -0700
@@ -343,44 +343,6 @@ spurious_8259A_irq:
}
}
-static int i8259A_resume(struct sys_device *dev)
-{
- init_8259A(0);
- return 0;
-}
-
-static int i8259A_shutdown(struct sys_device *dev)
-{
- /* Put the i8259A into a quiescent state that
- * the kernel initialization code can get it
- * out of.
- */
- outb(0xff, 0x21); /* mask all of 8259A-1 */
- outb(0xff, 0xA1); /* mask all of 8259A-1 */
- return 0;
-}
-
-static struct sysdev_class i8259_sysdev_class = {
- set_kset_name("i8259"),
- .resume = i8259A_resume,
- .shutdown = i8259A_shutdown,
-};
-
-static struct sys_device device_i8259A = {
- .id = 0,
- .cls = &i8259_sysdev_class,
-};
-
-static int __init i8259A_init_sysfs(void)
-{
- int error = sysdev_class_register(&i8259_sysdev_class);
- if (!error)
- error = sysdev_register(&device_i8259A);
- return error;
-}
-
-device_initcall(i8259A_init_sysfs);
-
void init_8259A(int auto_eoi)
{
unsigned long flags;
_
next prev parent reply other threads:[~2004-08-21 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 17:57 Eric W. Biederman
2004-08-21 23:24 ` Andrew Morton [this message]
2004-08-23 4:22 ` Eric W. Biederman
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=20040821162417.7bad0b08.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ebiederm@xmission.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®