linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: pwilshire@cox.net, linux-embedded@vger.kernel.org
Subject: Re: initramfs size limitation
Date: Tue, 3 Jun 2008 17:54:38 -0400	[thread overview]
Message-ID: <8bd0f97a0806031454g6d8fe57ahca942b2a81b737aa@mail.gmail.com> (raw)
In-Reply-To: <200806031559.55526.rob@landley.net>

On Tue, Jun 3, 2008 at 4:59 PM, Rob Landley wrote:
> On Sunday 01 June 2008 19:25:11 Mike Frysinger wrote:
>> On Sun, Jun 1, 2008 at 8:03 PM, Rob Landley wrote:
>> > fact it would be really nice if qemu grew blackfin support because
>> > messing
>>
>> i imagine it would be ... too bad qemu lacks real documentation
>
> Actually there was documentation on the old stuff if you knew where to dig it
> up (a good starting point was Fabrice's old usenix paper and then I had some
> links I'd collected from there)

yes, but spotiness doesnt help

> but they just ripped out the old code
> generator in favor of a new one
> (See http://lists.gnu.org/archive/html/qemu-devel/2008-02/msg00011.html ) so
> there's not much point in going there right now.  (Hopefully they'll have a
> 1.0 release within our lifetimes.)

i'm aware the tcg stuff exists, but that's about it.  only hope for
new ports atm is to contract a qemu guy.  not that the qemu guys would
mind.  thanks for the link.
-mike

  reply	other threads:[~2008-06-03 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31 12:44 initramfs size limitation Phil Wilshire
2008-06-02  0:03 ` Rob Landley
2008-06-02  0:25   ` Mike Frysinger
2008-06-02  0:42     ` Bryan Wu
2008-06-03 20:59     ` Rob Landley
2008-06-03 21:54       ` Mike Frysinger [this message]
2008-06-04 17:24         ` Rob Landley

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=8bd0f97a0806031454g6d8fe57ahca942b2a81b737aa@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=pwilshire@cox.net \
    --cc=rob@landley.net \
    /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).