mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: aebr@win.tue.nl, axboe@suse.de
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: 2.5.37 oopses at boot in ide_toggle_bounce
Date: Mon, 30 Sep 2002 20:30:48 +0200 (MEST)	[thread overview]
Message-ID: <UTC200209301830.g8UIUmR20205.aeb@smtp.cwi.nl> (raw)

> Does it work in 2.4.20-pre-ac?


In 2.4.20-pre8 and in 2.5.33 the disks on a HPT366 are
detected without CONFIG_BLK_DEV_HPT366 being present.
Look at 2.4.20-pre8 in ide-pci.c and find an explicit list
ide_pci_chipsets that is walked by ide_scan_pcidev().

In 2.4.20-pre8ac2 and in 2.5.38 this HPT366 is not seen
without CONFIG_BLK_DEV_HPT366. The routine ide_scan_pcidev()
in setup-pci.c walks a list ide_pci_drivers that is
initially empty. HPT366 will only add itself when hpt366.c
is present and its hpt366_ide_init() invokes
ide_pci_register_driver().


So, all is well in both worlds, but one has to add
CONFIG_BLK_DEV_HPT366=y to .config now.
Long ago that would cause corruption, but so far
I have not seen any bad effects with recent kernels.

All the best - Andries

             reply	other threads:[~2002-09-30 18:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 18:30 Andries.Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-21 12:11 Andries.Brouwer
2002-09-22 19:54 ` Thunder from the hill
2002-09-23  7:41 ` Jens Axboe
2002-09-23 10:01   ` Andries Brouwer
2002-09-23 10:02     ` Jens Axboe
2002-09-23 10:04       ` Jens Axboe
2002-09-30  1:59       ` Andries Brouwer
2002-09-30 13:51         ` Jens Axboe

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=UTC200209301830.g8UIUmR20205.aeb@smtp.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=aebr@win.tue.nl \
    --cc=axboe@suse.de \
    --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®