All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Boergens <kevin@boergens.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: cs5530_set_xfer_mode
Date: Sat, 10 Jan 2004 09:02:53 +0100	[thread overview]
Message-ID: <3FFFB1AD.5050307@boergens.de> (raw)

Hello!

Maybe this is a question to stupid for this list,
but I asked for it in de.comp.os.unix.linux.hardware
<bt8tln$4htn0$1@ID-213387.news.uni-berlin.de> and on the Debian user
mailing list, and although many people tried, nobody could help me.

I have a server with a National Semiconductor CS5530 southbridge
(http://www.national.com/pf/CS/CS5530.html) and after booting it only
worked in MDMA2. I tried to force it with hdparm -d1X66 but that caused
only nasty messages on syslog, like:

***********************************************************************
Jan  5 16:46:14 server kernel: hda: timeout waiting for DMA
Jan  5 16:46:14 server kernel: ide_dmaproc: chipset supported
ide_dma_timeout fu
nc only: 14
Jan  5 16:46:14 server kernel: hda: status error: status=0x58 {
DriveReady SeekC
omplete DataRequest }
Jan  5 16:46:14 server kernel: hda: drive not ready for command
**********************************************************************

I tried this with the Debian kernel images 2.4.18-bf2.4 and
2.2.20-idepci and with several disks, all the same.



I would have given up hope already, if I had not found out that the
S.u.S.E. 7.3 kernel 2.4.10-4GB has no problem with this chipset at all.
While booting, the kernel says:

hda WDC[...]
ide0 at 0x[...] on irq14
hda: cs5530_set_xfer_mode(UDMA2)

And everything works as fast as I want.
My questions:

1) What's the differences in the kernels to cause this behavior?
2) How do I get my Debian kernel to behave alike?



Any help GREATLY appreciated,
	Kevin

-- 
http://www.boergens.de



                 reply	other threads:[~2004-01-10  8:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3FFFB1AD.5050307@boergens.de \
    --to=kevin@boergens.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.