From: Jan Rekorajski <baggins@sith.mimuw.edu.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, andre@linux-ide.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.4.21(-ac) ide-disk and hpt366 modules problem
Date: Sun, 29 Jun 2003 19:04:09 +0200 [thread overview]
Message-ID: <20030629190409.A22124@sith.mimuw.edu.pl> (raw)
Hi,
There is a chicken-egg problem between ide-disk and hpt366 modules.
ide-disk should be loaded after chipset driver to detect what disks are
connected, but hpt366 needs ide-disk loaded because of 372N tricks and
__ide_do_rw_disk symbol.
I used the following hack to avoid the problem, but I think maybe
something better is needed.
--- linux-2.4.21/drivers/ide/ide-disk.c~ Fri Jun 13 16:51:33 2003
+++ linux-2.4.21/drivers/ide/ide-disk.c Sun Jun 29 18:48:33 2003
@@ -698,12 +698,9 @@
{
ide_hwif_t *hwif = HWIF(drive);
if (hwif->rw_disk)
- return hwif->rw_disk(drive, rq, block);
- else
- return __ide_do_rw_disk(drive, rq, block);
+ hwif->rw_disk(drive, rq, block);
+ return __ide_do_rw_disk(drive, rq, block);
}
-
-EXPORT_SYMBOL_GPL(__ide_do_rw_disk);
static int idedisk_open (struct inode *inode, struct file *filp, ide_drive_t *drive)
{
--- linux-2.4.21/drivers/ide/pci/hpt366.c~ Sun Jun 29 15:09:43 2003
+++ linux-2.4.21/drivers/ide/pci/hpt366.c Sun Jun 29 18:50:33 2003
@@ -742,7 +742,7 @@
hpt372n_set_clock(drive, wantclock);
HWIF(drive)->config_data = wantclock;
}
- return __ide_do_rw_disk(drive, rq, block);
+ return ide_started;
}
/*
Jan
--
Jan Rękorajski | ALL SUSPECTS ARE GUILTY. PERIOD!
baggins<at>mimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, MANIAC | -- TROOPS by Kevin Rubio
next reply other threads:[~2003-06-29 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 17:04 Jan Rekorajski [this message]
2003-06-29 20:36 ` Alan Cox
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=20030629190409.A22124@sith.mimuw.edu.pl \
--to=baggins@sith.mimuw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--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®