linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@debian.org>
To: Dave Peterson <dsp@llnl.gov>, Andrew Morton <akpm@osdl.org>,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
	bluesmoke-devel@lists.sourceforge.net, thayne@realmsys.com
Subject: Re: [PATCH 7/15] EDAC: i82875p cleanup
Date: Tue, 7 Mar 2006 12:47:10 -0300	[thread overview]
Message-ID: <20060307154710.GA23763@khazad-dum.debian.net> (raw)
In-Reply-To: <20060307050609.GA32733@zhen-devel.sh.intel.com>

On Tue, 07 Mar 2006, Wang Zhenyu wrote:
> On 2006.03.04 02:47:01 +0000, Dave Peterson wrote:
> >    On Thursday 02 March 2006 18:30, Andrew Morton wrote:
> >    > Dave Peterson <dsp@llnl.gov> wrote:
> >    > >  +#ifdef CORRECT_BIOS
> >    > >  +fail0:
> >    > >  +#endif
> >    >
> >    > What is CORRECT_BIOS?  Is the fact that it's never defined some sort of
> >    > commentary?  ;)
> >    I'm not sure about this.  I'm cc'ing Thayne Harbaugh and Wang Zhenyu since
> >    their names are in the credits for the i82875p module.  Maybe they can
> >    provide some info.
> 
> You can take CORRECT_BIOS as "strict-pci-resource-reserve" for overflow device
> in 82875p, some bad BIOS does make it reserved, which cause pci_request_region()
> failed.  Actually we never defined it. 

Bad? :-)  It would be bad only if they didn't *hide* the overflow device.
Regardless of the overflow device being hidden or not, that area is really
in use, and should be known to be in use.  How can you know it is in use if
the device is hidden, unless the BIOS reserves it?

Let's call that "inconvenient" BIOSes instead...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2006-03-07 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03  1:48 [PATCH 7/15] EDAC: i82875p cleanup Dave Peterson
2006-03-03  2:30 ` Andrew Morton
2006-03-03 18:47   ` Dave Peterson
2006-03-04  1:43     ` Thayne Harbaugh
2006-03-04 17:06       ` Henrique de Moraes Holschuh
2006-03-07  5:06     ` Wang Zhenyu
2006-03-07 15:47       ` Henrique de Moraes Holschuh [this message]
2006-03-03  2:30 ` Andrew Morton

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=20060307154710.GA23763@khazad-dum.debian.net \
    --to=hmh@debian.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=dsp@llnl.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thayne@realmsys.com \
    /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;
as well as URLs for NNTP newsgroup(s).