From: Grant Grundler <grundler@parisc-linux.org>
To: "M. Grabert" <xam@cs.ucc.ie>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] C3000 and Promise Ultra100 TX2 PCI Controller
Date: Thu, 26 Feb 2004 08:56:59 -0700 [thread overview]
Message-ID: <20040226155659.GA11451@colo.lackof.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0402260513010.28003@sal.ucc.ie>
On Thu, Feb 26, 2004 at 05:24:45AM +0000, M. Grabert wrote:
> Maybe I took out too many lines when I responded to my Alan's reply;
> The first part of the mail describes a problem with the siimage driver
> (big-endian problem), the rest of the mail is also about the Promise IDE
> controller I'm currently trying to get working.
ah ok. that makes sense. I probably just read your mail too fast.
> Both the Silicon Image and the Promise IDE controller show the
> "hda: lost interrupt" symptom. However the Promise driver seems to
> me more 'usable' or easily fixable than the siimage driver, since
> it detects the controller and hard disk correctly!
yes - the endian issue is probably harder to fix.
If the Promise interrupt is being delivered on a different interrupt line
than the one advertised (INTERRUPT_PIN), then dumping the state
of the IOSAPIC should show which IRQ input is "high" and we can
figure out where the disconnect is.
But I'm skeptical that's really the issue. I suspect more the IDE command
isn't being programmed properly into the Promise controller and thus it
doesn't DMA correctly or for some other reason complete the command.
ie it has no reason to interrupt.
> The Promise Ultra100 TX2 controller is reported to work on PPC - not the
> siimage one - so there is probably no difference between the PARISC and
> PPC ports in this respect.
ok
grant
>
> Greetings,
> Max
next prev parent reply other threads:[~2004-02-26 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 0:52 [parisc-linux] C3000 and Promise Ultra100 TX2 PCI Controller M. Grabert
2004-02-26 1:08 ` Alan Cox
2004-02-26 1:59 ` M. Grabert
[not found] ` <20040226051124.GB3645@colo.lackof.org>
[not found] ` <Pine.LNX.4.58.0402260513010.28003@sal.ucc.ie>
2004-02-26 15:56 ` Grant Grundler [this message]
2004-02-27 18:44 ` Alan Cox
2004-02-27 21:23 ` Grant Grundler
2004-02-27 23:50 ` M. Grabert
2004-02-28 1:05 ` M. Grabert
2004-02-28 16:07 ` Alan Cox
2004-02-28 16:45 ` Grant Grundler
2004-02-28 17:24 ` James Bottomley
2004-02-28 17:41 ` Matthew Wilcox
2004-02-28 19:48 ` Grant Grundler
2004-02-28 1:53 ` Matthew Wilcox
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=20040226155659.GA11451@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=xam@cs.ucc.ie \
/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