From owner-soc-status@FreeBSD.ORG  Wed Aug  8 13:21:24 2012
Return-Path: <owner-soc-status@FreeBSD.ORG>
Delivered-To: soc-status@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id CEB391065672;
	Wed,  8 Aug 2012 13:21:24 +0000 (UTC)
	(envelope-from ericmcc@cs.umass.edu)
Received: from mail.cs.umass.edu (loki.cs.umass.edu [128.119.240.93])
	by mx1.freebsd.org (Postfix) with ESMTP id 7056B8FC08;
	Wed,  8 Aug 2012 13:21:23 +0000 (UTC)
Received: from loki.cs.umass.edu (localhost [127.0.0.1])
	by mail.cs.umass.edu (8.13.8/8.13.1) with ESMTP id q78DLGnQ019669
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 8 Aug 2012 09:21:16 -0400
Received: from localhost (ericmcc@localhost)
	by loki.cs.umass.edu (8.13.8/8.13.1/Submit) with ESMTP id
	q78DLFgs019663; Wed, 8 Aug 2012 09:21:16 -0400
X-Authentication-Warning: loki.cs.umass.edu: ericmcc owned process doing -bs
Date: Wed, 8 Aug 2012 09:21:15 -0400 (EDT)
From: Eric McCorkle <ericmcc@cs.umass.edu>
To: soc-status@freebsd.org, ae@freebsd.org
Message-ID: <alpine.LRH.2.02.1208080913240.18565@loki.cs.umass.edu>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: 
Subject: Status report
X-BeenThere: soc-status@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Summer of Code Status Reports and Discussion <soc-status.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/soc-status>,
	<mailto:soc-status-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/soc-status>
List-Post: <mailto:soc-status@freebsd.org>
List-Help: <mailto:soc-status-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/soc-status>,
	<mailto:soc-status-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 13:21:24 -0000

Now that I can get status reports through...

At the present, I'm working in a full test environment, a partition 
containing a full system, which I'm trying to boot.  My objective now is 
to identify exactly where things go wrong with attempting to boot the 
kernel.  I know there are issues with the kernel being non-contiguous in 
memory, but I want to get a clearer picture of why it fails.

However, I have been traveling for job interviews more or less 
continuously for the past two weeks, so my progress has been very slow.

On a more important note, the end of coding is approaching.  However, I 
have no intention of stoping work on EFI at that time.  Rather, 
I intend to keep going, as part of my open-source work.  Therefore, I 
need to start setting up whatever resources I'll need to continue working.