Re: [PATCH] APIC physical broadcast for i82489DX

[William Lee Irwin III]

On Thu, 7 Oct 2004, William Lee Irwin III wrote:
>> This is the same as version <= 0xf || version >= 0x14; I'm rather

On Thu, Oct 07, 2004 at 11:12:55PM +0100, Maciej W. Rozycki wrote:
>  I suppose defining a macro called something like APIC_XAPIC(x) to (x >= 
> 0x14) might actually have some sense, although unlike with the i82489DX, 
> there is no promise for this to be always true.

There is a presumption there that higher APIC revisions will be
backward-compatible and will have comparable version numbers, yes.


On Thu, 7 Oct 2004, William Lee Irwin III wrote:
>> suspicious, as the docs have long since been purged, making this

On Thu, Oct 07, 2004 at 11:12:55PM +0100, Maciej W. Rozycki wrote:
>  AFAIK i82489DX documents were never available online and I suppose they
> might have never existed in a PDF form.  You could have ordered hardcopies
> in mid 90's.

Which probably either predated or coincided with my earliest use of
computers.


On Thu, 7 Oct 2004, William Lee Irwin III wrote:
>> hopeless for anyone without archives (or a good memory) dating back to
>> that time to check. All that's really needed is citing the version that
>> comes out of the version register and checking other APIC
>> implementations to verify they don't have versions tripping this check,

On Thu, Oct 07, 2004 at 11:12:55PM +0100, Maciej W. Rozycki wrote:
>  The APIC_INTEGRATED() macro reflects the range reserved for the i82489DX.  
> Both "Multiprocessor Specification" and "IA-32 Intel Architecture Software
> Developer's Manual, Vol.3" which are available online specify it clearly
> and explicitly.  AFAIK, there is no integrated APIC implementation that
> would violate it (unlike with I/O APICs), so what's the problem?  If a 
> buggy chip appears, we can revisit this assumption.

Only documentation; this is probably as good as it gets, so I'm happy
with this level of explanation, for instance, saying what the revision
numbers are.


On Thu, 7 Oct 2004, William Lee Irwin III wrote:
>> the latter of which is feasible for those relying on still-extant
>> documentation. Better yet would be dredging up the docs... So, what is
>> the range of the version numbers reported by i82489DX's?

On Thu, Oct 07, 2004 at 11:12:55PM +0100, Maciej W. Rozycki wrote:
>  The i82489DX datasheet documents 0x01 for the chip and the
> implementations I've encountered so far agree.

Since it's not available online this will have to do. I seem to have
turned up some vague evidence they were made into PDF's ca. 1993, but
don't really expect that to mean anything.


-- wli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/