From: Rob Landley <rob@landley.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: The OpenBIOS Mailinglist <openbios@openbios.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] svn 6658 broke powerpc.
Date: Sat, 28 Mar 2009 15:41:28 -0500 [thread overview]
Message-ID: <200903281541.29956.rob@landley.net> (raw)
In-Reply-To: <f43fc5580903271159p704263f9xaac3710793925323@mail.gmail.com>
On Friday 27 March 2009 13:59:36 Blue Swirl wrote:
> On 3/25/09, Rob Landley <rob@landley.net> wrote:
> > On Sunday 22 March 2009 11:54:22 Blue Swirl wrote:
> > > > So the bug was introduced (or at least triggered) by revision 452:
> > > >
> > > >
> > > > http://tracker.coreboot.org/trac/openbios/changeset/452/openbios-dev
> > > >el
> > > >
> > > > Anything in there look broken to you?
> > >
> > > Fixed in r481. I removed the PCI encode-unit/decode-unit methods for
> > > non-bus devices, now get-instance-path works.
> >
> > Cool!
> >
> > Is there a procedure to ask how to queue this up for qemu 0.10.2? :)
>
> Technically the best solution would be to introduce a stable tree also
> to OpenBIOS like Qemu. But OpenBIOS development is not as fast paced
> as Qemu, so I'm not sure if it's worth the effort.
>
> I can commit the latest version to Qemu SVN and if there are no
> issues, update the version in stable before release.
>
> > Rob
> >
> > (By the way: qemu is shipping a gpled bios binary without accompanying
> > source code. I realize that the maintainer of said binary checked it in,
> > but what exactly is the rationale here?)
>
> I see it as a service for both OpenBIOS and Qemu development
> communities, also the casual users don't have to install cross
> compilers just to try the Sparc/PPC emulators. The binaries are
> compiled from unmodified sources as indicated in the README.
>
> If someone finds problems with this, it's easy to put the binaries to
> OpenBIOS site and remove them from Qemu SVN. That would make bisecting
> a bit harder. Or Qemu could just include the OpenBIOS tree, it's only
> 12M.
I'm not complaining, I just tend to pay attention to license issues.
If qemu is never going to try to enforce its license, it probably doesn't
matter. If it _does_ and the other side can point to you guys not honoring
your own license terms, you may have a hard time getting them to.
Most likely you guys fall under GPLv2 section 3c anyway. Commercial
redistributors of qemu might have to include the openbios source in addition
to the qemu source (and maybe the bochs bios source, who knows?) But the
qemu project itself probably doesn't.
Rob
prev parent reply other threads:[~2009-03-28 22:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 23:57 [Qemu-devel] svn 6658 broke powerpc Rob Landley
2009-03-18 8:41 ` Alexander Graf
2009-03-18 18:28 ` Rob Landley
2009-03-18 19:11 ` Blue Swirl
2009-03-19 3:16 ` Rob Landley
2009-03-19 17:48 ` Blue Swirl
2009-03-19 19:30 ` Rob Landley
2009-03-19 19:41 ` Blue Swirl
2009-03-21 9:32 ` Blue Swirl
2009-03-21 18:44 ` Rob Landley
2009-03-22 15:14 ` Blue Swirl
2009-03-22 16:54 ` Blue Swirl
2009-03-25 2:30 ` Rob Landley
2009-03-25 2:39 ` Anthony Liguori
2009-03-25 2:50 ` Anthony Liguori
2009-03-25 4:26 ` M. Warner Losh
2009-03-27 18:59 ` Blue Swirl
2009-03-27 19:41 ` Anthony Liguori
2009-03-28 20:41 ` Rob Landley [this message]
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=200903281541.29956.rob@landley.net \
--to=rob@landley.net \
--cc=blauwirbel@gmail.com \
--cc=openbios@openbios.org \
--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).