MTRR type AMD Duron/intel ?
A recent 2.4.0 ( not the final , but close ) kernel prints this :
mtrr: detected mtrr type: intel
I have an AMD K7 Duron 700 CPU
Is this correct ?
It also reports something like :
PCI chipset unknown : assuming transparent
I have a VIA KT133 chipset
Signature · 8 lines
David Balazic -------------- "Be excellent to each other." - Bill & Ted - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 2 lines · David Balazic
It also reports something like :
PCI chipset unknown : assuming transparent
Are you sure it's not
Unknown bridge resource 0: assuming transparent
(which is just about every kernel log I have seen...)
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?
/Tobias
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 9 lines · Tobias Ringstrom
Quoted 2 lines · David Balazic
It also reports something like :
PCI chipset unknown : assuming transparentAre you sure it's not
Unknown bridge resource 0: assuming transparent
Might be, I don't remember the exact wording.
Signature · 8 lines
David Balazic -------------- "Be excellent to each other." - Bill & Ted - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 4 lines · Tobias Ringstrom
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.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 11 lines · Linus Torvalds
Quoted 4 lines · Tobias Ringstrom
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.
I'm talking about bridges that bridge memory, but not io, which is quite common. (AGP bridges)
I do not have my PCI book right now, but there are two registers, basically io_base and io_limit, and if io_limit == io_base-1, that means that no io is bridged.
I still think its silly. ;-)
/Tobias
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 10 lines · Linus Torvalds
Quoted 3 lines · Tobias Ringstrom
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.
Quoted 1 line
Linus
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Followup to: <[email protected]> By author: Linus Torvalds <[email protected]> In newsgroup: linux.dev.kernel
Quoted 7 lines · Tobias Ringstrom
Quoted 4 lines
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?
Quoted 6 lines
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.
What kind of bridge? Depending on the kind of bridge, it could be a subtractive-decoding bridge; or it could be a Host Bridge, which normally advertise only the resources it needs for itself.
-hpa
Signature · 7 lines
<[email protected]> at work, <[email protected]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 7 lines · David Balazic
A recent 2.4.0 ( not the final , but close ) kernel prints this :
mtrr: detected mtrr type: intel
I have an AMD K7 Duron 700 CPU
Is this correct ?
Yes. The K7 supports MTRRs exactly according to the Intel specs, as opposed to the MTRR-like but somewhat different features that some other x86 CPUs implement. So while it may appear odd, it is correct.
David Wragg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/