From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Subject: Re: remoteproc: Load coprocessor code to the specific main memory location Date: Wed, 22 Feb 2012 13:10:11 +0100 Message-ID: <4F44DB23.4010303@monstr.eu> References: <4F1EE861.4030405@monstr.eu> <4F1FF870.3000105@monstr.eu> <4F200F64.9060203@monstr.eu> <4F212E9E.9060807@monstr.eu> <4F391C1D.9020402@monstr.eu> <4F3BA962.9040109@monstr.eu> <4F3BC30A.4030301@monstr.eu> <4F3CC899.4070302@monstr.eu> <4F3CFFAD.9030402@monstr.eu> <4F3D032B.6090700@monstr.eu> <4F425711.80102@monstr.eu> Reply-To: monstr@monstr.eu Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Ohad Ben-Cohen Cc: LKML , John Williams , linux-arm , "Grosen, Mark" , Arnd Bergmann , Grant Likely , devicetree-discuss@lists.ozlabs.org List-Id: devicetree@vger.kernel.org Ohad Ben-Cohen wrote: > Hi Michal, > > On Mon, Feb 20, 2012 at 4:22 PM, Michal Simek wrote: >> IRC you mentioned somewhere that you maybe will have firmware which is >> possible to >> compiled by gcc and which doesn't required that TI tools. Am I correct or >> that was >> something totally different? > > You're correct - this is in the works, but I'm afraid I don't have any > scheduling information about this, sorry. > > But we have folks from another vendor now who got rpmsg working, and > are working out the legal issues so they can release the RTOS sources. > Hopefully that'll be released soon. That will be great to get it. Please let me know when you have them. After EW I will look at it anyway. Thanks, Michal -- Michal Simek, Ing. (M.Eng) w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/ Microblaze U-BOOT custodian