All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>, qemu-devel@nongnu.org
Cc: jordan.l.justen@intel.com, gleb@cloudius-systems.com
Subject: Re: [Qemu-devel] fw_cfg specification ?
Date: Wed, 11 Mar 2015 19:50:40 +0100	[thread overview]
Message-ID: <55008E80.50907@redhat.com> (raw)
In-Reply-To: <20150311152758.GU1832@HEDWIG.INI.CMU.EDU>

On 03/11/15 16:27, Gabriel L. Somlo wrote:
> Hi,
> 
> I'm looking for the closest thing to an official spec for qemu's
> fw_cfg device, and so far I have found this:
> 
> http://lists.gnu.org/archive/html/qemu-devel/2011-04/msg00238.html
> 
> but it apparently never got committed to qemu (any idea why not?).

Must have fallen through the cracks. (Just speculating; in April 2011 I
had been with RH for less than half a year, and learning Xen. :))

> Googling around didn't get me much further than that.
> 
> Is there anything better or more up to date floating around out
> there somewhere ?

I won't say "better", but it is "committed": check
"Documentation/devicetree/bindings/arm/fw-cfg.txt" in the kernel tree.
It is intentionally vague on the set of keys and fw_cfg files that qemu
provides, because that's a moving target. You can only rely on the qemu
source for those.

Also, I updated Gleb's email address in the CC: header.

If you have a ton of time, you could try documenting fw_cfg yourself,
but as I said, it's a moving target, so the description would either
become stale quickly, or require people to keep it in sync with the
source all the time. Updating documentation sucks *hard*.

(At one point I had also started a text file like Jordan's, but I didn't
even get as far as posting it anywhere; I just gave up.)

Thanks
Laszlo

  reply	other threads:[~2015-03-11 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 15:27 [Qemu-devel] fw_cfg specification ? Gabriel L. Somlo
2015-03-11 18:50 ` Laszlo Ersek [this message]
2015-03-11 20:45   ` Gabriel L. Somlo
2015-03-11 21:30     ` Laszlo Ersek
2015-03-12  7:47       ` Gerd Hoffmann
2015-03-12 14:17       ` Paolo Bonzini
2015-03-12 15:42         ` Laszlo Ersek
2015-03-12 16:16           ` Gabriel L. Somlo
2015-03-12 16:35             ` Paolo Bonzini

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=55008E80.50907@redhat.com \
    --to=lersek@redhat.com \
    --cc=gleb@cloudius-systems.com \
    --cc=gsomlo@gmail.com \
    --cc=jordan.l.justen@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.