From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: FDC motor left on
Date: Fri, 3 Oct 2003 13:25:30 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0310031322430.499@chaos> (raw)
In linux-2.4.22 and earlier, if there is no FDC driver installed,
the FDC motor may continue to run after boot if the motor was
started as part of the BIOS boot sequence.
This patch turns OFF the motor once Linux gets control.
--- linux-2.4.22/arch/i386/boot/setup.S.orig Fri Aug 2 20:39:42 2002
+++ linux-2.4.22/arch/i386/boot/setup.S Fri Oct 3 11:50:43 2003
@@ -59,6 +59,8 @@
#define SIG1 0xAA55
#define SIG2 0x5A5A
+FDC_MOTOR = 0x3f2
+FDC_MOTON = 0x10
INITSEG = DEF_INITSEG # 0x9000, we move boot here, out of the way
SYSSEG = DEF_SYSSEG # 0x1000, system loaded at 0x10000 (65536).
SETUPSEG = DEF_SETUPSEG # 0x9020, this is the current segment
@@ -776,6 +778,12 @@
movb $0xFB, %al # mask all irq's but irq2 which
outb %al, $0x21 # is cascaded
+
+ movl $FDC_MOTOR, %edx # FDC motor control
+ inb %dx, %al # Get what's there
+ andb $~FDC_MOTON, %al # Reset motor bit
+ outb %al, %dx # Turn OFF motor
+
# Well, that certainly wasn't fun :-(. Hopefully it works, and we don't
# need no steenking BIOS anyway (except for the initial loading :-).
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next reply other threads:[~2003-10-03 17:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 17:25 Richard B. Johnson [this message]
2003-10-03 23:58 ` Dave Jones
2003-10-06 12:42 ` Richard B. Johnson
2003-10-06 12:50 ` Maciej W. Rozycki
2003-10-06 12:59 ` Mikael Pettersson
2003-10-06 13:58 ` Richard B. Johnson
2003-10-06 14:25 ` John Bradford
2003-10-06 15:09 ` Richard B. Johnson
2003-10-06 15:49 ` Maciej W. Rozycki
2003-10-06 16:17 ` Richard B. Johnson
2003-10-06 16:46 ` Maciej W. Rozycki
2003-10-06 16:06 ` John Bradford
2003-10-06 16:22 ` Richard B. Johnson
2003-10-06 16:41 ` John Bradford
2003-10-04 13:56 Mikael Pettersson
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=Pine.LNX.4.53.0310031322430.499@chaos \
--to=root@chaos.analogic.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®