Filippo Giunchedi <[email protected]> wrote:
Hi,
>> Thanks. The mmap fails for some reason that's not immediately obvious
>> :/ Did you ever have a working pommed?
>
> sure, it's been working flawlessly since ever! (implicit "thanks for pommed"
> here)
OK, that's a good data point (and you're welcome ;))
> That's why I'm rather puzzled at this... I'm not sure what has changed or
> where
> to look. I'm starting to think that I might be missing something obvious.
That was your lspci output:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: Apple Computer Inc. Device 00a1
Flags: bus master, fast devsel, latency 0, IRQ 315
Memory at d0100000 (64-bit, non-prefetchable) [size=1M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 3110 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Mask- 64bit- Count=1/1 Enable+
Capabilities: [d0] Power Management version 3
Kernel modules: intelfb
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated
Graphics Controller (rev 03)
Subsystem: Apple Computer Inc. Device 00a1
Flags: bus master, fast devsel, latency 0
Memory at d0200000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [d0] Power Management version 3
Compare with:
<http://launchpadlibrarian.net/16481998/lspci-vvnn.log>
The memory regions are the same except for one bit. Something changed
at some level and the memory regions aren't reported in the same way
anymore. (wonder if it's linked to the OS X update?)
Can you send me your dmesg? I'd like to see what the PCI layer has to
tell about that. (mainly to see if using resource files under /sys
would work as opposed to using /dev/mem)
JB.
--
Julien BLACHE - Debian & GNU/Linux Developer - <[email protected]>
Public key available on <http://www.jblache.org> - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
