From: Jamie Lokier <jamie@shareable.org>
To: Mike Frysinger <vapier.adi@gmail.com>
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>
Subject: Re: [uClinux-dev] [PATCH/RFC] FDPIC: add hook for arches to customize program header parsing
Date: Sat, 13 Jun 2009 19:25:40 +0100 [thread overview]
Message-ID: <20090613182540.GJ16220@shareable.org> (raw)
In-Reply-To: <8bd0f97a0906130940j6b5e578bha8193f59d03c2f05@mail.gmail.com>
Mike Frysinger wrote:
> 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
Wouldn't you still want to put some things into local L1 SRAM, using thos, perhaps by
flagging it instead of
> > 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
Oh, I see that is indeed quite nice :-)
I see it checks for both flags and special address values. Are the
special address checks mainly historical, as usually flags/types are
used to designate special memory types in ELF.
Anyway,
Acked-By: Jamie Lokier <jamie@shareable.org>
-- Jamie
next prev parent reply other threads:[~2009-06-13 18:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 1:01 [PATCH/RFC] FDPIC: add hook for arches to customize program header parsing Mike Frysinger
2009-06-13 12:23 ` [uClinux-dev] " David Howells
2009-06-13 16:13 ` Jamie Lokier
2009-06-13 16:40 ` Mike Frysinger
2009-06-13 18:25 ` Jamie Lokier [this message]
2009-06-13 18:26 ` Jamie Lokier
2009-06-14 0:32 ` Mike Frysinger
2009-06-14 0:42 ` Jie Zhang
2009-06-14 9:43 ` Paul Mundt
2009-06-15 1:43 ` Greg Ungerer
2009-06-16 8:24 ` [PATCH] " Mike Frysinger
2009-06-23 5:32 ` Andrew Morton
2009-06-23 11:04 ` Mike Frysinger
2009-12-04 17:44 ` [uClinux-dev] [PATCH/RFC] " David Howells
2009-12-05 0:28 ` Jie Zhang
2009-12-05 15:14 ` David Howells
2009-12-07 10:09 ` Mike Frysinger
2009-12-07 3:27 ` [Uclinux-dist-devel] " Zhang, Sonic
2009-12-07 10:10 ` Mike Frysinger
2009-12-07 10:17 ` Jie Zhang
2009-12-07 10:10 ` Mike Frysinger
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=20090613182540.GJ16220@shareable.org \
--to=jamie@shareable.org \
--cc=davidm@snapgear.com \
--cc=gerg@uclinux.org \
--cc=jie.zhang@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dev@uclinux.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier.adi@gmail.com \
/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