All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Locke <mlocke@mvista.com>
To: David Blythe <blythe@routefree.com>
Cc: Steve Hein <ssh@sgi.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: mkcramfs changes to switch endianness
Date: Thu, 03 May 2001 11:48:56 -0700	[thread overview]
Message-ID: <3AF1A818.DE019F5B@mvista.com> (raw)
In-Reply-To: 3AF1A44C.75BA4186@routefree.com


David Blythe wrote:
>
> Steve Hein wrote:
>
> > Just out of curiousity, where do you get the source for the transmeta
> > changes (their Midora Linux, I assume....).  I went looking at their
> > web site, and the FTP location they pointed to contained a
> > midora-1.0.0-beta1*.tar.gz file that was only 36K.....where's the real
> > thing?

that file is just the build structure/files.  once you install that you
need to download the rest from the apps dir on the ftp site.  start at
http://midori.sourceforge.net.

>
> We used this, as a starting point (or one of the other references to
> this patch, i just did a google search to find it again).
>
> http://lwn.net/2001/0118/a/cramfs.php3

That is the patch include with midori.  If i remember correctly, it is
included in the kernel mlz. mlz is the midori packaging method,
basically a tar gz file.

>
> I was hoping that it was all on sourceforge, but I guess not.  We should
> finish integrating the endianness changes against this patch pretty
> soon.  Maybe if someone else knows if there is a more up to date version
> around they could let us know.


it is all there on sourceforge, just need to dig a little:)

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-05-03 18:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 20:38 mkcramfs changes to switch endianness Steven Hein
2001-05-02 20:39 ` Matthew Locke
2001-05-02 23:56 ` David Blythe
2001-05-03  2:24   ` Steve Hein
2001-05-03 18:32     ` David Blythe
2001-05-03 18:48       ` Matthew Locke [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=3AF1A818.DE019F5B@mvista.com \
    --to=mlocke@mvista.com \
    --cc=blythe@routefree.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ssh@sgi.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 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.