lkml.org 
[lkml]   [2004]   [Jan]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Intel Alder IOAPIC fix


On Mon, 12 Jan 2004, James Bottomley wrote:
>
> OK, with the patch below (to insert_resource) I know get the IO APIC
> successfully inserted under the reserved fixmap resources:
>
> /proc/iomem still looks very odd:
>
> fec00000-fec08fff : reserved
> fec01000-fec013ff : 0000:00:0f.0
> fffffc00-ffffffff : 0000:00:0f.0
> fffffc00-ffffffff : 0000:00:0f.0
> fffffc00-ffffffff : 0000:00:0f.0
> fffffc00-ffffffff : 0000:00:0f.0
> fffffc00-ffffffff : 0000:00:0f.0
> ffe80000-ffffffff : reserved
>
> unfortunately, because BARs 1-5 cover the same region.

I think BARs 1-5 don't exist at all. Being set to all ones is common for
"unused" (it ends up being a normal result of a lazy probe - you set all
bits to 1 to check for the size of the region, and if you decide not to
map it and leave it there, you'll get the above behaviour).

I suspect only BAR0 is actually real.

What's in that ffe80000-ffffffff region that the BIOS has allocated,
anyway?

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

\
 
 \ /
  Last update: 2009-11-18 23:46    [W:0.056 / U:1.592 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site