public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] CMD649 driver in 2.5.5x
Date: Sat, 01 Feb 2003 05:34:08 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805792@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805780@msgid-missing>

David Mosberger wrote:
> No, the IDE subsystem is actually back to basically 2.4.xx with "some"
> changes.  So it shouldn't be too bad.

"some" is pretty loosely defined (ide-cd.c, 2.4.20 vs 2.5.59):
o substantial changes in the request_sense error handling,
o a new interrupt handler,
o some sort of new block merging code (blk_attempt_remerge()).
o just for ide-cd.c, "diff -up" output is 2988 lines

But primarily, I'm concerned about these type of changes:

                if (info->cmd = READ) {
-                       info->dma = !HWIF(drive)->dmaproc(ide_dma_read, drive);
+                       info->dma = !HWIF(drive)->ide_dma_read(drive);
                } else if (info->cmd = WRITE) {
-                       info->dma = !HWIF(drive)->dmaproc(ide_dma_write, drive);
+                       info->dma = !HWIF(drive)->ide_dma_write(drive);
                } else {
                        printk("ide-cd: DMA set, but not allowed\n");

It means someone had to rewrite cmd64x.c to match those changes.
I was looking for one of the key changes to ide-cd (start DMA after
sending the cmd) and it is in 2.5.59.

The new block merging code (if used for ide-disk.c) could introduce the
kind of data corruption bug you saw.

I'll review cmd64x.c next.

>   Grant> I'll take a whack at it if we can get 2.5.59 to boot/run from our
>   Grant> CVS linux-2.5 (which is merged to 2.5.59).
> 
> OK, that would be great.  Thanks!

Well, as of this evening, I've hung my rx2600 (disabled offending features)
several times and most recently mca'd my rx2600 4 times. I'm still am not
clueful what is causing the MCA.

Anyone have a .config they know boots on rx2600?
I noticed I'm using CONFIG_IA64_HP_ZX1 and not CONFIG_IA64_DIG.
I might switch to DIG for now.

grant


  parent reply	other threads:[~2003-02-01  5:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30 16:37 [Linux-ia64] CMD649 driver in 2.5.5x David Mosberger
2003-01-30 21:58 ` Grant Grundler
2003-01-30 23:40 ` David Mosberger
2003-02-01  5:34 ` Grant Grundler [this message]
2003-02-02  3:10 ` Matthew Wilcox
2003-02-04  0:53 ` Grant Grundler
2003-02-04 13:46 ` Matthew Wilcox

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=marc-linux-ia64-105590709805792@msgid-missing \
    --to=grundler@cup.hp.com \
    --cc=linux-ia64@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