From: "Jonathan Kalbfeld" <jonathan.kalbfeld@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Porting QEMU to PalmOS
Date: Thu, 24 May 2007 16:33:26 -0700 [thread overview]
Message-ID: <db7b3ca90705241633i5818b501la0657461acfdb897@mail.gmail.com> (raw)
In-Reply-To: <865259.82695.qm@web54601.mail.re2.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 3974 bytes --]
Still sounds fantistically fun.
Maybe you can point me in the right direction to write PalmOS programs
(.prc's right?).
I have some goofy ideas for things to write for my Treo.
jonathan
On 5/24/07, sinisa marovic <sinisamarovic@yahoo.com> wrote:
>
> I'm afraid I will have to dissapoint you: it will be only isapc with no
> networking or other fancy devices. Main goal is the ability to run dos
> games.
> I do not know how familiar are you with PalmOS developer support. It
> is poor, gcc lack many important functions that have to be written from
> scratch. When I ported dosbox (which is written in c++) I realized that
> there is no support for vectors, iterators, namespaces etc, so I had to
> write many operators myself. The biggest problem with QEMU is that
> it uses signals a lot, and, guess what, PalmOS has no support for signals
> _at_ _all_. I found a way to get things going without them for now, but
> this has it's drawbacks. I will have to think about something better later
> on.
>
> ----- Original Message ----
> From: Jonathan Kalbfeld <jonathan.kalbfeld@gmail.com>
> To: qemu-devel@nongnu.org
> Sent: Thursday, May 24, 2007 11:18:48 PM
> Subject: Re: [Qemu-devel] Porting QEMU to PalmOS
>
> One definite plus with having QEMU for PalmOS is the ability to run things
> like OpenVPN (even if slow) and connect to a VPN back-end.
>
> As is, I use OpenVPN tunnels to link up my QEMU machines on Solaris.
>
> jonathan
>
> On 5/23/07, Wolfgang Schildbach <
> Wolfgang.Schildbach@codingtechnologies.com> wrote:
> >
> > Try compiling as position-dependent (i.e. not PIC) code. GOT is a
> > typical
> > feature of position independent code.
> >
> > - Wolfgang
> >
> > qemu-devel-bounces+wolfgang.schildbach=codingtechnologies.com@nongnu.org
> > wrote on 23.05.2007 13:20:22:
> >
> > > Hi Johannes,
> > >
> > > thanks for your quick response.
> > > I thought QEMU was already compiled and run on an ARM machine?
> > > If so, how come that noone else had such problem (I searched for it
> > > on google),
> > > and PXA255 is a standard ARM CPU with a few additional instructions.
> > > And how to make them not come from GOT, those vars are declared as
> > extern,
> > > so they are globals?
> > >
> > > BR,
> > > Voda.
> >
> > > ----- Original Message ----
> > > From: Johannes Schindelin < Johannes.Schindelin@gmx.de>
> > > To: sinisa marovic <sinisamarovic@yahoo.com>
> > > Cc: qemu-devel@nongnu.org
> > > Sent: Wednesday, May 23, 2007 12:48:59 PM
> > > Subject: Re: [Qemu-devel] Porting QEMU to PalmOS
> >
> > > Hi,
> > >
> > > On Wed, 23 May 2007, sinisa marovic wrote:
> > >
> > > > Relocation types that fail are 25 and 26, which are R_ARM_GOTPC and
> > > > R_ARM_GOT32 respectively. Their names are:
> > > >
> > > > _GLOBAL_OFFSET_TABLE_
> > > > cc_table
> > > > __op_param1
> > > > __op_param2
> > > > __op_param3
> > > >
> > > > Is there a way to fix this?
> > >
> > > The GOT is an offset table. Many CPUs have fixed-size instruction
> > sets,
> > > which means that you cannot easily jump to an absolute address, since
> > the
> > > address alone would already fill up the size.
> > >
> > > Of course, this is a no-no for QEmu, since the _same_ function snippet
> > > will be reused _multiple_ times. So, the address must not come from a
> > GOT,
> > > but be inserted directly into the code.
> > >
> > > I do not remember off-hand how I managed to do this a couple of years
> > ago,
> > > when I worked on a MIPS host, but there _are_ gcc options to avoid a
> > GOT.
> > >
> > > Hth,
> > > Dscho
> > >
> > >
> > > Food fight? Enjoy some healthy debate
> > > in the Yahoo! Answers Food & Drink Q&A.
> >
> >
> >
> >
>
>
> --
> --
> Jonathan Kalbfeld
> +1 323 620 6682
>
>
> ------------------------------
> Get the free Yahoo! toolbar<http://us.rd.yahoo.com/evt=48226/*http://new.toolbar.yahoo.com/toolbar/features/norton/index.php>and rest assured with the added security of spyware protection.
>
--
--
Jonathan Kalbfeld
+1 323 620 6682
[-- Attachment #2: Type: text/html, Size: 7211 bytes --]
next prev parent reply other threads:[~2007-05-24 23:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 23:19 [Qemu-devel] Porting QEMU to PalmOS sinisa marovic
2007-05-24 23:33 ` Jonathan Kalbfeld [this message]
2007-05-25 5:37 ` Jason Brand
-- strict thread matches above, loose matches on Subject: below --
2007-06-04 15:33 sinisa marovic
2007-07-01 12:29 ` andrzej zaborowski
2007-07-01 17:20 ` Luke-Jr
2007-07-01 18:08 ` Johannes Schindelin
2007-07-01 18:16 ` andrzej zaborowski
2007-05-24 23:47 sinisa marovic
2007-05-23 11:20 sinisa marovic
2007-05-23 15:23 ` Wolfgang Schildbach
2007-05-23 22:02 ` Jonathan Kalbfeld
2007-05-24 21:18 ` Jonathan Kalbfeld
2007-05-23 9:07 sinisa marovic
2007-05-23 10:48 ` Johannes Schindelin
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=db7b3ca90705241633i5818b501la0657461acfdb897@mail.gmail.com \
--to=jonathan.kalbfeld@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).