All of lore.kernel.org
 help / color / mirror / Atom feed
From: utx@penguin.cz (Stanislav Brabec)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Zaurus: Fix PROM partition table for spitz
Date: Fri, 23 Oct 2009 00:09:48 +0200	[thread overview]
Message-ID: <1256249388.1986.0@zaurus> (raw)
In-Reply-To: <20091022214511.GB9364@elf.ucw.cz> (from pavel@ucw.cz on Thu Oct 22 23:45:11 2009)

On 2009-10-29 23:45:11 Pavel Machek wrote:
> On Fri 2009-10-23 05:33:27, Eric Miao wrote:
> > (I won't refuse some comments to make this more clear in the code
> > though).
> 
> I don't know. If the table is wrong, we should fix it. Yes, it may
> break someone, but it probably will not.

This change is not worse than change in .config, as there is no
guarantee of order of loading NAND and PROM maps.

I just looked at original 2.4 kernel. There were:
PROM EN-JP as "Filesystem", bootloader not mapped
NAND partitions as "smf", "root", "home"

This is an output of cat /proc/mtd on vendor's 2.4.20.

dev:    size   erasesize  name
mtd0: 006b0000 00020000 "Filesystem"
mtd1: 00700000 00020000 "smf"
mtd2: 02b00000 00020000 "root"
mtd3: 04e00000 00020000 "home"

We never were compatible:

Guessing from "file" output, EN-JP partition is just a file, not a
filesystem. I am OK with keeping of name "Boot PROM Filesystem" and
calling the new partition as "PROM Bootloader", but EN-JP in the name
cleanly describes the surprising contents. Adding bootloader data
partition has probably a single use case: Being easily able to grab
the PROM contents for the emulator.

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus

      reply	other threads:[~2009-10-22 22:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 20:58 [PATCH] Zaurus: Fix PROM partition table for spitz Stanislav Brabec
2009-10-22 21:05 ` Eric Miao
2009-10-22 21:13   ` Stanislav Brabec
2009-10-22 21:33     ` Eric Miao
2009-10-22 21:45       ` Pavel Machek
2009-10-22 22:09         ` Stanislav Brabec [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=1256249388.1986.0@zaurus \
    --to=utx@penguin.cz \
    --cc=linux-arm-kernel@lists.infradead.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.