From: "Mallick, Asit K" <asit.k.mallick@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Re: Support for more than 2GB RAM
Date: Wed, 19 Jul 2000 17:18:52 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205216@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205208@msgid-missing>
We are making good progress with the PCI DMA implementation and we should
have a patch by end of this week. This will remove the 2GB RAM check adn
will use all the memory in the system.
--Asit
> -----Original Message-----
> From: David Mosberger [mailto:davidm@hpl.hp.com]
> Sent: Wednesday, July 19, 2000 8:22 AM
> To: Christoph Rohland
> Cc: linux-ia64@linuxia64.org
> Subject: [Linux-ia64] Re: Support for more than 2GB RAM
>
>
> You should be able to change that check to 4GB without ill effects.
> (The 1GB check is there for historical reasons.) Anyhow, if this
> isn't urgent, I'd just wait until Goutham is done with the PCI DMA
> implementation and then that check will go away completely.
>
> --david
>
> >>>>> On 19 Jul 2000 11:07:15 +0200, Christoph Rohland
> <cr@sap.com> said:
>
> Christoph> David Mosberger <davidm@hpl.hp.com> writes:
> >> >>>>> On 18 Jul 2000 14:40:42 +0200, Christoph Rohland
> >> <cr@sap.com> said:
> >>
> Christoph> Hi, Are there any plans to support more than 2GB RAM in
> Christoph> the near future?
> >> There never was a limit for 2GB. 4GB is no problem and more
> >> than 4GB works fine also except if there are 32-bit PCI devices
> >> that do DMA (or the machine has huge holes in the physical
> >> address space, which isn't true for the prototypes). For the DMA
> >> issue, a solution is in the works (Goutham has been working on
> >> this).
>
> Christoph> So why do I get the following:
>
> Christoph> Linux version 2.4.0-0.8smp (root@boris.devel.redhat.com)
> Christoph> (gcc version 2.9-ia64-0 00216-final) #1 SMP Sun Jun 18
> Christoph> 00:32:35 EDT 2000 EFI v0.92 by INTEL
> Christoph> AL460GX.86B.0027.D27.021800: SALsystab=0x7ff29d60
> Christoph> ACPI=0x7ffd 9718 MPS=0x7ffd0000 map_pal_code: mapping PAL
> Christoph> code [0x7ff40000-0x7ff7b000) into [0xe00000007fc00000-
> Christoph> 0xe000000080000000) Warning: ignoring 0MB of memory above
> Christoph> 1GB! Warning: ignoring 0MB of memory above 1GB!
> Christoph> Warning: ignoring 2046MB of memory above 1GB!
>
> Christoph> and I can only use 2GB of my 4GB machine?
>
> Christoph> Greetings Christoph
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>
next prev parent reply other threads:[~2000-07-19 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 9:07 [Linux-ia64] Re: Support for more than 2GB RAM Christoph Rohland
2000-07-19 9:35 ` Akbar A.
2000-07-19 15:17 ` Christoph Rohland
2000-07-19 15:21 ` David Mosberger
2000-07-19 17:18 ` Mallick, Asit K [this message]
2000-07-19 17:37 ` Christoph Rohland
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=marc-linux-ia64-105590678205216@msgid-missing \
--to=asit.k.mallick@intel.com \
--cc=linux-ia64@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.