From owner-freebsd-hackers@FreeBSD.ORG  Thu May 22 20:33:24 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CB145446;
 Thu, 22 May 2014 20:33:24 +0000 (UTC)
Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com
 [IPv6:2607:f8b0:400d:c04::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 7A40128A7;
 Thu, 22 May 2014 20:33:24 +0000 (UTC)
Received: by mail-qg0-f54.google.com with SMTP id q108so6632750qgd.13
 for <multiple recipients>; Thu, 22 May 2014 13:33:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type:content-transfer-encoding;
 bh=Ie7uv6Wj+Iw/rDV6/UNGAIocWw3xAdxULbz21prH/ek=;
 b=PimkyEoPzxmq+mNYGmG9f/zgHTwNrBjLQDgtOSlp9D2jwVVcORPCIH6U8zaR15Q3ft
 squpTdvepwk/aUYUkYJLt0rd/BY9VSZufLsitEb0nQwj+TJHtMwfUTIJmf36pq6dZzps
 EmJhAhrNZOUnCbzgqX6tdW3UnCEErDRxHgEDZuSO3Bd28ZfWWc+RvbeQrcVppljkAmgx
 Oq6P+dFiXfcGnJsTwix3j2g7t7Inq8XrSiYq1ZZwrYefJLOo+y/uDlxJQ6fCfCrQDyUR
 yd+bZjjZGUUHU2+GosEeS/nDkx0vCfCz+4JMFvuh0u+ZMjTOxsHdkh9QxyugLSWrLwEQ
 GBGA==
MIME-Version: 1.0
X-Received: by 10.140.48.1 with SMTP id n1mr17344059qga.107.1400790803661;
 Thu, 22 May 2014 13:33:23 -0700 (PDT)
Received: by 10.96.84.232 with HTTP; Thu, 22 May 2014 13:33:23 -0700 (PDT)
In-Reply-To: <CFA3AB63.2D2AD%marcelm@juniper.net>
References: <CFA3A930.2D2A3%marcelm@juniper.net>
 <CFA3AB63.2D2AD%marcelm@juniper.net>
Date: Thu, 22 May 2014 14:33:23 -0600
Message-ID: <CACS+7ZS8W22Tsnz1BtwT2=2x6Hi9zumpNByF31Vyt+t6QtdkuA@mail.gmail.com>
Subject: Re: Patch to tech mkimg about the TMPDIR variable
From: Dan McGregor <danismostlikely@gmail.com>
To: Marcel Moolenaar <marcelm@juniper.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>,
 Alan Somers <asomers@freebsd.org>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 20:33:24 -0000

On 22 May 2014 14:27, Marcel Moolenaar <marcelm@juniper.net> wrote:
> On 5/22/14, 1:18 PM, "Marcel Moolenaar" <marcelm@juniper.net> wrote:
>>>
>>>The next itch I want to scratch is a way to set the active partition
>>>on an MBR image.
>>
>>I thought I made the first partition active by default.
>>I guess not=E2=80=A6
>
> Yes, I did!
>
> The gotcha is that mkimg only does that if you give it
> a boot code file. Try that...

Also, while I'm thinking about it, the other thing I wanted was a way
to specify the origin of a partition. So as an example (units are
sectors):

0: MBR table
2-63: empty
64-2047: first partition data
2048-$end: second partition data

The use case for this is some other boards (Wandboard for me) puts
u-boot as raw data 1K into the image.

Dan