qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PPC emulation on Qemu
Date: Thu, 19 Feb 2004 04:33:42 +0100	[thread overview]
Message-ID: <1077161621.17685.28.camel@rapid> (raw)
In-Reply-To: <1077158928.20789.203.camel@gaston>

On Thu, 2004-02-19 at 03:48, Benjamin Herrenschmidt wrote:
> On Thu, 2004-02-19 at 13:32, J. Mayer wrote:
> > On Thu, 2004-02-19 at 02:57, Benjamin Herrenschmidt wrote:
> > > > > If you look at the MOL bk web front end, you'll see an openbios dir
> > > > > in there)
> > > > 
> > > > Yep, I've already seen it, but I can't get the a copy of this
> > > > repository. But I saw it's a copy of a CVS tree. Is this tree available
> > > > somewhere ?
> > > 
> > > I don't know about CVS. What's wrong with bk clone ?
> > 
> > No sources, no specs... 
> 
> Do bk -r get once you have cloned the tree to checkout the files
> 
> > Cannot compile it => cannot install to use it,
> > neither can I write a free client...
> > Want to keep my machine and my mind safe and free from those kind of
> > softwares...
> 
> Heh... There may be an rsync mirror, I don't know

I hope ! That's what I'm looking for !
There's a CVS at openbios.org, but it's not up-to-date, for PPC support.
And:
\> rsync -avz rsync.penguinppc.org::
linux-2.4-benh  Ben's 2.4 Tree (aka, the PowerMac tree)
mol             Mac-On-Linux Source
libmol          Binary MOL Support Files
yaboot          Yaboot 1.3.x Development Tree (yaboot--devel--1.3)
yaboot-unstable Yaboot 1.99 Development Tree (yaboot--devel--1.99)
prom-libc       Prom-libc 1.0 Development Tree (prom-libc--devel--1.0)
No luck, no open-bios there...

-- 
J. Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2004-02-19  3:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 11:17 [Qemu-devel] PPC emulation on Qemu Manish Bansal
2004-02-15 14:07 ` J. Mayer
2004-02-15 14:59   ` Gabriel Ebner
2004-02-15 16:06     ` J. Mayer
2004-02-15 22:44       ` Benjamin Herrenschmidt
2004-02-16  3:34         ` J. Mayer
2004-02-16  4:08           ` Benjamin Herrenschmidt
2004-02-16  4:27             ` J. Mayer
2004-02-16  7:09               ` Benjamin Herrenschmidt
2004-02-18  9:42                 ` J. Mayer
2004-02-18 10:35                   ` J. Fortmann
2004-02-18 13:20                     ` Jocelyn Mayer
2004-02-18 23:13                       ` Benjamin Herrenschmidt
2004-02-19  0:59                         ` J. Mayer
2004-02-19  1:57                           ` Benjamin Herrenschmidt
2004-02-19  2:32                             ` J. Mayer
2004-02-19  2:48                               ` Benjamin Herrenschmidt
2004-02-19  3:33                                 ` J. Mayer [this message]
2004-02-19  4:27                                   ` Benjamin Herrenschmidt
2004-02-16  7:20               ` Gwenole Beauchesne
2004-02-16  7:46                 ` Chad Page

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=1077161621.17685.28.camel@rapid \
    --to=l_indien@magic.fr \
    --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).