Date: Sat, 1 Mar 2014 20:38:37 -0700 From: Tom Everett <tom@khubla.com> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-arm <freebsd-arm@freebsd.org>, Ian Lepore <ian@freebsd.org> Subject: Re: A unified imx6 kernel config, old WANDBOARD-* configs going away Message-ID: <CAB3ij4DGb0E9wN6AEntmyNQ189=_czyikBrtkX4zFEkk8%2BsO4w@mail.gmail.com> In-Reply-To: <CAB3ij4Dd1jq-_v7LVZ75skA3tZVOb=03vJ5JkSCb-7FL8FMrLg@mail.gmail.com> References: <1393594966.1149.161.camel@revolution.hippie.lan> <F38D0A2F-D2AF-426D-8515-BD111501B2A2@kientzle.com> <CAB3ij4Dd1jq-_v7LVZ75skA3tZVOb=03vJ5JkSCb-7FL8FMrLg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
ok I figured out what the dtsi file is. I've got a bootable image here: http://files.khubla.com/freebsd-wandboard/FreeBSD-armv6-11.0-IMX6-r262666.img.gz and the boot log is here http://files.khubla.com/freebsd-wandboard/FreeBSD-armv6-11.0-IMX6-r262666.txt I put the dtb file on the FAT partition and loaded it using uEnv.txt. On Sat, Mar 1, 2014 at 6:01 PM, Tom Everett <tom@khubla.com> wrote: > I'm looking at the crochet code, and I see in freebsd_install_fdt that > both *.dtb and *.dts are supported. However on the source tree it's > imx6.dtsi. What's the difference b/t a dts file and a dtsi file? > > > > On Sat, Mar 1, 2014 at 8:41 AM, Tim Kientzle <tim@kientzle.com> wrote: > >> >> On Feb 28, 2014, at 5: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. >> >> Nice! Another step towards GENERIC ARM. >> >> > 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. >> >> Using a U-Boot env var to specify the FDT is a nice idea. >> >> > 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. >> >> If you could get to a single U-Boot binary, you might >> be able to do what BeagleBone does: The U-boot.env >> script detects the board variation and conditionally >> loads the correct DTB blob. >> >> Tim >> >> _______________________________________________ >> 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" >> > > > > -- > A better world shall emerge based on faith and understanding - Douglas > MacArthur > -- A better world shall emerge based on faith and understanding - Douglas MacArthur
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB3ij4DGb0E9wN6AEntmyNQ189=_czyikBrtkX4zFEkk8%2BsO4w>