public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.demon.co.uk>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 (and maybe earlier versions) can't see my IDE disks where 2.2 can
Date: 02 Jul 2002 08:50:24 +0100	[thread overview]
Message-ID: <87vg7yr2kf.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <Pine.LNX.4.10.10207010048040.10213-100000@master.linux-ide.org>

On Mon, 1 Jul 2002, Andre Hedrick spake:
> Lemme guess PDC5030 or 4030

I've just tried with that driver and append="ide0=dc4030". No joy:
identical output to the `normal' ide.c case (i.e. controller found, but
no drives found), and no mention of `Promise caching controller'
anywhere in the output. I guess my ancient Promise isn't one of those
after all. (Again, not *all* that surprising: this disk controller is
older than Linux...)

:(

I'll scatter a bunch of printk's through the code in 2.2 and 2.4
ide-probe.c and see what happens in 2.2 versus 2.4 probing; it'll be
tomorrow before that's doable though because I can only reboot the
machine in the early morning when nobody else is around.

(The code in ide-probe.c is very divergent anyway, but this might give
me, or someone else, *some* clue.)

-- 
`What happened?'
                 `Nick shipped buggy code!'
                                             `Oh, no dinner for him...'

       reply	other threads:[~2002-07-02  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10207010048040.10213-100000@master.linux-ide.org>
2002-07-02  7:50 ` Nix [this message]
2002-06-30 19:22 2.4.18 (and maybe earlier versions) can't see my IDE disks where 2.2 can Nix
2002-07-01 11:57 ` Denis Vlasenko
2002-07-01  7:43   ` Nix

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=87vg7yr2kf.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.demon.co.uk \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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