mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Nerijus Baliunas <nerijus@users.sourceforge.net>
Cc: "jim@rubylane.com" <jim@rubylane.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Re[2]: Update on Promise 100TX2 + Serverworks IDE issues -- 2.2.20
Date: Thu, 4 Apr 2002 02:03:31 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10204040202220.7246-100000@master.linux-ide.org> (raw)
In-Reply-To: <ISPFE11vdnznMEmPzhz00000d07@mail.takas.lt>


I need to find time to publish and break down a new 352K patch for
2.4.19-pre4 that covers this issue also.

Andre Hedrick
LAD Storage Consulting Group

On Thu, 4 Apr 2002, Nerijus Baliunas wrote:

> On Tue, 2 Apr 2002 18:58:20 -0800 (PST) "jim@rubylane.com" <jim@rubylane.com> wrote:
> 
> j> This board does claim to support UDMA33 and Linux says the MB IDE
> j> ports are in UDMA33 mode.  Works fine in just PIO mode.  Slower, but
> j> at least it doesn't trash drives.
> 
> j> This board says:
> j> 
> j> ServerWorks OSB4: IDE controller on PCI bus 00 dev 79
> j> ServerWorks OSB4: chipset revision 0
> 
> IIRC downgrading DMA to MDMA2 should help.
> 
> Regards,
> Nerijus
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2002-04-04 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 23:38 jim
2002-04-03  0:48 ` Trent Piepho
2002-04-03  1:18   ` Alan Cox
2002-04-03  2:08     ` Jeff Nguyen
2002-04-03  2:58       ` Alan Cox
2002-04-03  2:58         ` jim
2002-04-04  1:32           ` Re[2]: " Nerijus Baliunas
2002-04-04 10:03             ` Andre Hedrick [this message]
2002-04-03  3:10   ` jim

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=Pine.LNX.4.10.10204040202220.7246-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=jim@rubylane.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nerijus@users.sourceforge.net \
    /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®