Re: [PATCH] [RSB] Add support for building rtems-or1k tool-chain - fixed

Hi Chris, Please have a look at this patch when you have sometime. I have fixed it according to your comments. Thanks, - Hesham On Mon, May 26, 2014 at 3:40 AM, Hesham ALMatary wrote: > Configuration files get the following releases: > - binutils-2.24 > - newlib-2.1.0 > - gcc-4.8.2 > - gdb-7.7

Re: [PATCH] [RSB] Add support for building rtems-or1k tool-chain.

On Mon, May 26, 2014 at 2:45 AM, Chris Johns wrote: > On 26/05/2014 10:07 am, Hesham Moustafa wrote: > >> On Mon, May 26, 2014 at 12:57 AM, Chris Johns > <mailto:ch...@contemporary.net.au>> wrote: >> >> >> Just looking at this file I cannot see

Re: [PATCH] [RSB] Add support for building rtems-or1k tool-chain.

On Mon, May 26, 2014 at 12:57 AM, Chris Johns wrote: > On 25/05/2014 10:12 am, Hesham ALMatary wrote: > >> From: Hesham AL-Matary >> >> Configuration files get the following releases: >> - binutils-2.24 >> - newlib-2.1.0 >> - gcc-4.8.2 >> - gdb-7.7 >> >> Patches are mix of OpenRISC original patch

Re: [PATCH] [RSB] Add support for building rtems-or1k tool-chain.

On Mon, May 26, 2014 at 12:57 AM, Chris Johns wrote: > On 25/05/2014 10:12 am, Hesham ALMatary wrote: > >> From: Hesham AL-Matary >> >> Configuration files get the following releases: >> - binutils-2.24 >> - newlib-2.1.0 >> - gcc-4.8.2 >> - gdb-7.7 >> >> Patches are mix of OpenRISC original patch

Re: [RSB] possible bug - zip extracting

On Mon, May 12, 2014 at 6:54 AM, Chris Johns wrote: > On 9/05/2014 11:40 am, Chris Johns wrote: > >> On 9/05/2014 5:02 am, Hesham Moustafa wrote: >> >>> >>> When I replaced __zip with __unzip (in the previous file) I got the >>> following error:

[RSB] possible bug - zip extracting

Hi, When I was trying to add a package to be built from RSB, I came a cross an error. The package is downloaded as *.zip file. The error I got when extracting the package is (quoted from the log file): "prep: or1ksim: %setup -q -n or32-master making dir: /run/media/hesham/2cdb13e0-83ac-4ebd-9ead

Re: [GSoC] Porting RTEMS to OpenRISC - Status Report 1

On Fri, May 2, 2014 at 11:40 PM, Joel Sherrill wrote: > > On 5/1/2014 10:17 PM, Hesham Moustafa wrote: >> Hi, >> >> This is a status report of the project during last week. >> >> 1- newlib: is ported and gcc builds successfully. The only feedback I >>

Re: [GSoC] Porting RTEMS to OpenRISC - Status Report 1

On Fri, May 2, 2014 at 10:41 AM, Chris Johns wrote: > On 2/05/2014 1:17 pm, Hesham Moustafa wrote: >> >> Hi, >> >> This is a status report of the project during last week. >> >> 1- newlib: is ported and gcc builds successfully. The only feedback I >&

[GSoC] Porting RTEMS to OpenRISC - Status Report 1

Hi, This is a status report of the project during last week. 1- newlib: is ported and gcc builds successfully. The only feedback I got when I posted the newlib patch [1] is about licence of setjmp.S file. I contacted Damjan Lampret, the author of the file, asking him to change the licence as Ralf

Re: [PATCH] port newlib for or1k/rtems (avoiding GPL licence problem)

On Apr 29, 2014 7:54 AM, "Ralf Corsepius" wrote: > > On 04/29/2014 05:20 AM, Hesham Moustafa wrote: >> >> Hi, >> >> In the last few days, I have been working on porting newlib for >> or1k/rtems. Joel and Chris mentioned that the previous newlib port h

[PATCH] port newlib for or1k/rtems (avoiding GPL licence problem)

Hi, In the last few days, I have been working on porting newlib for or1k/rtems. Joel and Chris mentioned that the previous newlib port has some GPL code which conflicts with RTEMS; that's why I used this patch [1] as a starting point. I had to do some changes and additions over the patch including

Re: Possible bug at newlib/libc/rtems/sys/crt0.c sigfillset

On Mon, Apr 28, 2014 at 6:32 PM, Joel Sherrill wrote: > > On 4/28/2014 11:25 AM, Hesham Moustafa wrote: >> Thanks! These patches really help. I've already reverted back to the >> original read/write prototypes after defining __rtems__ and it works. >> Now newlib wor

Re: Possible bug at newlib/libc/rtems/sys/crt0.c sigfillset

;> >> From: rtems-devel-boun...@rtems.org [rtems-devel-boun...@rtems.org] On >> Behalf Of Joel Sherrill [joel.sherr...@oarcorp.com] >> Sent: Sunday, April 27, 2014 7:17 PM >> To: Hesham Moustafa >> Cc: rtems-devel@rtems.org &g

Re: Possible bug at newlib/libc/rtems/sys/crt0.c sigfillset

cc/newlib are build successfully. > > From: rtems-devel-boun...@rtems.org [rtems-devel-boun...@rtems.org] On Behalf > Of Joel Sherrill [joel.sherr...@oarcorp.com] > Sent: Sunday, April 27, 2014 7:17 PM > To: Hesham Moustafa > Cc: rtems-devel@rtems.org > Subject: Re: Po

Re: Possible bug at newlib/libc/rtems/sys/crt0.c sigfillset

el-boun...@rtems.org [rtems-devel-boun...@rtems.org] On Behalf > Of Joel Sherrill [joel.sherr...@oarcorp.com] > Sent: Sunday, April 27, 2014 7:17 PM > To: Hesham Moustafa > Cc: rtems-devel@rtems.org > Subject: Re: Possible bug at newlib/libc/rtems/sys/crt0.c sigfillset > > On Apr 27, 201

Possible bug at newlib/libc/rtems/sys/crt0.c sigfillset

Hi all, When I am trying to get newlib compiled while porting newlib to rtems/or1k, I met an error that confused me. The error happens for me with both: Ubuntu and Fedora. Also it arises when configuring and building a standalone newlib library (with configure --target=or1k-rtems4.11) or when buil

Re: [GSoC] Wiki page for the project

Thanks Andre. On Sat, Apr 26, 2014 at 6:10 PM, Andre Marques wrote: > Hello, > > > On 04/26/14 17:00, Hesham Moustafa wrote: >> >> Hi all, >> >> I wanna create a Wiki page for my project, but I see no clear >> instructions for dealing with the website.

[GSoC] Wiki page for the project

Hi all, I wanna create a Wiki page for my project, but I see no clear instructions for dealing with the website. Please provide me with any links and/or templates that may help. Regards, Hesham ___ rtems-devel mailing list rtems-devel@rtems.org http://w

Re: [PATCH 00/14] Removal of or32/openrisc and introduction of or1k

On Thu, Apr 24, 2014 at 12:00 AM, Joel Sherrill wrote: > > On 4/23/2014 4:57 PM, Hesham Moustafa wrote: >> On Wed, Apr 23, 2014 at 11:48 PM, Christian Svensson >> wrote: >>> On Wed, Apr 23, 2014 at 10:38 PM, Hesham Moustafa >>> wrote: >>>> Here [

Re: [PATCH 00/14] Removal of or32/openrisc and introduction of or1k

On Wed, Apr 23, 2014 at 11:48 PM, Christian Svensson wrote: > On Wed, Apr 23, 2014 at 10:38 PM, Hesham Moustafa > wrote: >> Here [1] line 76. Please correct me if I misunderstood that. When I > > That's just setting the default board. If you don't specify a > -mboa

Re: [PATCH 00/14] Removal of or32/openrisc and introduction of or1k

On Wed, Apr 23, 2014 at 10:45 PM, Christian Svensson wrote: > On Wed, Apr 23, 2014 at 9:38 PM, Hesham Moustafa > wrote: >> One issue, building gcc for RTEMS will have to discard some libraries >> that are linked by default (like or1ksim) in or1k-gcc when compiling >>

Re: [PATCH 00/14] Removal of or32/openrisc and introduction of or1k

On Wed, Apr 23, 2014 at 10:19 PM, Christian Svensson wrote: > On Wed, Apr 23, 2014 at 9:12 PM, Joel Sherrill > wrote: >> Is gcc close then? > Close to merging - not really. There is interest and momentum but the > effort hasn't begun. > Close to being fully functional - I would say so, bugs are r

Re: Re: [PATCH 00/14] Removal of or32/openrisc and introduction of or1k

Yes it's. Hope that gcc and gdb come next (soon). On Wed, Apr 23, 2014 at 5:27 PM, Joel Sherrill wrote: > Looks like the OpenRISC is now in binutils. > > > Original Message Subject: Re: [PATCH 00/14] Removal of > or32/openrisc and introduction of or1k Date: Wed, 23 Apr 2014

[GSoC] Porting RTEMS to OpenRISC - Introduction

Hi all, This year I am participating in GSoC for RTEMS organization with a project named after, "Porting RTEMS to OpenRISC." As the name indicates, the project aims to port RTEMS to OpenRISC architecture. If you're interested in the news and progress of this project, you may want to follow my blog

Re: newlib/openrisc port issues

On Tue, Apr 1, 2014 at 12:45 AM, Chris Johns wrote: > On 29/03/2014 9:10 am, Hesham Moustafa wrote: > >> Hi, >> >> A few weeks ago I was able to build gcc linked with newlib for >> or1k-rtems* target. But, I had to >> do some work-arounds to get it working w

newlib/openrisc port issues

Hi, A few weeks ago I was able to build gcc linked with newlib for or1k-rtems* target. But, I had to do some work-arounds to get it working which I think I have to discuss it with you. First issue, is that when building gcc/newlib with --enable-threads option, I got a lot of errors which fade out

Re: [PATCH] Add OpenRISC support for building or1k-rtems4.11-* toolchain

On Wed, Mar 19, 2014 at 8:24 PM, Christian Svensson wrote: > Hi, > > Exciting stuff! Looking forward to reviewing your work. > > On Wed, Mar 19, 2014 at 6:06 PM, Hesham Moustafa > wrote: >> >> >> The patches and changes are against : >> >> 1-

Re: Conflict when modifying newlib/openrisc to work for RTEMS

On Wed, Mar 19, 2014 at 5:04 PM, Gedare Bloom wrote: > On Wed, Mar 19, 2014 at 2:00 AM, Hesham Moustafa > wrote: > > > > > > > > On Wed, Mar 19, 2014 at 3:33 AM, Hesham Moustafa < > heshamelmat...@gmail.com> > > wrote: > >> > >>

Re: Conflict when modifying newlib/openrisc to work for RTEMS

On Wed, Mar 19, 2014 at 3:33 AM, Hesham Moustafa wrote: > > > > On Tue, Mar 18, 2014 at 8:26 PM, Joel Sherrill > wrote: > >> >> On 3/18/2014 1:07 PM, Hesham Moustafa wrote: >> >> Hi, >> >> I am working on modifying or1k newlib port to be

Re: Conflict when modifying newlib/openrisc to work for RTEMS

On Wed, Mar 19, 2014 at 8:00 AM, Hesham Moustafa wrote: > > > > On Wed, Mar 19, 2014 at 3:33 AM, Hesham Moustafa > wrote: > >> >> >> >> On Tue, Mar 18, 2014 at 8:26 PM, Joel Sherrill > > wrote: >> >>> >>> On 3/18/2014 1:07 P

Fwd: Conflict when modifying newlib/openrisc to work for RTEMS

On Tue, Mar 18, 2014 at 8:26 PM, Joel Sherrill wrote: > > On 3/18/2014 1:07 PM, Hesham Moustafa wrote: > > Hi, > > I am working on modifying or1k newlib port to be built for RTEMS. > Building and installing > newlib with --target=or1k-elf is done successfully, howeve

Conflict when modifying newlib/openrisc to work for RTEMS

Hi, I am working on modifying or1k newlib port to be built for RTEMS. Building and installing newlib with --target=or1k-elf is done successfully, however, when I try to build newlib with --target=or1k-rtems4.11 I got conflict error. part of this error is "sys/rtems/crt0.c:72:22: error: conflictin

Re: [GSoC] How RTEMS, GCC and newlib interact ?

On Sat, Mar 8, 2014 at 5:10 PM, Joel Sherrill wrote: > > On Mar 7, 2014 4:37 PM, Hesham Moustafa wrote: >> >> I have some questions about how RTEMS, GCC, newlib interact with each >> other, >> and which parts of them should I care and know about when porting R

[GSoC] How RTEMS, GCC and newlib interact ?

I have some questions about how RTEMS, GCC, newlib interact with each other, and which parts of them should I care and know about when porting RTEMS to OpenRISC. For example, the newlib port for OpenRISC includes some functions that deal with interrupts, exceptions, writing to SPRs, Caches, MMU, e

Re: GSoC 2014 | Porting RTEMS for OpenRISC

s moment, I do not. But I will make some contacts with their community and see who may want to mentor me. At the worst case, their mailing list, documentation, linux port, and forums should be of great help. [1] http://opencores.org/or1k/OR1200_OpenRISC_Processor [2] http://opencores.org/or1k/

Re: GSoC 2014 | Porting RTEMS for OpenRISC

On Wed, Mar 5, 2014 at 3:29 PM, Gedare Bloom wrote: > > On Tue, Mar 4, 2014 at 8:58 PM, Hesham Moustafa > wrote: > > > > > > > > On Tue, Mar 4, 2014 at 8:47 PM, Gedare Bloom wrote: > >> > >> On Tue, Mar 4, 2014 at 1:22 PM, Hesham Moustafa &

Re: GSoC 2014 | Porting RTEMS for OpenRISC

On Tue, Mar 4, 2014 at 8:47 PM, Gedare Bloom wrote: > On Tue, Mar 4, 2014 at 1:22 PM, Hesham Moustafa > wrote: > > > > > > > > On Mon, Mar 3, 2014 at 6:54 PM, Gedare Bloom wrote: > >> > >> Hesham, > >> > >> On Mon, Mar 3, 2014 a

Re: GSoC 2014 | Porting RTEMS for OpenRISC

e an RTEMS port, hopefully, can target both opensource HW and embedded SW communities. Industry preferences are of my concerns Alan, I appreciate your opinion regarding which architecture would you like to use a port for and why ? > Alan > > On Mar 4, 2014, at 1:22 PM, Hesham Moustafa &

Re: GSoC 2014 | Poring RTEMS for OpenRISC

On Mon, Mar 3, 2014 at 6:54 PM, Gedare Bloom wrote: > Hesham, > > On Mon, Mar 3, 2014 at 11:06 AM, Hesham Moustafa > wrote: > > > > > > > > On Mon, Mar 3, 2014 at 5:06 PM, Joel Sherrill > > > wrote: > >> > >> > &g

Re: GSoC 2014 | Poring RTEMS for OpenRISC

a port needs to be to a viable architecture from a "is it > alive" view this includes the cpu, tools, a way for us to test, etc > Sure, that's what I hope to work on. > > Gedare > > > > On Sun, Mar 2, 2014 at 12:39 AM, Hesham Moustafa > > wrot

GSoC 2014 | Poring RTEMS for OpenRISC

Hi, I am thinking of porting RTEMS for OpenRISC as a proposal for GSoC project this year. I know there was an older port, but it's not available anymore on the current RTEMS mainsteam. Would this project be of useful to RTEMS and suitable for GSoC ? Thanks, Hesham

Re: [PATCH] Modify raspberrypi mm_config_table to map GPIO and registers.

On Tue, Oct 15, 2013 at 8:59 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 2013-10-14 18:16, Hesham Moustafa wrote: > >> >> On Mon, Oct 14, 2013 at 6:03 PM, Gedare Bloom > <mailto:ged...@rtems.org>> wrote: >> >> O

Re: [PATCH] Modify raspberrypi mm_config_table to map GPIO and registers.

On Tue, Oct 15, 2013 at 1:39 AM, Chris Johns wrote: > Hesham Moustafa wrote: > >> >> On Mon, Oct 14, 2013 at 4:02 PM, Sebastian Huber >> >> <mailto:sebastian.huber@**embedded-brains.de>> >> wrote: >> >> On 2013-10-14 15:34, Hesham AL-

Re: [PATCH] Modify raspberrypi mm_config_table to map GPIO and registers.

On Mon, Oct 14, 2013 at 6:03 PM, Gedare Bloom wrote: > On Mon, Oct 14, 2013 at 11:54 AM, Hesham Moustafa > wrote: > > > > > > > > On Mon, Oct 14, 2013 at 4:02 PM, Sebastian Huber > > wrote: > >> > >> On 2013-10-14 15:34, Hesham AL-Matar

Re: [PATCH] Modify raspberrypi mm_config_table to map GPIO and registers.

On Mon, Oct 14, 2013 at 4:02 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 2013-10-14 15:34, Hesham AL-Matary wrote: > >> diff --git a/c/src/lib/libbsp/arm/**raspberrypi/startup/mm_config_**table.c >> b/c/src/lib/libbsp/arm/**raspberrypi/startup/mm_config_**table.c >> index

Re: [rtems commit] Shared MMU initialization for ARM BSPs and RaspberryPi MMU support

On Fri, Oct 4, 2013 at 9:50 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 2013-10-03 14:49, Gedare Bloom wrote: > >> @@ -87,9 +90,9 @@ arm_cp15_start_setup_**translation_table_and_enable_** >> mmu_and_cache( >> arm_cp15_set_domain_access_**control(dac); >> arm_cp15_

Re: [GSoC] low-level documentation for RTEMS/MMU project

emature right now. > > On Sat, Sep 28, 2013 at 11:06 AM, Hesham Moustafa > wrote: > > Hi, > > > > This is low-level documentation that contains design and implementation > > notes for > > libmm/MMU project. Please take a look if you are interested. > > &

[GSoC] low-level documentation for RTEMS/MMU project

Hi, This is low-level documentation that contains design and implementation notes for libmm/MMU project. Please take a look if you are interested. [1] http://heshamelmatary.blogspot.com/2013/09/inside-low-level-details-of-rtemsmmu.html Thanks, Hesham _

[GSoC] Final report of MMU project

Hi all, This [1] is the final report of MMU project containing what has been done and TODO tasks. Please take a look if you are interested. [1] http://heshamelmatary.blogspot.com/2013/09/gsoc-final-report-of-mmu-project-rtems.html Thanks, Hesham ___ rt

Re: [PATCH 1/6] libmm-score-api. The high-level libmm API should be used by applications. It helps developers to manage memory by setting generic and target-independent protection and cache attributes

ed to delay this high-level layer patch until we implement mprotect as a use-case. [1] https://github.com/heshamelmatary/rtems-gsoc2013/blob/low-level-libmm/cpukit/posix/src/mprotect.c > > I suggested to use such a scheme since I had only the BSP low-level stuff > in mind. For a mprotec

Re: [PATCH 2/3] shared MMU initialization for ARM BSPs

Please review the patch on the previous reply only. On Mon, Sep 16, 2013 at 6:23 PM, Hesham Moustafa wrote: > From 4d2a4662da9b0988c9e871490ed4ca466940754b Mon Sep 17 00:00:00 2001 > From: Hesham AL-Matary > Date: Sun, 15 Sep 2013 12:37:25 +0200 > Subject: [PATCH 2/3

Re: [PATCH 2/3] shared MMU initialization for ARM BSPs

Hesham On Sep 16, 2013 6:38 PM, "Gedare Bloom" wrote: > > The first patch you sent is the right one to look at? > No the second patch (on the reply) is the one to look at. The first one is missing arm-cp15-start.h changes. > On Mon, Sep 16, 2013 at 12:27 PM, Hesham Moustaf

Re: [PATCH 2/3] shared MMU initialization for ARM BSPs

>From 4d2a4662da9b0988c9e871490ed4ca466940754b Mon Sep 17 00:00:00 2001 From: Hesham AL-Matary Date: Sun, 15 Sep 2013 12:37:25 +0200 Subject: [PATCH 2/3] shared MMU initialization for ARM BSPs The newly added ORed flag: ARM_CP15_CTRL_XP is vital to get RaspberryPi MMU working properly and to shar

Re: [PATCH 2/6] arm-cp15-new-definitions New definitions for arm-cp15 Fault Status Register and ARMv6 control register.

On Fri, Sep 13, 2013 at 5:19 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 2013-09-12 08:59, Hesham AL-Matary wrote: > >> --- >> c/src/lib/libcpu/arm/shared/**include/arm-cp15.h | 21 >> + >> 1 file changed, 21 insertions(+) >> >> diff --git a/c/src/l

Re: [PATCH 4/6] libmm-libbsp-arm-shared. libmm low-level implementation that can be shared between many ARM targets. mminit.c contains initialization function for arm-cp15 and setup page tables. After

Thanks. I will resolve these issues in the next patch. On Fri, Sep 13, 2013 at 9:16 PM, Gedare Bloom wrote: > On Fri, Sep 13, 2013 at 11:25 AM, Sebastian Huber > wrote: > > Hello Hesham AL-Matary, > > > > please add a blank line after the subject in your Git commit messages. > > > Also try to

Re: [PATCH 3/6] libmm-libbsp-shared. Files shared between all target BSPs and low-level implementations for libmm. These shared files contain mm.h which is a link between high-level score api and low-

On Thu, Sep 12, 2013 at 2:55 PM, Gedare Bloom wrote: > On Thu, Sep 12, 2013 at 2:59 AM, Hesham AL-Matary > wrote: > > --- > > c/src/lib/libbsp/shared/include/mm.h | 36 > +++ > > c/src/lib/libbsp/shared/src/no_memorymanagement.c | 21 + > > 2 files c

Re: [PATCH 4/6] libmm-libbsp-arm-shared. libmm low-level implementation that can be shared between many ARM targets. mminit.c contains initialization function for arm-cp15 and setup page tables. After

On Thu, Sep 12, 2013 at 3:01 PM, Gedare Bloom wrote: > On Thu, Sep 12, 2013 at 2:59 AM, Hesham AL-Matary > wrote: > > --- > > .../lib/libbsp/arm/shared/include/arm-cp15-start.h | 11 -- > > c/src/lib/libbsp/arm/shared/mm.c | 46 > ++ > > c/src/lib/libbs

Re: [PATCH 3/6] libmm-libbsp-shared. Files shared between all target BSPs and low-level implementations for libmm. These shared files contain mm.h which is a link between high-level score api and low-

gt; > Yes, if I kept the struct definition at and deleted it from arm-cp15-start.h, that will get rid of such a redundancy. The struct definition at arm-cp15-start.h is not useful anymore. > -Gedare > > On Thu, Sep 12, 2013 at 2:00 PM, Hesham Moustafa > wrote: > > > > >

Re: [PATCH 4/6] libmm-libbsp-arm-shared. libmm low-level implementation that can be shared between many ARM targets. mminit.c contains initialization function for arm-cp15 and setup page tables. After

On Thu, Sep 12, 2013 at 8:17 PM, Gedare Bloom wrote: > On Thu, Sep 12, 2013 at 2:10 PM, Hesham Moustafa > wrote: > > > > > > > > On Thu, Sep 12, 2013 at 3:01 PM, Gedare Bloom wrote: > >> > >> On Thu, Sep 12, 2013 at 2:59 AM, Hesham AL-Matary &g

Set new BSP_OPTS for libmm

Hi all, I want to ask if it's OK to set new BSP options at BSP/configure.ac to make sure this BSP supports some features or not. For example, we can set new options like BSP_HAS_MMU, BSP_HAS_DATA_CACHE, BSP_XXX and according to these defines generate some useful code or just do nothing (stubs).

move libmm/libcpu shared files to libbsp

Hi, Currently libmm have a routine implemented at libcpu/arm/shared Since libcpu maybe deprecated soon, I'd like to ask whether I should move this implementation to libbsp files or not. This function just apply protection attributes for a memory region dynamically. What may be the best directory t

Re: [PATCH] libmm patches after fixups

coded values in the >>> tests) is the use of a global SMP lock. I don't know if that is the >>> right way we want to use locks, or if the lock should be encapsulated >>> inside of some kind of MM structure (even if that structure is only a >>> wrapper for the

Re: [PATCH] libmm patches after fixups

o. I will implement it. > > -Gedare > > On Wed, Aug 28, 2013 at 12:11 PM, Hesham Moustafa > wrote: >> Hey all, >> >> Please review the new patches after fixups according >> to your reviews. >> >> Thanks, >> Hesham >> >> On Tue,

Allocate memory within an application and modify its access permissions

Hey all, I want to allocate memory within an application code, set memory access attributes on it, and check whether these permissions are set correctly or not. I tried to use _Workspace_Allocate(), malloc(), and partition and region managers to allocate a region of memory, but just after I set t

Re: [PATCH 3/5] Shared libmm implemenation for ARM BSPs

On Mon, Aug 26, 2013 at 5:31 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 2013-08-26 02:14, Hesham AL-Matary wrote: > >> +/** >> + * @brief dummy exception handler for data aborts to help in debugging >> + */ >> +void dummy_data_abort_exception_**handler(void); >> > > This

Re: [PATCH 1/5] libmm score API

On Mon, Aug 26, 2013 at 8:21 PM, Gedare Bloom wrote: > On Mon, Aug 26, 2013 at 2:15 PM, Hesham Moustafa > wrote: > > > > > > > > On Mon, Aug 26, 2013 at 5:22 PM, Sebastian Huber > > wrote: > >> > >> On 2013-08-26 02:14, Hes

Re: [PATCH 1/5] libmm score API

On Mon, Aug 26, 2013 at 4:54 PM, Gedare Bloom wrote: > On Sun, Aug 25, 2013 at 8:14 PM, Hesham AL-Matary > wrote: > > --- > > cpukit/score/Makefile.am | 2 + > > cpukit/score/include/rtems/score/mm.h | 52 > > cpukit/score/include/rtems/score/mmimpl.h

Re: [PATCH 1/5] libmm score API

On Mon, Aug 26, 2013 at 5:22 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 2013-08-26 02:14, Hesham AL-Matary wrote: > >> +/** >> + * @brief _Memory_management_Region Flags defs >> + */ >> +#define RTEMS_MM_REGION_NO_PROTECTION 0x0 >> +#define RTEMS_MM_REGION_PROT

[GSoC] libmm patches and blog update

Hey all, I submitted recent patches for libmm project. I would appreciate your review and feedback. I have also updated my blog to document libmm design and some changes [1] [1] http://heshamelmatary.blogspot.com/2013/08/libmm-design-on-rtems-for-arm.html Regards, Hesham ___

Re: Raspberry/ARM processor halts when invalidating tlb

pe I can get an inexpensive setup for mine before I try to add any more > drivers. > The readme at the repository below has some good info on setting up JTAG > on the raspberry pi: > https://github.com/dwelch67/raspberrypi/tree/master/armjtag > > Alan > > > > On 8/22/20

Raspberry/ARM processor halts when invalidating tlb

Hey all, I am working on Raspberry Pi BSP which has ARM1176JZF-S (ARMv6) processor on it. Here is what I am doing that causes the processor to halt: At BSP startup, specifically in bsp_start_hook_0 function, I call another function that : 1- Initialize first level page tables (sections) with READ

[GSoC] Translate high-level memory abstract attributes into CPU specific attributes

Hi all, To make libmm abstract for the user who wants to apply memory attributes for a region of memory, libmm defines general common attributes at high-level that maps to specific CPU attributes for each target. These attributes are for Caches, memory protection currently. I propose two solution

Re: [PATCH 1/4] Add libmm score changes

On Mon, Jul 15, 2013 at 4:18 PM, Gedare Bloom wrote: > Overall this looks OK from what I have seen before. I have a few > comments about how we might want to consider improving the interface > though before we start to commit code. > > On Sat, Jul 13, 2013 at 7:05 PM, Hesham AL-Matary > wrote: >

Re: [PATCH 2/4] Add cpukit shared libmm header and stubs

On Mon, Jul 15, 2013 at 4:22 PM, Gedare Bloom wrote: > Are there compiler function attributes that can limit code generation > when stubs are used? > > I searched for GCC functions attributes and found that there are some function attributes that may be used for that purpose but not sure about th

[PATCH] Add basic infrastructure for libmm

Hi, This patch includes basic files and modifications to add libmm support. It includes the high-level score functions API, stubs for BSPs that do not support libmm at low-level and a test case called mmtest1. SPARC BSP is modified to support the stubs and run mmtest1. Another big patch is ready t

[GSoC] Defining regions of memory to apply attributes on it

Hi, The current test cases for libmm use hard-coded memory region addresses to apply memory attributes on. We want to remove that BSP dependency and hide any target specs to enable test cases to run for any BSP. I would suggest some solutions for your review : - Use the current allocators like pa

Re: [GSoC] libmm project status

plementation we can review it. > > A patch To include the stubs and high-level headers for every BSP and changes to all Makefile.am only ? > On Tue, Jul 9, 2013 at 12:53 PM, Hesham Moustafa > wrote: > > > > > > > > On Tue, Jul 9, 2013 at 6:47 PM, Rempel, C

Re: [GSoC] libmm project status

n't break the build)... > > Hopefully we can get your work committed over the summer and reduce the > number of patches at the end of the summer :) > > --- > > I noticed there wasn't a copyright on the .doc s. Could you add > > # COPYRIGHT (c) 2013. > # H

Re: [GSoC] libmm project status

> Actually I was confused about where is the best place for mmtest3 and I thought of smptests too. Should I move it with the same name ? > Until we have bsp specific tests it will be hard to construct good generic > tests. > On Jul 8, 2013 8:07 PM, "Rempel, Cynthia"

Re: [GSoC] libmm project status

On Tue, Jul 9, 2013 at 2:07 AM, Rempel, Cynthia wrote: > Hi Hesham Moustafa, > > Thanks for adding the .doc s :) > > Is there a way to conditionally build the mmtests based on whether libmm > is being built? > > My initial thought is something like an AM_CONDITIONA

Re: [GSoC] libmm project status

ity. > > Committed, thanks for your feedback :) > That way we can quickly identify what each test does in 5 years... Good > job with the documentation :) > > Cindy > ____ > From: rtems-devel-boun...@rtems.org [rtems-devel-boun...@rtems.org]

[GSoC] libmm project status

Hi all, I have posted a new thread to my blog that contains a brief introduction to libmm and latest updates, here is the thread [1] Please take a look. TODO: port libmm for Raspberry PI board on real hardware. Questions : I have created a new test case at libtests called mmtest3 [2] which simu

Re: Build error on the latest repo

On Sat, Jul 6, 2013 at 6:11 PM, Deng Hengyi wrote: > And do you use the latest repo from git which do not have problem with > libtests build? > I am using the latest update from github, AFAIK it's synchronized daily with git repo. The only difference is that I configure rtems with "--enable-rtem

Re: Build error on the latest repo

I have some errors related too the same BSP when --enable-smp too. But it's only for some Atomic/sptests test cases, other sample and libtests built successfully. Here is the error : /home/hesham/rtems-dev/build_bsps/smprealview/arm-rtems4.11/c/realview_pbx_a9_qemu/testsuites/sptests/spatomic01/

Re: SMP/MMU updating page tables on realview BSP

On Fri, Jul 5, 2013 at 6:42 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 05/07/13 18:30, Gedare Bloom wrote: > >> On Fri, Jul 5, 2013 at 12:11 PM, Hesham Moustafa >> wrote: >> >>> >Hi, >>> > >>> >I a

Re: SMP/MMU updating page tables on realview BSP

On Fri, Jul 5, 2013 at 6:30 PM, Gedare Bloom wrote: > On Fri, Jul 5, 2013 at 12:11 PM, Hesham Moustafa > wrote: > > Hi, > > > > I am working on a use case for cortex-a9/realview BSP that deals with > page > > tables and MMU. I need your help in gathering the req

SMP/MMU updating page tables on realview BSP

Hi, I am working on a use case for cortex-a9/realview BSP that deals with page tables and MMU. I need your help in gathering the required API and calls and any other details to implement the following case (if applicable) : 1- A thread running on a core that updates the page table. 2- On another

How memory access violation should be handled ?

Hi, What's the best way(s) to handle memory exceptions that result from memory access and permission violations ? for example, what should happen if an area of memory set to be read only and a thread tried to write data into this area ? Currently I am using it in debugging purpose to monitor excep

[GSoC] psim BSP memory layout

Hi, I want to understand how memory layout works at psim BSP. I studied linkcmd for psim and found that there are 16MB for RAM (starting at 0x) and another 16MB for psim-registers (starting at 0x0C0). all sections goes to psim-registers memory with noload (why?) directive. What exactly

Re: [GSoC] BAT vs Pages on PowerPC [Please give a feedback]

On Sun, Jun 23, 2013 at 11:18 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > on PowerPC you have also the Freescale Book E based MMUs: > > http://www.freescale.com/**files/32bit/doc/ref_manual/**EREF_RM.pdf

Re: [GSoC] BAT vs Pages on PowerPC [Please give a feedback]

On Sun, Jun 23, 2013 at 3:46 AM, Chris Johns wrote: > Thomas Dörfler wrote: > >> >> please note that some PPC derivatives (especially those for embedded >> projects) usually have eight DBATs and eight IBATs. This feature must be >> enabled (e.g. in a 603e core) with a special bit in one of the HI

Re: [GSoC] BAT vs Pages on PowerPC [Please give a feedback]

nfiguration option at build time? libmm should be general and abstract in the way that it provides memory protection. Only a developer who ports libmm should know about HW details like BAT and Pages. > wkr, > > Thomas. > > On 22.06.2013 04:11, Chris Johns wrote: > > Hesham Mo

[GSoC] libmm project status

Hi, This week I have done the following tasks: - Review PPC/MMU code. - Define common attributes/flags. - Define functions prototypes we may need. - Define set of common block sizes that we would work on. - Tried to integrate BAT and Page into libmm TODO: - Try to run qemuppc BSP and test l

Re: [GSoC] BAT vs Pages on PowerPC [Please give a feedback]

Eight: 4 for data and 4 for instructions. BAT areas can not overlap. Hesham On Jun 22, 2013 12:39 AM, "Chris Johns" wrote: > Hesham Moustafa wrote: > >> Hi there, >> >> I am working on providing memory protection for many targets/BSPs that >> RTEM

[GSoC] BAT vs Pages on PowerPC [Please give a feedback]

Hi there, I am working on providing memory protection for many targets/BSPs that RTEMS support through a library called libmm. Previous MMU projects depended on "Pages" to provide memory protection. I was thinking of using BATs for extending libmm for PowerPC targets. The following are some charac

What are the provided data structures by RTEMS

Hi, I want to keep track of some control data structures and have common operations (Insert, Search, Delete) on them. I know there is rbtree, Object manager, btree. Is there a reliable support for hash-tables and other data structures to consider ? Thanks, Hesham _

Re: realview pb - Cortex A9

Thanks Gedare & Sebastian for replying. I was able to run hello and ticker samples on gem5 successfully. On May 21, 2013 10:05 AM, "Sebastian Huber" < sebastian.hu...@embedded-brains.de> wrote: > On 05/17/2013 10:27 PM, Hesham Moustafa wrote: > >> Hi, >>

realview pb - Cortex A9

Hi, I am trying to build a simulation system on gem5 for the new realview_qemu BSP. I need to know the BSP specs that are needed. Primary, -How many cores? -Caches sizes -DRAM size -Frequency And any other important specs. Thanks, Hesham ___ rtems-deve