From: Marek Vasut <marek.vasut@gmail.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add Palm Tungsten|C support
Date: Wed, 14 Jan 2009 18:08:40 +0100 [thread overview]
Message-ID: <200901141808.40974.marek.vasut@gmail.com> (raw)
In-Reply-To: <20090114161725.GL26085@game.jcrosoft.org>
On Wednesday 14 of January 2009 17:17:25 Jean-Christophe PLAGNIOL-VILLARD
wrote:
> On 17:23 Wed 14 Jan , Marek Vasut wrote:
> > On Wednesday 14 of January 2009 17:02:05 Jean-Christophe PLAGNIOL-VILLARD
> >
> > wrote:
> > > On 16:20 Wed 14 Jan , Marek Vašut wrote:
> > > > Hi,
> > > >
> > > > this patch adds Palm TC support. It's a PXA based handheld device
> > > > (unlike PalmTE defined in palm.c which is OMAP) so I decided to
> > > > separate these and create new palmpxa.c . Near future plan is to add
> > > > basic support for other pxa-based palm models as well. Please
> > > > consider applying.
> > >
> > > IIRC some hacker port u-boot on it maybe you could try it
> >
> > uboot on what? palmtc? Nikolay ported uboot on palmt2, I ported it to
> > palmz71. There is also port of uboot for palmt3, but there never was port
> > for palmtc. Actually PalmOS can boot to some place even on this basic
> > setup.
>
> I known about the Z71 but we report me that some hacker work on the TC but
> I never see or search the patches
Im not really sure I got your point, but I'm working on the palmtc linux port
and I know of noone else who does work in it. Also, I added some code to old
qemu fork in palmlinux project.
>
> Best Regards,
> J.
next prev parent reply other threads:[~2009-01-14 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 15:20 [Qemu-devel] [PATCH] Add Palm Tungsten|C support Marek Vašut
2009-01-14 16:02 ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-14 16:23 ` Marek Vasut
2009-01-14 16:17 ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-14 17:08 ` Marek Vasut [this message]
2009-01-14 17:26 ` Marek Vasut
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=200901141808.40974.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=plagnioj@jcrosoft.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).