From: Len Brown <len.brown@intel.com>
To: "Ph. Marek" <philipp.marek@bmlv.gv.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can't access ACPI memory through /dev/mem
Date: 12 Mar 2004 10:55:00 -0500 [thread overview]
Message-ID: <1079106900.2173.21.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F4E11@hdsmsx402.hd.intel.com>
does dmidecode find what you're looking for?
http://www.nongnu.org/dmidecode/
-Len
On Fri, 2004-03-12 at 04:18, Ph. Marek wrote:
> Hello everybody!
>
> My machine gives me for
> $ cat /proc/iomem
> 00000000-0009fbff : System RAM
> 0009fc00-0009ffff : reserved
> 000a0000-000bffff : Video RAM area
> 000c0000-000c7fff : Video ROM
> 000d0000-000d9fff : Extension ROM
> 000f0000-000fffff : System ROM
> 00100000-0f7dffff : System RAM
> 00100000-0022ca51 : Kernel code
> 0022ca52-0029d8e3 : Kernel data
> 0f7e0000-0f7e7fff : ACPI Tables
> 0f7e8000-0f7fffff : ACPI Non-volatile Storage
> 80100000-801fffff : PCI Bus #01
> 80100000-8011ffff : Silicon Integrated Systems [SiS] SiS630
> GUI
> and so on.
>
> Now I can access the whole area below the ACPI tables (I tried RAM,
> video and
> system ROM, and kernel code/data).
> But on reaching the ACPI tables and above (PCI space and so on) I get
> no data
> (that is, vche blanks the screen).
>
> I'd expect that for the PCI space - as this is really IO-memory and
> shouldn't
> be messed with.
>
> But I'd like to access the ACPI tables; especially the NVRAM, as some
> machines
> store DMI data there.
>
> This is on
> Linux version 2.4.24-1-686 (herbert@gondolin) (gcc version
> 3.3.2 (Debian))
> and an old 2.4.19 kernel.
>
>
> Any tips? Help for accessing this memory space?
>
>
> Regards,
>
> Phil
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" 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.tux.org/lkml/
>
next parent reply other threads:[~2004-03-12 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F4E11@hdsmsx402.hd.intel.com>
2004-03-12 15:55 ` Len Brown [this message]
2004-03-15 12:58 ` Can't access ACPI memory through /dev/mem Ph. Marek
2004-03-12 9:18 Ph. Marek
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=1079106900.2173.21.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.marek@bmlv.gv.at \
/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