public inbox for linux-kernel@vger.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: [PATCH] pdc20265 problem.
Date: Thu, 8 Aug 2002 14:45:18 +0200	[thread overview]
Message-ID: <16CF2372467@vcnet.vc.cvut.cz> (raw)

On  8 Aug 02 at 3:50, Andre Hedrick wrote:
> On Wed, 7 Aug 2002, Bill Davidsen wrote:
> 
> > I would just as soon use a boot option as to try and make it a compile
> > option, and I think that many people just use a compiled kernel and never
> > change, which argues for a reasonable default (most pdc20265) ARE
> > currently offboard, and an easy way to change it.
> 
> There are ZERO pdc20265's offboard, only pdc20267's were in both options.
> This is the direct asic packaging.  Thus all pdc20265 have the right to be
> listed as onboard.  If you have a pdc20265 on an add-on card please send
> me a digital photo so I can question promise as to why.

They are on the mainboard, but mainboard has also (in my case VIA) IDE
chipset on the shelf, and BIOS shows everywhere (autodetection, IDE config)
that VIA is the primary chipset, and PDC ('UDMA100' interface in the BIOS)
is an additional, optional, interface. So forcing PDC20265 as primary is 
a bug - it is not consistent with BIOS, it is not consistent with Windows, 
and it is not consistent with other Linux versions.

Up to now nobody showed me mainboard which has PDC20265, but which does
not have other IDE chipset integrated in the southbridge, or at least
mainbord with BIOS which names disks connected to the PDC primary/secondary
master/slave. It is 3rd/4th channel on all mainboards I ever saw.
                                                    Petr Vandrovec
                                                    vandrove@vc.cvut.cz
                                                    

             reply	other threads:[~2002-08-08 12:42 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 12:45 Petr Vandrovec [this message]
2002-08-08 13:02 ` [PATCH] pdc20265 problem Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:22 Petr Vandrovec
2002-08-08 18:35 ` Andre Hedrick
2002-08-09  6:47   ` Marcin Dalecki
2002-08-12  1:24     ` Andre Hedrick
2002-08-08 16:48 Petr Vandrovec
2002-08-08 17:30 ` Andre Hedrick
2002-08-07 18:39 Adam J. Richter
2002-08-07 19:33 ` Thunder from the hill
2002-08-07 21:11   ` Alan Cox
2002-08-07 20:02     ` Thunder from the hill
2002-08-07 23:40       ` Alan Cox
2002-08-07 10:20 Petr Vandrovec
2002-08-07 23:04 ` Bill Davidsen
2002-08-07  7:54 Adam J. Richter
2002-08-07 11:41 ` Alan Cox
2002-08-07 23:08   ` Bill Davidsen
2002-08-08 10:49     ` Zwane Mwaikambo
2002-08-07 16:32 ` Thunder from the hill
2002-08-06 10:28 Petr Vandrovec
2002-08-02 19:05 Bartlomiej Zolnierkiewicz
2002-08-02 23:05 ` Marcelo Tosatti
2002-08-03  0:55   ` Bartlomiej Zolnierkiewicz
2002-08-03  0:08     ` Marcelo Tosatti
2002-08-03  1:22     ` Nick Orlov
2002-08-03 13:41       ` Alan Cox
2002-08-06  3:48     ` Bill Davidsen
2002-08-06  4:33       ` Nick Orlov
2002-08-07  3:09         ` Bill Davidsen
2002-08-07  3:56           ` Nick Orlov
2002-08-07 18:30             ` Andre Hedrick
2002-08-07 20:27               ` Tomas Szepe
2002-08-07 22:46             ` Bill Davidsen
2002-08-08 10:50               ` Andre Hedrick
2002-08-08 17:42                 ` Nick Orlov
2002-08-08 18:02                   ` Andre Hedrick
2002-08-09  6:44                     ` Marcin Dalecki
2002-08-12  1:37                       ` Andre Hedrick
2002-08-09 17:16                 ` Bill Davidsen
2002-08-01  6:38 Linux v2.4.19-rc5 Marcelo Tosatti
2002-08-02  1:47 ` [PATCH] pdc20265 problem Nick Orlov
2002-08-02  2:29   ` Nick Orlov
2002-08-02 12:27   ` Alan Cox
2002-08-02 12:52     ` Nick Orlov
2002-08-02 14:00       ` Bartlomiej Zolnierkiewicz
2002-08-02 14:45         ` Nick Orlov

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=16CF2372467@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