From: "Alessandro Corradi" <ale.corradi@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] SystemC hw simulation in qemu
Date: Thu, 29 Jun 2006 13:33:50 +0200 [thread overview]
Message-ID: <b921df970606290433h6487acc6off27e50cb31047cb@mail.gmail.com> (raw)
In-Reply-To: <b921df970606280336j5d5e90fdi69a369acb1c765ef@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
Can someone help me about this? I've looked at exec.c source for understand
how io memory addressment go but i don't know if it's the right place to
start.
I see that in serial.c source there are IO and memory map function for read
and write, and serial_mm_read/write functions use serial_read/write
functions. The difference is the base address I see... right? Where I can
find this IO address?
And there is a serial_mm_init function. Is it used only all emulation except
i386 or can I use it for i386 too? In other words... can I use IO memory
address for serial port in 386 emulation or not?
Thanks
Ale
Ps: Be patience, I am only a poor student ;)
2006/6/28, Alessandro Corradi <ale.corradi@gmail.com>:
>
>
> ... The problem is that I write my simple hw, but instead use IOddress
> such as 0x378 I need to use memory address, so I can use it in every
> virtualizzation (i386, mips etc...).
> Where can I look for it?
>
> Thanks
> Ale
>
[-- Attachment #2: Type: text/html, Size: 1229 bytes --]
next prev parent reply other threads:[~2006-06-29 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 8:59 [Qemu-devel] SystemC hw simulation in qemu Alessandro Corradi
2006-06-19 22:54 ` Fabrice Bellard
2006-06-28 10:36 ` Alessandro Corradi
2006-06-29 11:33 ` Alessandro Corradi [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 10:46 Laurent DESNOGUES
2006-06-28 10:59 ` Alessandro Corradi
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=b921df970606290433h6487acc6off27e50cb31047cb@mail.gmail.com \
--to=ale.corradi@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).