public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jie Zhang <jie.zhang@analog.com>
To: David Howells <dhowells@redhat.com>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
	linux-kernel@vger.kernel.org, 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, 5 Dec 2009 08:28:26 +0800	[thread overview]
Message-ID: <4B19A92A.5030804@analog.com> (raw)
In-Reply-To: <14959.1259948697@redhat.com>

On 12/05/2009 01:44 AM, David Howells wrote:
> Mike Frysinger<vapier@gentoo.org>  wrote:
>
>> 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.
>
> Now that I've ACK'd this, I feel I'm going to have to NAK it.  I'm not against
> the general concept, but:
>
>> +		do_munmap(mm, *maddr, phdr->p_memsz + *disp);
>
> There needs to be a mapping covering the SRAM region for the purposes of the

Our GDB is still lack of the feature to debug applications using SRAM. 
So this part of code was not got exercised. So if we remove this line, 
can this patch got merged?

> debugger.  Do you have a chardev covering the SRAM device?  Perhaps through
> MTD?
>
Sorry, I don't know the answer to these two questions.


Jie



  reply	other threads:[~2009-12-05  0:29 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
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 [this message]
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=4B19A92A.5030804@analog.com \
    --to=jie.zhang@analog.com \
    --cc=davidm@snapgear.com \
    --cc=dhowells@redhat.com \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uclinux-dev@uclinux.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.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