From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Tobias Ringstrom <tori@tellus.mine.nu>,
David Balazic <david.balazic@uni-mb.si>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: MTRR type AMD Duron/intel ?
Date: Mon, 15 Jan 2001 22:01:25 +0200 [thread overview]
Message-ID: <20010115220125.U25659@mea-ext.zmailer.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0101151937460.8658-100000@svea.tellus> <Pine.LNX.4.10.10101151151080.6408-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10101151151080.6408-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Mon, Jan 15, 2001 at 11:52:12AM -0800
On Mon, Jan 15, 2001 at 11:52:12AM -0800, Linus Torvalds wrote:
> On Mon, 15 Jan 2001, Tobias Ringstrom wrote:
> > Last time I checked this was issued for perfectly known and valid bridges
> > that advertice no IO resources. Isn't it a bit silly to issue that
> > warning for that case, or am I missing something?
>
> Ehh - so what do they bridge, then?
>
> I'd say that a bridge that doesn't seem to bridge any IO or MEM region,
> yet has stuff behind it, THAT is the silly thing. Thus the "silly"
> warning.
Like a cardbus controller without any cards in ?
My IBM laptop reports that at the TI PCI1450 bridges,
when I don't have anything plugged in.
> Linus
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-15 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 19:35 David Balazic
2001-01-15 18:42 ` Tobias Ringstrom
2001-01-15 19:46 ` David Balazic
2001-01-15 19:52 ` Linus Torvalds
2001-01-15 19:01 ` Tobias Ringstrom
2001-01-15 20:01 ` Matti Aarnio [this message]
2001-01-15 21:44 ` H. Peter Anvin
2001-01-15 23:45 ` David Wragg
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=20010115220125.U25659@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=david.balazic@uni-mb.si \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@tellus.mine.nu \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®