linux-kernel - Re: [PATCH 1/4] Blackfin: arch patch for 2.6.18

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a0609230435k702806e6h38578258dcfefc85@mail.gmail.com>
Date:	Sat, 23 Sep 2006 07:35:38 -0400
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	"Matthieu CASTET" <castet.matthieu@...e.fr>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] Blackfin: arch patch for 2.6.18

On 9/23/06, Matthieu CASTET <castet.matthieu@...e.fr> wrote:
> On Sat, 23 Sep 2006 02:50:02 -0400, Mike Frysinger wrote:
> >> It would be nice if you could use a generic way to pass this partition data
> >> to the kernel from the mtd medium, instead of hardcoding it here.
> >
> > i often wish for such things myself :)
> >
> > unfortunately, the boot loader we utilize (u-boot) isnt exactly
> > friendly to the idea of managing flash partitions like redboot, and
> > what we have here is the current standard method for defining flash
> > partitions with mtd
>
> humm you could use cmdlinepart [1] and pass the partition as a kernel
> string with uboot.
>
> That's what we are doing and it works perfectly.

yes, that is an option ... we find that utilizing the board files "better" as:
 - the boot syntax tends to be a little unwieldy
 - embedded boards dont change, so if you're defining so much
board-specific information in the boards file, the partition map makes
sense there as well
 - the dynamic partitioning aspect of declaring the map at runtime is
unnecessary due to the previous comment

but each to their own i guess
-mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/