From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: John Goerzen <jgoerzen@complete.org>
Cc: Stefan Smietanowski <stesmi@stesmi.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Promise IDE controller crashes 2.4.22
Date: Sat, 29 Nov 2003 15:23:37 +0100 [thread overview]
Message-ID: <200311291523.37651.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20031129015230.GA3124@complete.org>
It means two things:
(a) There is a bug in drivers/ide/pci/pdc202xx_new.c:init_hwif_pdc202new(),
hwif->autodma shouldn't be set to 0 or "idex=dma" parameter won't work.
(b) If you don't use autodma you have to tune desired mode _explicitly_ first,
because most of ->ide_dma_check() implementations (for pdc202xx_new.c
it is pdcnew_config_drive_xfer_rate()) check for hwif->autodma.
--bart
On Saturday 29 of November 2003 02:52, John Goerzen wrote:
> On Fri, Nov 28, 2003 at 02:00:55PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > My mistake, it should have been -Xudma5 :-).
>
> I tried the ide2=dma in the kernel and then:
>
> hdparm -d 1 -u 1 -X 69 /dev/hde
>
> That did seem to solve the problem. Output of hdparm after that
> command:
>
> pi:~# hdparm /dev/hde
>
> /dev/hde:
> multcount = 16 (on)
> IO_support = 0 (default 16-bit)
> unmaskirq = 0 (off)
> using_dma = 1 (on)
> keepsettings = 0 (off)
> readonly = 0 (off)
> readahead = 8 (on)
> geometry = 19929/255/63, sectors = 320173056, start = 0
>
> What does that mean?
prev parent reply other threads:[~2003-11-29 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 18:43 Promise IDE controller crashes 2.4.22 John Goerzen
2003-11-28 19:36 ` Wes Janzen
2003-11-29 1:23 ` John Goerzen
2003-11-29 9:12 ` Wes Janzen
[not found] ` <200311281400.55500.bzolnier@elka.pw.edu.pl>
[not found] ` <20031129015230.GA3124@complete.org>
2003-11-29 14:23 ` Bartlomiej Zolnierkiewicz [this message]
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=200311291523.37651.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=jgoerzen@complete.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stesmi@stesmi.com \
/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;
as well as URLs for NNTP newsgroup(s).