public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: highpoint driver problem, 2.4.21-ac4
Date: Mon, 07 Jul 2003 19:54:07 +0200	[thread overview]
Message-ID: <3F09B3BF.8010108@gmx.at> (raw)
In-Reply-To: 20030706132507.240683d1.wilreichert@yahoo.com

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

Wil Reichert wrote:
 >> could you try the attachted patch, and report if this changes
 >> something?
 >
 >
 > Applied patch & rebuilt with hpt366 as a module.  No more oops, dmesg
 > prints the following:
 >
 > HPT372A: IDE controller at PCI slot 01:0b.0 HPT372A: chipset revision
 > 2 HPT372A: not 100% native mode: will probe irqs later hpt: HPT372N
 > detected, using 372N timing. FREQ: 126 PLL: 45 hpt: no known IDE
 > timings, disabling DMA. hpt: no known IDE timings, disabling DMA.
 >
 > It has 2 drives attached to it, neither seems to be found.
 >
 > Other things: the 2.5.xx seems to work ok and my board supports some
 > 'RAID 1.5' which seems to be nothing more than PR crap and some
 > firmware hacks.  Could that cause problems?
 >
 > Wil

ide_get_or_set_dma_base() is may be called via ide_setup_pci_device() 
when an ide controller module is loaded. however, 
ide_get_or_set_dma_base() is defined with __init and the function is 
called when its memory is already deallocated.

greetings,
Wilfried

[-- Attachment #2: linux-2.4.21-ac4-idedmafix.patch --]
[-- Type: text/plain, Size: 489 bytes --]

--- linux/drivers/ide/setup-pci.c.orig	2003-07-06 00:04:06.000000000 +0200
+++ linux/drivers/ide/setup-pci.c	2003-07-06 00:04:12.000000000 +0200
@@ -172,7 +172,7 @@ static int ide_setup_pci_baseregs (struc
  *	is already in DMA mode we check and enforce IDE simplex rules.
  */
 
-static unsigned long __init ide_get_or_set_dma_base (ide_hwif_t *hwif)
+static unsigned long ide_get_or_set_dma_base (ide_hwif_t *hwif)
 {
 	unsigned long	dma_base = 0;
 	struct pci_dev	*dev = hwif->pci_dev;

  parent reply	other threads:[~2003-07-07 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4V9E.47E.39@gated-at.bofh.it>
     [not found] ` <4V9E.47E.37@gated-at.bofh.it>
     [not found]   ` <4WyE.5oC.19@gated-at.bofh.it>
2003-07-03 19:21     ` highpoint driver problem, 2.4.21-ac4 Wilfried Weissmann
     [not found]       ` <20030703184427.3cb71051.wilreichert@yahoo.com>
2003-07-05 22:07         ` Wilfried Weissmann
     [not found]           ` <20030706132507.240683d1.wilreichert@yahoo.com>
2003-07-07 17:41             ` Wilfried Weissmann
2003-07-07 17:54             ` Wilfried Weissmann [this message]
     [not found] <4FHn.4MD.1@gated-at.bofh.it>
2003-07-02 18:50 ` Wilfried Weissmann
2003-07-02 20:36   ` Wil Reichert
2003-07-02  2:27 Wil Reichert

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=3F09B3BF.8010108@gmx.at \
    --to=wilfried.weissmann@gmx.at \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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