All of lore.kernel.org
 help / color / mirror / Atom feed
From: alfred hitch <alfred.hitch@gmail.com>
To: Marco Gerards <metgerards@student.han.nl>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Fwd: memory probing
Date: Tue, 10 May 2005 06:23:00 -0400	[thread overview]
Message-ID: <29f91651050510032358cc2370@mail.gmail.com> (raw)
In-Reply-To: <87y8an4emu.fsf@student.han.nl>

I agree with u, 
if there are holes and all in the area being scanned also with this fail ?

anyways, how can u get this from processor also ? 
I vaguely remember see'ing some code where someone on a i386 based
plattform but WITHOUT bios, used smbus protocol to talk to a device
across PIIX4 to get the info.

I am not familiar with PC architecture, so can someone tell me if
there is some standard chip  (memory controller? ?) where one can read
this on PC type arch. atleast ?

I am on  a IXDP425 plattform, and so far I cannot see any such
register on the data sheets ..

Cheers,
Alfred

On 5/10/05, Marco Gerards <metgerards@student.han.nl> wrote:
> "coly li" <colyli@263.net> writes:
> 
> > write and verify means: you read the content from location X, and
> > change the value, then write back to location X; then re-read the
> > content from X, if the value is what you write, the location X is
> > valid; otherwise, maybe the location X is invalid.
> 
> This sounds dangerous to me, what if you are writing to memory mapped
> I/O?  I think you can get the amount of memory from the processor, no?
> 
> --
> Marco
> 
>



  reply	other threads:[~2005-05-10 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10  8:50 Re: Fwd: memory probing coly li
2005-05-10  9:24 ` Marco Gerards
2005-05-10 10:23   ` alfred hitch [this message]
2005-05-10 12:13     ` Stefan Reinauer
2005-05-11  2:11       ` alfred hitch
2005-05-11  4:39         ` Douglas Wade Needham
2005-05-11  7:47           ` alfred hitch
2005-05-11 17:09             ` Douglas Wade Needham
  -- strict thread matches above, loose matches on Subject: below --
2005-05-10  7:37 coly li
2005-05-10  8:33 ` alfred hitch

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=29f91651050510032358cc2370@mail.gmail.com \
    --to=alfred.hitch@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=metgerards@student.han.nl \
    /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.