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

On Sunday 01 June 2008 19:25:11 Mike Frysinger wrote:
> On Sun, Jun 1, 2008 at 8:03 PM, Rob Landley wrote:
> > On Saturday 31 May 2008 07:44:14 Phil Wilshire wrote:
> >> I hope this is the right place and the right sort of question.
> >>
> >> I work closely with the Blackfin systems and they have now integrated
> >> the initramfs generation into their system build. The result is great
> >> the root fs is ready to run from the page cache.
> >
> > Is it possible to get blackfin working with a vanilla gcc release yet, or
> > do you still need out-of-tree patches?  (I have a blackfin board I got at
> > OLS, but it needs a toolchain I can't reproduce.)
>
> there's plenty of usable binaries available

I like to build things from source.  (I'm funny that way, I realize this is 
totally out of place when dealing with Linux, but it's what I do.)  I also 
like to use vanilla release packages where possible, and failing that a patch 
against against the release version.  (Again, a personal idiosyncrasy...)

To me, saying "you need this binary-only toolchain to build" is like 
saying "you need this binary-only driver to boot".

> > 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), 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 guessing that's why your qemu blackfin work on wh0rd.net stalled last 
year?

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

  parent reply	other threads:[~2008-06-03 20:59 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 [this message]
2008-06-03 21:54       ` Mike Frysinger
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=200806031559.55526.rob@landley.net \
    --to=rob@landley.net \
    --cc=linux-embedded@vger.kernel.org \
    --cc=pwilshire@cox.net \
    --cc=vapier.adi@gmail.com \
    /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).