public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Orlov <nick.orlov@mail.ru>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Bill Davidsen <davidsen@tmr.com>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pdc20265 problem.
Date: Thu, 8 Aug 2002 13:42:58 -0400	[thread overview]
Message-ID: <20020808174258.GA5622@nikolas.hn.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10208080344290.24560-100000@master.linux-ide.org>

On Thu, Aug 08, 2002 at 03:50:19AM -0700, 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.

Could you comment next couple lines of code (2.4.19-vanilla):

==========================================
#else /* !CONFIG_PDC202XX_FORCE */
[ ... skipped ... ]
        {DEVID_PDC20265,"PDC20265" .... OFF_BOARD ..... },
                                        ^^^^^^^^^
[ ... skipped ... ]
#endif
==========================================

Another bug? Just typo?
Why author put PDC20265 in off-board list ?

> Cheers,
> 
> Andre Hedrick
> LAD Storage Consulting Group
> 

-- 
With best wishes,
        Nick Orlov.


  reply	other threads:[~2002-08-08 17:41 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 19:05 [PATCH] pdc20265 problem 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 15:37       ` [PATCH] " Nick Orlov
2002-08-03 18:29         ` Nick Orlov
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 [this message]
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
  -- 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-08 12:45 Petr Vandrovec
2002-08-08 13:02 ` 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-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=20020808174258.GA5622@nikolas.hn.org \
    --to=nick.orlov@mail.ru \
    --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 \
    /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