From: Esteban Bosse <estebanbosse@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: BeagleBone support, omap1, omap2, omap3, etc.
Date: Tue, 3 Dec 2019 16:24:11 +0100 [thread overview]
Message-ID: <CAGbAg_A5G2trFWEuAL2da169v=XFrS44g64F6yZo5phLC+T=PQ@mail.gmail.com> (raw)
In-Reply-To: <CAGbAg_CAh-U-xRh+d6wNLQVWoHXEA0xcW6021Qd4WsMJBGfgOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Ping
El mié., 6 nov. 2019 16:04, Esteban Bosse <estebanbosse@gmail.com> escribió:
> Hello!
>
> Some months ago I started to work trying to port the Beaglebone support
> from the old qemu-linaro fork to the new QEMU mainstream.
>
> During my work I found that the Beaglebone have an OMAP3 mpu this mpu has
> very strong relation with the OMAP2 and OMAP1 in qemu, they implement a lot
> of functions in common.
>
> Then I understood that the omap1 and omap2 don't implement things like QOM
> and needs a lot of work to upgrade it, at the same time they are some
> boards like: omap1_sx, palm, nseries that implement this mpus.
>
> Looking the datasheet of the omap1 I realized that it's an very old device
> and some questions like "make sense work with this old device?" comes to my
> mind.
>
> When I went to the KVM Forum the last week I talked with some of you, and
> you help my with different ideas and proposal to make this task, but I
> can't see the right way to make this work because it is a lot of work.
>
> My motivation is learn more about embedded devices, architecture, kernel,
> etc. and of course contribute to the community.
>
> I would love to hear your opinions about this 3 related devices with they
> respected boards.
>
> Maybe someone is interested to work with me.
> I dream to make this work beautiful (like the musca board with the armsse
> and armv7m modules) with a good variety of tests. And in the same time I
> would like to write some documentation about the process with the final
> idea to "make an easier way for new contributors".
>
> If someone want to work with me in this task, should know that I don't
> have to much experience and I'm doing this job in my free time (this means
> that I work only in my free time).
>
> I appreciate any kind of comment or advice.
>
> Thanks for your time ;)
> EstebanB
>
[-- Attachment #2: Type: text/html, Size: 2198 bytes --]
next prev parent reply other threads:[~2019-12-03 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 15:04 BeagleBone support, omap1, omap2, omap3, etc Esteban Bosse
2019-12-03 15:24 ` Esteban Bosse [this message]
2019-12-10 9:55 ` Philippe Mathieu-Daudé
2019-12-10 19:51 ` Niek Linnenbank
2019-12-11 10:24 ` Esteban Bosse
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='CAGbAg_A5G2trFWEuAL2da169v=XFrS44g64F6yZo5phLC+T=PQ@mail.gmail.com' \
--to=estebanbosse@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.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).