linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Zaurus: Fix PROM partition table for spitz
Date: Thu, 22 Oct 2009 23:45:11 +0200	[thread overview]
Message-ID: <20091022214511.GB9364@elf.ucw.cz> (raw)
In-Reply-To: <f17812d70910221433x27998c6do4617d2b259d6ef90@mail.gmail.com>

On Fri 2009-10-23 05:33:27, Eric Miao wrote:
> On Fri, Oct 23, 2009 at 5:13 AM, Stanislav Brabec <utx@penguin.cz> wrote:
> > Eric Miao wrote:
> >> I'm a bit upset that some things else may depend on the original
> >> layout (though that's incorrect), and this possibly breaks the
> >> sequence numbering of /dev/mtd?.
> >
> > It can break in many ways, e. g. by compiling one as module and another
> > into kernel, and depends on order of modules load.
> >
> > That is why software should search partitions by name.
> >
> 
> But there might be software that doesn't. I'd be a little bit
> conservative about this.
> 
> > AFAIK, nothing uses the EN-JP or initial bootloader data in the 2.6.x
> > distros, so it should be just safe housekeeping.
> >
> 
> This, on the other hand, says it's also safe not to inserting
> some additional partition in between :-)
> 
> (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.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-10-22 21:45 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 [this message]
2009-10-22 22:09         ` Stanislav Brabec

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=20091022214511.GB9364@elf.ucw.cz \
    --to=pavel@ucw.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 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).