From owner-freebsd-embedded@FreeBSD.ORG  Sat Nov 26 17:03:47 2011
Return-Path: <owner-freebsd-embedded@FreeBSD.ORG>
Delivered-To: freebsd-embedded@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 40C571065670;
	Sat, 26 Nov 2011 17:03:47 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mx1.freebsd.org (Postfix) with ESMTP id EA3BD8FC0C;
	Sat, 26 Nov 2011 17:03:43 +0000 (UTC)
Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63])
	(authenticated bits=0)
	by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id pAQGxQlM021395
	(version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO);
	Sat, 26 Nov 2011 09:59:26 -0700 (MST) (envelope-from imp@bsdimp.com)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <CAJ-Vmo==7W9nKu6mp_9Nr2Ayd8G3Ch9V5bXw4crTjXwmdBV_8Q@mail.gmail.com>
Date: Sat, 26 Nov 2011 09:59:26 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4E34ACD-7408-4953-AD90-8C0243796100@bsdimp.com>
References: <CAJ-Vmo=aLVTgA10UAg=KQMyybeLmBjF75qXdpmFAkqdU9GzJvA@mail.gmail.com>
	<B27CBE5B-EC8C-4B33-8614-53751211F895@lassitu.de>
	<alpine.BSF.2.00.1111241921210.76315@wonkity.com>
	<4ECFF854.5050602@swin.edu.au>
	<4010BC72-2896-4AD0-AECB-60768C82F549@lassitu.de>
	<a993ee4b21b709dcb14dc23aa3b5bc02.squirrel@eternamente.info>
	<CAJ-VmokNPBr=CH8ogWcQAJwo4zU7Cj-OiUFaxWsUeOT0cM60eQ@mail.gmail.com>
	<05A65C4A-CA28-409D-87D6-880F621CFCF2@bsdimp.com>
	<CAJ-Vmo==7W9nKu6mp_9Nr2Ayd8G3Ch9V5bXw4crTjXwmdBV_8Q@mail.gmail.com>
To: Adrian Chadd <adrian@FreeBSD.org>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1
	(harmony.bsdimp.com [10.0.0.6]);
	Sat, 26 Nov 2011 09:59:26 -0700 (MST)
Cc: freebsd-embedded@FreeBSD.org
Subject: Re: tplink TL-WR1043ND access point is now ready (was Re: svn
	commit: r227926 - head/sys/mips/conf)
X-BeenThere: freebsd-embedded@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Dedicated and Embedded Systems <freebsd-embedded.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-embedded>, 
	<mailto:freebsd-embedded-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-embedded>
List-Post: <mailto:freebsd-embedded@freebsd.org>
List-Help: <mailto:freebsd-embedded-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-embedded>, 
	<mailto:freebsd-embedded-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Nov 2011 17:03:47 -0000


On Nov 26, 2011, at 1:11 AM, Adrian Chadd wrote:

> On 26 November 2011 14:01, Warner Losh <imp@bsdimp.com> wrote:
>>=20
>> On Nov 25, 2011, at 6:44 PM, Adrian Chadd wrote:
>>> That's why I included "newfs" in my build. You can create an MSDOS
>>> partition (or BSD label partition if you'd like) on a USB flash
>>> device, plug it into the tplink, then "newfs" it. I however haven't
>>> added anything into my startup scripts to mount filesystems. Ok,
>>> someone should file an issue in my google code project.
>>=20
>> makefs is the usual way to create an "other" endian file system.
>=20
> .. and is a pain if you want to makefs a 500 gig UFS filesystem for
> that 2.5" USB attached disk. :-)
>=20
> You can makefs a small FS, dd that there, then use growfs.. or I can
> just run "newfs" from the host.
>=20
> That's why I included it.

Ah!  Any plans for pushing this all the way into the kernel and =
importing NetBSD's bi-endian patches?

Warner