qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gautam Bhat <mindentropy@gmail.com>
To: qemu-devel@nongnu.org
Subject: Pain points in Software Virtual Development
Date: Sun, 14 Jun 2020 13:07:28 +0530	[thread overview]
Message-ID: <CAM2a4uw6J_+w9i6cN-Qfuyiq58_+vFqiBFrrx+A7hq7appo-4w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 578 bytes --]

Hi All,

I am interested in knowing what are the pain points in using Qemu as a
Software Virtual Development Platform from not only CPU perspective but a
complete PCB (CPU + different peripherals).

In most of the engineering firms that I have worked at, the PCB board was
the problem. There would either be a lack of boards due to costs, systems
being bulky etc. All these could easily be emulated using Qemu.

Is Qemu lacking a good way to model the entire system quickly to start with
BSP and application software development?

Any help would be appreciated.

Thanks,
Gautam

[-- Attachment #2: Type: text/html, Size: 1489 bytes --]

                 reply	other threads:[~2020-06-14  7:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAM2a4uw6J_+w9i6cN-Qfuyiq58_+vFqiBFrrx+A7hq7appo-4w@mail.gmail.com \
    --to=mindentropy@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).