* Probing for (non-existing) memory?
@ 1999-10-21 19:28 Wolfgang Denk
1999-10-21 20:36 ` Michael Schmitz
0 siblings, 1 reply; 2+ messages in thread
From: Wolfgang Denk @ 1999-10-21 19:28 UTC (permalink / raw)
To: linuxppc-dev
Hi,
please excuse the silly question: is there a standard way to probe an
address if it is readable/writable memory? Ideally something that is
portable across all architectures?
[For those familiar with LynxOS: what I'm looking for is something
like recoset() / noreco().]
Thanks in advance,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Never give in. Never give in. Never. Never. Never."
- Winston Churchill
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Probing for (non-existing) memory?
1999-10-21 19:28 Probing for (non-existing) memory? Wolfgang Denk
@ 1999-10-21 20:36 ` Michael Schmitz
0 siblings, 0 replies; 2+ messages in thread
From: Michael Schmitz @ 1999-10-21 20:36 UTC (permalink / raw)
To: Wolfgang Denk; +Cc: linuxppc-dev
On Thu, 21 Oct 1999, Wolfgang Denk wrote:
> please excuse the silly question: is there a standard way to probe an
> address if it is readable/writable memory? Ideally something that is
> portable across all architectures?
Look at what copy_to_user or copy_from_user does to set up a temporary
page fault handler, so to speak. m68k has hwreg_present() so I'd start by
translating that to ppc assembly.
Michael
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1999-10-21 20:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-10-21 19:28 Probing for (non-existing) memory? Wolfgang Denk
1999-10-21 20:36 ` Michael Schmitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).