From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rob Landley <rob@landley.net>
Subject: Re: Bare metal hexagon status
Date: Sun, 17 Mar 2013 23:32:55 -0500
Message-ID: <1363581175.15703.27@driftwood>
References: <CA+3xLx7yCG9AqxpTg7Xm+TjyuHr3gfwrPpfn3a9dJwG9UNxWZw@mail.gmail.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 8BIT
Return-path: <linux-hexagon-owner@vger.kernel.org>
In-Reply-To: <CA+3xLx7yCG9AqxpTg7Xm+TjyuHr3gfwrPpfn3a9dJwG9UNxWZw@mail.gmail.com>
	(from jonpry@gmail.com on Sat Mar 16 15:59:39 2013)
Content-Disposition: inline
Sender: linux-hexagon-owner@vger.kernel.org
List-ID: <linux-hexagon.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; delsp="Yes"; format="Flowed"
To: Jon Pry <jonpry@gmail.com>
Cc: linux-hexagon@vger.kernel.org

On 03/16/2013 03:59:39 PM, Jon Pry wrote:
> The port to bare metal hexagon appears to be fully functional on V3
> processors. All cores are running under SMP. It has not yet been
> tested on V2. So anybody interested in Hexagon programming should be
> able to mess with it now.

Where do we pull the tree from, and does the documentation say what  
hardware we need to try it? (Still just that one brand of device that  
doesn't sign firmware?)

Rob