mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Pam <xanni@glasswings.com.au>
To: andre@linux-ide.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Initialisation bug in IDE patch
Date: Wed, 22 May 2002 15:55:15 +1000	[thread overview]
Message-ID: <20020522155515.F2437@kira.glasswings.com.au> (raw)
In-Reply-To: <20020522151510.A2437@kira.glasswings.com.au>

On Wed, May 22, 2002 at 03:15:10PM +1000, Andrew Pam wrote:
> In the latest available kernel 2.2 IDE patch "ide-2.2.20.01102002.patch"
> there is a bug that prevents ide_setup in drivers/block/ide.c
> from accepting kernel parameters selecting special IDE hardware.
> 
> The ide_init_default_hwifs() function in include/asm-*/ide.h fails to
> initialise the "hw_regs_t hw" variable, thus leaving uninitialised data
> in some fields.  Specifically, the "chipset" field is uninitialised which
> causes the "if (hwif->chipset != ide_unknown)" test in drivers/block/ide.c
> to always fail with the error message " -- BAD OPTION".

This bug also appears to be present in the mainline 2.4 kernel IDE code.
I haven't checked the 2.5 code yet.

Regards,
	Andrew Pam
-- 
mailto:xanni@xanadu.net                         Andrew Pam
http://www.xanadu.com.au/                       Chief Scientist, Xanadu
http://www.glasswings.com.au/                   Technology Manager, Glass Wings
http://www.sericyb.com.au/                      Manager, Serious Cybernetics
http://two-cents-worth.com/?105347&EG		Donate two cents to our work!
P.O. Box 477, Blackburn VIC 3130 Australia	Phone +61 401 258 915

  reply	other threads:[~2002-05-22  5:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22  5:15 Andrew Pam
2002-05-22  5:55 ` Andrew Pam [this message]
2002-05-22  6:00   ` Andre Hedrick
2002-05-22  6:11     ` Andrew Pam
2002-05-22  6:18       ` Andre Hedrick
2002-05-22  6:34         ` Andrew Pam
2002-05-22  6:57         ` Andrew Pam
2002-05-22  6:59           ` Andre Hedrick
2002-05-22  7:05             ` Andrew Pam

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=20020522155515.F2437@kira.glasswings.com.au \
    --to=xanni@glasswings.com.au \
    --cc=andre@linux-ide.org \
    --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®