* Linear memory access
@ 2002-06-12 6:42 Frederic Marmond
2002-06-12 6:58 ` Konstantin Boldyshev
2002-06-12 10:36 ` Linear memory access, and register-modifier debugger Frederic Marmond
0 siblings, 2 replies; 3+ messages in thread
From: Frederic Marmond @ 2002-06-12 6:42 UTC (permalink / raw)
To: linux-assembly
hi all,
I'd like to access to a memory area on a mtd device, without having
compiling the mtd support in the kernel.
(read a firmware info, on a embeded environment => kernel as small as
possible)
Is there any isue?
I mean:
is the device mapped anywhere, or is it really invisible, if i don't
compile the mtd support?
If it is visible (how can i check that point?) do you know if there is
any way to access it (like in flat mode, by a largest descriptor or
something...)?
thanks for answers!
Fred
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Linear memory access
2002-06-12 6:42 Linear memory access Frederic Marmond
@ 2002-06-12 6:58 ` Konstantin Boldyshev
2002-06-12 10:36 ` Linear memory access, and register-modifier debugger Frederic Marmond
1 sibling, 0 replies; 3+ messages in thread
From: Konstantin Boldyshev @ 2002-06-12 6:58 UTC (permalink / raw)
To: linux-assembly
On Wed, 12 Jun 2002, Frederic Marmond wrote:
> I'd like to access to a memory area on a mtd device, without having
> compiling the mtd support in the kernel.
> (read a firmware info, on a embeded environment => kernel as small as
> possible)
> Is there any isue?
>
> I mean:
> is the device mapped anywhere, or is it really invisible, if i don't
> compile the mtd support?
> If it is visible (how can i check that point?) do you know if there is
> any way to access it (like in flat mode, by a largest descriptor or
> something...)?
It should be visible, but you need to know its address.
If you want to access it from userspace, use /dev/mem.
(from kernelspace all is as usual).
--
Regards,
Konstantin
^ permalink raw reply [flat|nested] 3+ messages in thread
* Linear memory access, and register-modifier debugger
2002-06-12 6:42 Linear memory access Frederic Marmond
2002-06-12 6:58 ` Konstantin Boldyshev
@ 2002-06-12 10:36 ` Frederic Marmond
1 sibling, 0 replies; 3+ messages in thread
From: Frederic Marmond @ 2002-06-12 10:36 UTC (permalink / raw)
To: linux-assembly
I'm sorry to send it again, but I had troubles with my suscribtion,
obliged to re-suscribe to the list
So, (as the archive is down) i couldn't read any (if any) answer...
could you please re-post me answer if, if you have one...
by the way:
I'm looking for a debugger capable of changing registers while
executing the code (during a break-point for exemple), or/and best,
modifying the code itself in memory.
for the code
brk :08048081 6689c0 mov ax, ax
when steping to this breakpoint, filling the 6689c0 by 909090, to
disable this wonderfull instruction, and step to the following! ;-)
ok, I know, there are 'pro' debuggers under windows.
I've use turboDebugger (borland, under dos) from my young time...
but now, under GNU/linux, I miss it!
(perhapse that under Linux, there is no bug at all, opposate to
windows... ;-))
thanks in advance!
Fred
> Hi all,
>
> I'd like to access to a memory area on a mtd device, without having
> compiling the mtd support in the kernel.
> (read a firmware info, on a embeded environment => kernel as small as
> possible)
> Is there any isue?
>
> I mean:
> is the device mapped anywhere, or is it really invisible, if i don't
> compile the mtd support?
> If it is visible (how can i check that point?) do you know if there is
> any way to access it (like in flat mode, by a largest descriptor or
> something...)?
>
>
> thanks for answers!
>
> Fred
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-06-12 10:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-06-12 6:42 Linear memory access Frederic Marmond
2002-06-12 6:58 ` Konstantin Boldyshev
2002-06-12 10:36 ` Linear memory access, and register-modifier debugger Frederic Marmond
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).