public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@verizon.net>
To: Ankit Jain <ankitjain1580@yahoo.com>
Cc: newbie <linux-newbie@vger.kernel.org>
Subject: Re: address limitation
Date: Fri, 08 Oct 2004 18:08:36 -0400	[thread overview]
Message-ID: <41670FE4.6020605@verizon.net> (raw)
In-Reply-To: <20041008122809.99434.qmail@web52906.mail.yahoo.com>

Ankit Jain wrote:

>hi
>
>well i am not able ot understand this... there are lot
>many more problems
>
>/proc/iomem
>00000000-0009fbff : System RAM
>0009fc00-0009ffff : reserved
>000a0000-000bffff : Video RAM area
>000c0000-000c7fff : Video ROM
>000f0000-000fffff : System ROM
>00100000-077effff : System RAM
>00100000-00250d5b : Kernel code
>00250d5c-0034ac43 : Kernel data
>
>this is just a brief..... System RAM what does that
>mean? the range can just point 65K of RAM? what about
>rest? so what that means?
>  
>

Okay,

00000000-0009fbff : System RAM

This is the 640 KB that is part of the legacy support for real-mode PC 
applications.

0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM


This is the BIOS and VGA address area (up to 1 MB), once again to 
support real-mode PC stuff (DOS, primarily).  The original IBM PC's (I 
think starting with the XT, maybe the PC) had a 20-bit memory addressing 
scheme, but only 16-bit registers.  If you ever want to hop into the 
way-back machine to the days of CGA's, hardcards, and 5 1/4" floppies, 
grab a book on DOS programming - FreeDOS (http://www.freedos.org) is 
still out there, and it's actually kind of fun to run something that 
blindingly simple :)

00100000-077effff : System RAM


Here is the rest of your system's memory.


>also,
>
>on a 32 bit proceesor we can at the most have a access
>to 4GB of area as we have that many address space.
>well some what it look stupid but then also asking
>some where this blunder i have to clear, that how it
>access the hard disks which is of much high capacity?
>  
>
Hard disks are controlled by sending requests to and from the drive for 
blocks of data.  Sort of like reading a book - you only see a couple of 
pages at a time, but you can access the whole book, or any section of 
it, by flipping to the right page number.  Same way with the hard disk 
controller.  Ask it for sector 11432, and it will give it to you 
(oversimplified, but essentially correct).


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs

  reply	other threads:[~2004-10-08 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 12:28 address limitation Ankit Jain
2004-10-08 22:08 ` Jim Nelson [this message]
2004-10-09  9:12   ` Ankit Jain
2004-10-09  9:44     ` Jim Nelson

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=41670FE4.6020605@verizon.net \
    --to=james4765@verizon.net \
    --cc=ankitjain1580@yahoo.com \
    --cc=linux-newbie@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox