All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Nick Orlov <nick.orlov@mail.ru>,
	B.Zolnierkiewicz@elka.pw.edu.pl,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	linux-kernel@vger.kernel.org, davidsen@tmr.com
Subject: Re: Part 2: Re: [PATCH] pdc20265 problem.
Date: Thu, 8 Aug 2002 20:29:34 +0200	[thread overview]
Message-ID: <172AF2F5BB8@vcnet.vc.cvut.cz> (raw)

On  8 Aug 02 at 10:41, Andre Hedrick wrote:

> ide0 at 0xdfe0-0xdfe7,0xdfae on irq 31
> ide1 at 0xdfa0-0xdfa7,0xdfaa on irq 31
> ide2 at 0x1f0-0x1f7,0x3f6 on irq 14

This is definitely bug. It should assigned ide0 to the port
in legacy mode, as far as I can tell.
 
> PIIX4: IDE controller on PCI bus 00 dev 39
> PIIX4: device not capable of full native PCI mode
> PIIX4: device disabled (BIOS)
> PIIX4: device disabled (BIOS)
> hda: DupliDisk IDE RAID-1 Adapter( 1.19), ATA DISK drive
> hdc: QUANTUM FIREBALLP KA13.6, ATA DISK drive
> ide2: ports already in use, skipping probe
> ide0 at 0xd800-0xd807,0xdc02 on irq 18
> ide1 at 0xe400-0xe407,0xe802 on irq 18

You have disabled PIIX4 here, so ide0/1 were not reserved. I assume
that if you enable PIIX4, it will use legacy ports, and will become
ide0/1.
                                            Petr Vandrovec
                                            

             reply	other threads:[~2002-08-08 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 18:29 Petr Vandrovec [this message]
2002-08-08 18:43 ` Part 2: Re: [PATCH] pdc20265 problem Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08 19:01 Petr Vandrovec
2002-08-09 17:32 ` Bill Davidsen
2002-08-08 16:48 Petr Vandrovec
2002-08-08 17:41 ` Part 2: " Andre Hedrick

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=172AF2F5BB8@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=andre@linux-ide.org \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=nick.orlov@mail.ru \
    /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.