From: Grant Grundler <grundler@dsl2.external.hp.com>
To: j.steindlberger@gmx.de
Cc: moritz@freesources.org, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] ide controller
Date: Thu, 19 Sep 2002 16:33:16 -0600 [thread overview]
Message-ID: <20020919223316.13D0E4829@dsl2.external.hp.com> (raw)
In-Reply-To: Message from j.steindlberger@gmx.de of "Thu, 19 Sep 2002 10:41:14 +0200." <28859.1032424874@www2.gmx.net>
j.steindlberger@gmx.de wrote:
> drivers. We disabled the following:
> [ ] Generic PCI bus-master DMA support
hmm....ok.
> After compiling wie had these three modules:
> ide-mod.o
> ide-probe-mod.o
> ide-disk.o
No pdc202xx.o?
> An insmod ide-mod.o was possible. But after insmod ide-probe-mod the kernel
> crashes. In some cases we got an output with about 50 pages of memory
> addresses. At the beginning we got some messages told about the SYM-SCSI-devi
> ce.
> Could that be a conflict?
I don't think so.
> We did not succeed to reproduce that and log it.
>
> Here my questions:
> Did You here about anyone to succeed in using an IDE-controller in a
> HP-RISC-architecture?
Yes. My C3000 has IDE CD-ROM hanging off the "SuckyIO" chip.
That works using PIO mode thanks to Randolph Chung/Thomas Bogendoerfer.
> Do You see a chance to use IDE-disks in future (with some none
> HP-controller)
yes - but I don't expect it to "just work".
IDE is a PoS with lots of buggy HW.
PARISC isn't very tolerant of many things the x86 PCs tolerate.
(eg access to disabled devices, PCI parity errors)
> Do You know about more people who are interrested in what we tried to do?
I don't offhand. If someone is, I ask they contact you directly.
Please continue to post status here and I'll offer advice when I can.
> That would be an argument for me to continue experimenting.
If you get it working, I'd be happy to help put any changes back
into our source tree and ultimately back to Alan Cox/Linus.
...
> > #define PDC202XX_DEBUG_DRIVE_INFO 0
> > #define PDC202XX_DECODE_REGISTER_INFO 0
> >
> > and rebuild the module with that.
> >
> > 3) post the console log and "ser pim" output at PDC prompt.
Using a serial console makes it easier to grab console logs in
the case were the machine is crashing.
Generally, I can help decode HPMCs and explain what might be wrong.
That's what the "ser pim" output is for.
I really need both to debug most IO problems.
grant
prev parent reply other threads:[~2002-09-19 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k7lm3mt8.fsf@appserv.sinnhq.de>
2002-09-16 4:30 ` [parisc-linux] Re: ide controller Grant Grundler
2002-09-19 8:41 ` [parisc-linux] " j.steindlberger
2002-09-19 10:06 ` Alan Cox
2002-09-19 12:50 ` J.Steindlberger
[not found] ` <20020919125032.50BB0482A@dsl2.external.hp.com>
2002-09-19 23:02 ` Grant Grundler
2002-09-19 22:33 ` Grant Grundler [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=20020919223316.13D0E4829@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=j.steindlberger@gmx.de \
--cc=moritz@freesources.org \
--cc=parisc-linux@lists.parisc-linux.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