DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=ETR5uf7erYQJpUyv8k7SxVr/S4zHQBQWvp9pJYdVc3l0BodWunYKVV04qEbGIAmDwD
         WHB18MnYCgfKlA5jmv/ePY1NYg7unASeebcy3C7hGELwiUsmVHxeaMGx/UTyAqHkJhMB
         5SaHFdyN+2sgebKhlfghSlf+/7Do8tW1ke8NE=
MIME-Version: 1.0
In-Reply-To: <20090613161323.GC16220@shareable.org>
References: <1244854869-2563-1-git-send-email-vapier@gentoo.org> 
	<20090613161323.GC16220@shareable.org>
From: Mike Frysinger <vapier.adi@gmail.com>
Date: Sat, 13 Jun 2009 12:40:45 -0400
Message-ID: <8bd0f97a0906130940j6b5e578bha8193f59d03c2f05@mail.gmail.com>
Subject: Re: [uClinux-dev] [PATCH/RFC] FDPIC: add hook for arches to customize 
	program header parsing
To: Jamie Lokier <jamie@shareable.org>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
       linux-kernel@vger.kernel.org, Jie Zhang <jie.zhang@analog.com>,
       Greg Ungerer <gerg@uclinux.org>,
       uclinux-dist-devel@blackfin.uclinux.org,
       David McCullough <davidm@snapgear.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1294
Lines: 29

On Sat, Jun 13, 2009 at 12:13, Jamie Lokier wrote:
> Mike Frysinger wrote:
>> From: Jie Zhang <jie.zhang@analog.com>
>>
>> The Blackfin port has custom program header flags/addresses for
>> automatically loading regions into the dedicated on-chip SRAM.  So add a
>> hook for ports to leverage.
>
> What does this have to do with FDPIC?  I don't see anything that is
> specific to FDPIC about this code, other than FDPIC being the type of
> ELF used on Blackfin.  If an MMU were added to some future Blackfins,
> wouldn't this code be used for non-FDPIC ELF too?

no, because with a MMU, the memory would be virtualized and we could
handle it dynamically

> It looks like a way for certain special executables to load themselves
> into fixed regions of the on-chip SRAM - and promptly crash if another
> executable does the same.  Not so much a general executable format, as
> a hack to load something specific which should only be done once at a
> time.  What am I missing here?

the addresses are keys, not fixed and/or "real" addresses
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/