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 21:01:36 +0200 [thread overview]
Message-ID: <17337971375@vcnet.vc.cvut.cz> (raw)
On 8 Aug 02 at 11:43, Andre Hedrick wrote:
> On Thu, 8 Aug 2002, Petr Vandrovec wrote:
> > 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.
>
> Again you have no experience in the logic!
>
> This boots with Promise first because of BIOS Logic with INT19 hooks.
> IE, that which I referenced in the documents that I know you did not read
> but come back and state it has nothing to do with the issues.
> Electrons wasted :-/
Yes, exactly. If you really believe that ide# (or even hd#) numbering
should change according to the BIOS boot order, then there is certainly
nothing we can agree on. And if I boot from floppy or SCSI, should IDE
code skip ide0/hda at all?
Maybe you did not notice that Linux can boot of /dev/hde, it does not
have to boot from /dev/hda. Just tell to LILO where /dev/hde lives (and
there are patches for EDD support, but adding two lines into /etc/lilo.conf
is easier than patching support for EDD structure, which is broken in 50%
of BIOSes I know anyway).
Petr
next reply other threads:[~2002-08-08 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 19:01 Petr Vandrovec [this message]
2002-08-09 17:32 ` Part 2: Re: [PATCH] pdc20265 problem Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:29 Petr Vandrovec
2002-08-08 18:43 ` Andre Hedrick
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=17337971375@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox