Date: Fri, 30 Sep 2011 14:23:38 -0400 From: "Naoyuki Tai" <ntai@smartfruit.com> To: freebsd-arm@freebsd.org, "Matthieu Kraus" <matthieu.kraus@s2008.tu-chemnitz.de> Subject: Re: freebsd-arm Digest, Vol 286, Issue 5 Message-ID: <op.v2mv1onei1oka3@ntai.abinitio.com> In-Reply-To: <20110930173253.55166lqso9c8zvad@mail.tu-chemnitz.de> References: <20110930120022.4ABAA10656A7@hub.freebsd.org> <20110930173253.55166lqso9c8zvad@mail.tu-chemnitz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 30 Sep 2011 11:32:53 -0400, Matthieu Kraus <matthieu.kraus@s2008.tu-chemnitz.de> wrote: > I've been playing around a bit with FreeBSD on the Dreamplug during > the last few days and had some issues as well, however here's what I > got so far: > > first I didn't manage to get it to work with a dynamic fdt, so you'll > need a static one (see attachment). > > second I found a somewhat customized and pretty stripped kernel config > more useful, so I'll attach mine as well to give you some guidance. Unfortunately, you are using include "../mv/kirkwood/std.dreamplug" so it's kinda hard to tell what the config ends up. Do you use ZFS? I'm new to ZFS (I finally installed one) and the docs recommend at least 1GB of physical memory which DreamPlug does not have. So, I'm staying away from ZFS. If you have anything to share about zfs on DreamPlug, it would be great. > finally for booting on the plug: > there are basically two options here: > first is to boot via go as you already tried > second (which I find nicer) is to use mkimage from the ports > collection to create an image file uboot can read which should be > issues like this: > mkimage -A arm -O linux -T kernel -C none -a 900000 -e 900000 -n > "FreeBSD" -d kernel.bin image_name > or if you have a compressed kernel: > mkimage -A arm -O linux -T kernel -C gzip -a 900000 -e 900000 -n > "FreeBSD" -d kernel.bin.gz image_name > > if you go for the image, you can use the default boot options as > guidance (just load the image at 640000 or whatever and boot it - > it'll be moved to the prroper place and executed there) > > note that -O linux isn't required - e.g. -O netbsd works as well - > however -O FreeBSD doesn't work as u-boot recognizes it, but doesn't > have a bootcmd implemented for it. Nice. Can I do this on intel machine? > following that I got most things to work so far (except libertas chip > in ap mode as that one is lacking a proper driver - especially an sdio > one). > > RlyDontKnow As far as I understand, this wifi hardware is same as the OLPC XO wifi, and the linux driver does exit but not FreeBSD. # I have no interest in wifi part of DreamPlug. -- Using Opera's revolutionary email client: http://www.opera.com/mail/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.v2mv1onei1oka3>