From: Robert Hancock <hancockr@shaw.ca>
To: Reinaldo de Carvalho <reinaldow@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Another missing RAM on x86_64
Date: Wed, 06 Jun 2007 17:47:56 -0600 [thread overview]
Message-ID: <466747AC.1080606@shaw.ca> (raw)
In-Reply-To: <4667362A.8040200@gmail.com>
Reinaldo de Carvalho wrote:
> This laptop have a nVidia 10de:0244 with 256Mb of RAM. No shared memory.
>
>
> Reinaldo de Carvalho
>
>
>
> 00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express
> Bridge (rev a2) (prog-if 00 [VGA])
> Subsystem: Hewlett-Packard Company Unknown device 30b5
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> Interrupt: pin A routed to IRQ 21
> Region 0: Memory at c2000000 (32-bit, non-prefetchable) [size=16M]
> Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
> Region 3: Memory at c1000000 (64-bit, non-prefetchable) [size=16M]
> [virtual] Expansion ROM at 50000000 [disabled] [size=128K]
> Capabilities: [48] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+
> Queue=0/0 Enable-
> Address: 0000000000000000 Data: 0000
It's a bit mysterious, then, where the extra 40-some MB of RAM has gone.
However, there's not much the kernel can do about it, as the BIOS is not
telling us about that memory..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2007-06-06 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.tF0YmfAYyv6X2INP3hwTgQ2Z2Pw@ifi.uio.no>
2007-06-05 3:40 ` Another missing RAM on x86_64 Robert Hancock
2007-06-06 22:33 ` Reinaldo de Carvalho
2007-06-06 23:47 ` Robert Hancock [this message]
2007-06-05 2:20 Reinaldo de Carvalho
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=466747AC.1080606@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=reinaldow@gmail.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