mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Wilck <Martin.Wilck@Fujitsu-Siemens.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Gonzalo Servat <gonzalo@unixpac.com.au>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: ServerWorks OSB4 in impossible state
Date: 22 Aug 2002 14:02:35 +0200	[thread overview]
Message-ID: <1030017756.9866.74.camel@biker.pdb.fsc.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10208220143440.11626-100000@master.linux-ide.org>

Am Don, 2002-08-22 um 10.51 schrieb Andre Hedrick:

> The problem is we need a special DMA engine for this broken puppy.

You certainly have much more insight into the problem than I. 
I wonder if (something like) the simple patch I submitted before can
be a temporary solution nevertheless. Please correct me if one of the
following statements is wrong:

1) The "4 byte shift" issue does not affect the CSB5 series.
2) The tested condition inb(dma_base+0x02)&1 is valid if the
   device doing the DMA reported an error status. Only if the
   device reports success is there an indication of the "4 byte shift".
3) The "4 byte shift" problem matters not for read-only devices like
   CD-ROMS; at least it is no reason to stall the computer if it occurs
   because data corruption is not an issue.

If these assertions are true, the patch I sent will at least prevent
people's machines from stalling unnecessarily. Even if one ore more are
false, the remaining correct condition test(s) will narrow the set
of machines that are stalled unnecessarily.

> 508 + 4 is okay but 510 + 2 is not.
> 
> Now I have to remember why :-/

You sure have to go for the right solution.
But if my patch was applied, ServerWorks chip sets would cause less
grief to people until you have figured it out.

> Yeah I expect to take heat for this one from ServerWorks and it may cost
> me later, but nobody else has got the guts to press the issue for the
> correct solution.

Let me know if we can help. I have no personal contacts to ServerWorks,
but we are a large customer of them and may be able to exert some
additional pressure. The current situation (IDE DMA must be disabled)
is hardly acceptable for us anyway.

Martin

-- 
Martin Wilck                Phone: +49 5251 8 15113
Fujitsu Siemens Computers   Fax:   +49 5251 8 20409
Heinz-Nixdorf-Ring 1	    mailto:Martin.Wilck@Fujitsu-Siemens.com
D-33106 Paderborn           http://www.fujitsu-siemens.com/primergy






  reply	other threads:[~2002-08-22 11:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1030002761.32380.27.camel@pluto.unixpac.com.au>
2002-08-22  8:35 ` Martin Wilck
2002-08-22  8:51   ` Andre Hedrick
2002-08-22 12:02     ` Martin Wilck [this message]
2002-08-22 16:45       ` Tomas Szepe
2002-08-22 17:48         ` Andre Hedrick
2002-08-22 17:59         ` Alan Cox
2002-08-22 18:14           ` Tomas Szepe
2002-08-22 17:58       ` Alan Cox
2002-08-22 18:58         ` Martin Wilck
     [not found] <20020613112932.C2B8C10A1B@mail.medav.de>
2002-06-13 12:52 ` Serverworks " Martin Wilck
2002-06-10 15:52 Martin Wilck
2002-06-10 16:41 ` Daniela Engert
2002-06-11  7:22   ` Martin Wilck
2002-06-11  7:45     ` Daniela Engert
2002-06-11  8:37       ` Martin Wilck
2002-06-11 11:25       ` Martin Wilck
2002-06-11 21:27         ` Chris Wedgwood
2002-06-12  7:24           ` Martin Wilck
2002-06-13 11:50         ` Daniela Engert
2002-06-13 11:59           ` Martin Wilck
2002-06-13 12:04             ` Daniela Engert
2002-06-13 18:27               ` rico-linux-kernel
2002-06-12  8:58 ` Alan Cox
2002-06-12  8:47   ` Martin Wilck
2002-06-12  9:14     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-06-03 17:40 Steven Timm
2002-06-04  0:29 ` Alan Cox
2002-06-03 18:11   ` kwijibo

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=1030017756.9866.74.camel@biker.pdb.fsc.net \
    --to=martin.wilck@fujitsu-siemens.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=gonzalo@unixpac.com.au \
    --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®