archive mirror
 help / color / mirror / Atom feed
From: Marcelo Penna Guerra <>
To: Bartlomiej Zolnierkiewicz <>
Cc: Andre Hedrick <>, <>
Subject: Re: [PATCH] Merge the changes from siimage 2.4.22-pre9 to 2.6.0-test2
Date: Thu, 31 Jul 2003 16:32:56 -0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thursday 31 July 2003 12:25, Bartlomiej Zolnierkiewicz wrote:
> What do you mean by "a lot more stable than before"?

I mean it doesn't crash the system during intensive read/write operations. It 
has something to do with limiting the max bk per request to 7.5 (hwif-

> Can you separate your changes from forward-port?

They are really small changes. It's the one I mentioned on the first e-mail 
and this one, that was suggested by Andre Hedrick on another post:

+		drive->id->hw_config |= 0x6000;
		if(strstr(drive->id->model, "Maxtor"))
			return 3;
		return 4;

> Are you aware of side effect?
> [ Disabling DMA on ATAPI devices on SiI680. ]
> Please consult this change with Alan :-).

No, I'm not. Sorry. I'm look for more information. But dma is working with my 
SiI3112A, everything is stable, so maybe it should be enabled by default for 
this chipset.

Also, there's a change missing in this patch. The PCI id for SiI1210SA is 
missing in 2.6.x.

#define PCI_DEVICE_ID_SII_680      0x0680 
+#define PCI_DEVICE_ID_SII_1210SA   0x0240 
#define PCI_DEVICE_ID_SII_3112      0x3112

Anyway, thank you for taking a look at this.

Marcelo Penna Guerra

  reply	other threads:[~2003-07-31 17:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 17:49 [PATCH] Merge the changes from siimage 2.4.22-pre9 to 2.6.0-test2 Marcelo Penna Guerra
2003-07-31 15:25 ` Bartlomiej Zolnierkiewicz
2003-07-31 19:32   ` Marcelo Penna Guerra [this message]
2003-07-31 17:19     ` Alan Cox
2003-07-31 17:24     ` Bartlomiej Zolnierkiewicz
2003-08-02  8:29   ` Andre Hedrick
2003-07-31 15:58 ` Alan Cox
2003-08-07  9:49 CASINO_E
2003-08-07 12:29 ` Alan Cox
2003-08-07 13:35   ` Bartlomiej Zolnierkiewicz
2003-08-07 15:53     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).