From: Mikael Pettersson <mikpe@csd.uu.se>
To: davej@redhat.com, root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: FDC motor left on
Date: Sat, 4 Oct 2003 15:56:47 +0200 (MEST) [thread overview]
Message-ID: <200310041356.h94Dul7T009782@harpo.it.uu.se> (raw)
On Sat, 4 Oct 2003 00:58:02 +0100, Dave Jones wrote:
>On Fri, Oct 03, 2003 at 01:25:30PM -0400, Richard B. Johnson wrote:
> > 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 @@
>
>Does this mean the 'kill_motor' function in bootsect.S isn't doing
>what it should be? If so, maybe that needs fixing instead of turning
>it off in two places ?
It's my understanding that bootsect.S:kill_motor is part of
the kernel's old builtin boot-from-floppy code, and that it
doesn't run when some other boot loader loaded the kernel.
(And it shouldn't have to.)
The workaround if you have a buggy BIOS or external loader
is to configure BLK_DEV_FD as a built-in. I do that anyway
for other reasons (to avoid an unresolved module autoloading
failure in some cases; it's in RH bugzilla somewhere).
/Mikael
next reply other threads:[~2003-10-04 13:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 13:56 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-03 17:25 Richard B. Johnson
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
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=200310041356.h94Dul7T009782@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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®