Date: Fri, 28 Feb 2014 11:27:11 -0700 From: Ian Lepore <ian@FreeBSD.org> To: Tom Everett <tom@khubla.com> Cc: freebsd-arm <freebsd-arm@FreeBSD.org> Subject: Re: A unified imx6 kernel config, old WANDBOARD-* configs going away Message-ID: <1393612031.1149.182.camel@revolution.hippie.lan> In-Reply-To: <CAB3ij4BLqWgdhpXgYWFcWnfwY3uC3nsiTi=Yt1PRetyAFydxsQ@mail.gmail.com> References: <1393594966.1149.161.camel@revolution.hippie.lan> <CAB3ij4BLqWgdhpXgYWFcWnfwY3uC3nsiTi=Yt1PRetyAFydxsQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It can work a couple different ways...
The .dtb files can be on the fat partition and the u-boot script stuff
can use "fatload" to load them and set fdt_addr= to the load address,
and ubldr will find them.
The .dtb files can be on the ufs partition in /boot/kernel/
or /boot/modules and all u-boot has to do is set fdt_file=filename.dtb
and ubldr will load the file from the ufs partition.
I favor the latter method, because I'd like to see us get all the way to
eliminating the msdos partition in the long run.
-- Ian
On Fri, 2014-02-28 at 11:10 -0700, Tom Everett wrote:
> I'll give updating Crochet for this a spin. I'm not that familiar with DTS
> however. I presume I need to drop the DTS blobs onto the FAT partition?
>
>
>
> On Fri, Feb 28, 2014 at 6:42 AM, Ian Lepore <ian@freebsd.org> wrote:
>
> > I've added a new imx6 unified kernel config named IMX6. It has no
> > compiled-in fdt, and can boot all three flavors of Wandboard when u-boot
> > and ubldr load a dtb file. Folks should start using it and eventually
> > the WANDBOARD* configs will go away when nobody needs them anymore.
> >
> > I build ubldr to load at address 11000000 and let it load the kernel at
> > 12000000. (The kernel can load on any 1MB boundary, but ubldr doesn't
> > make use of that feature yet.) ubldr will take a dtb file loaded by
> > u-boot and pass it along to the kernel. Another option is to put
> > the .dtb file in your /boot/kernel or /boot/modules directory, and ubldr
> > will load it from there, using the filename set in the u-boot env var
> > fdt_file.
> >
> > Unfortunately we can't do a single image that boots any wandboard,
> > because u-boot itself has to be different for each board. This is what
> > my u-boot env looks like on each wandboard:
> >
> > => printenv
> > baudrate=115200
> > bootcmd=run ubnet
> > bootdelay=1
> > console=ttymxc0
> > fdt_file=wandboard-dual.dtb
> > loadaddr=11000000
> > loaderdev=net
> > ubmmc=fatload mmc 0 ${loadaddr} ubldr; bootelf
> > ubnet=dhcp ${loadaddr} /wand/boot/ubldr;bootelf
> >
> > Environment size: 265/8188 bytes
> >
> > The only thing that differs per-board is the fdt_file setting, and the
> > u-boot binary itself. The "loaderdev=net" variable tells ubldr to load
> > the kernel from the network device rather than disk. So now all my
> > different model wandboards boot the same kernel and run from the same
> > nfs root directory.
> >
> > -- Ian
> >
> >
> > _______________________________________________
> > freebsd-arm@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
> >
>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1393612031.1149.182.camel>