All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Zaurus: make updater.sh obsolete for poodle, clamshells and tosa
Date: Sun, 17 Jan 2010 20:42:52 +0100	[thread overview]
Message-ID: <hivp7t$hib$1@ger.gmane.org> (raw)
In-Reply-To: <d1b08f941001170606w13dcfc0ey341da93deb94c7b8@mail.gmail.com>

Andrea Adami wrote:
> Well, there are very good reasons to make this now obsolete:
> - we can flash from console (2.6 userspace)
> - we have a different image-layout (kernel in /boot), thus we can boot
> from every hd partition
> - we can create jffs2 images (see Narcissus) and flash these from
> console, without striping the legacy headers. We can even have 2
> images in nand

Great.  Would be nice to see this documented somewhere in the wiki in a
language that mere humans understand.  I'll volunteer as tester.  I
think I'm stupid enough to qualify ;-)




      parent reply	other threads:[~2010-01-17 19:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17 14:06 [RFC] Zaurus: make updater.sh obsolete for poodle, clamshells and tosa Andrea Adami
2010-01-17 19:13 ` Marcin Juszkiewicz
2010-01-17 19:58   ` Yuri Bushmelev
2010-01-17 23:59     ` Andrea Adami
2010-01-22 10:12       ` Andrea Adami
2010-01-22 14:57         ` Rolf Leggewie
2010-01-28 22:50           ` Andrea Adami
2010-02-01 18:24             ` Andrea Adami
2010-02-01 21:57               ` Andrea Adami
2010-02-01 23:21                 ` Rolf Leggewie
2010-02-01 23:47                   ` Graeme Gregory
2010-02-06 23:09                     ` Andrea Adami
2010-02-07  0:18                       ` Andrea Adami
2010-05-03 12:37                         ` Andrea Adami
2010-01-17 19:42 ` Rolf Leggewie [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='hivp7t$hib$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --cc=openembedded-devel@lists.openembedded.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 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.