All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J.Steindlberger" <j@steindlberger.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Grant Grundler <grundler@dsl2.external.hp.com>,
	moritz@freesources.org, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] ide controller
Date: Thu, 19 Sep 2002 14:50:45 +0200	[thread overview]
Message-ID: <20020919125032.31FE74829@dsl2.external.hp.com> (raw)
In-Reply-To: <1032430004.26669.1.camel@irongate.swansea.linux.org.uk>

On Thursday 19 September 2002 12:06, you wrote:
> Our IDE code has been run on non x86 platforms. It does require that the
> defaults are set right for the platform so that it doesnt do stuff like
> blindly probe I/O 0x170.
>
> I don't know if the Promise card needs its BIOS to have run, I would
> suspect not but can't be sure.

Hi Alan,

we tried a different controller with originally an eprom bios. We simply put 
that eeprom away. (The Promise has a chip-integrated flash bios - putting 
that away seems not to be possible.) The kernel crashed alike. Do You have 
any ideas to get more debug output? I could set up my second C-Class with 
parisc-linux and test it there. (The first one is now running some essential 
services - continued crashing would not be good.)

Then I will have a deep look into the linux-code (oh, I'll have to learn C) 
and search for that stupid (sorry) 0x170 probe.

Thanks a lot! You will read more...
Joerg

  reply	other threads:[~2002-09-19 12:50 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 [this message]
     [not found]       ` <20020919125032.50BB0482A@dsl2.external.hp.com>
2002-09-19 23:02         ` Grant Grundler
2002-09-19 22:33     ` Grant Grundler

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=20020919125032.31FE74829@dsl2.external.hp.com \
    --to=j@steindlberger.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=grundler@dsl2.external.hp.com \
    --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 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.