From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Matthias_Wei=DFer?= Date: Mon, 07 May 2012 10:35:50 +0200 Subject: [U-Boot] uboot and ZFS In-Reply-To: <4FA7761D.90704@lundman.net> References: <4FA0A7F3.8010803@lundman.net> <201205030213.35048.marex@denx.de> <4FA2172D.9080106@lundman.net> <201205051526.52499.marex@denx.de> <4FA7761D.90704@lundman.net> Message-ID: <4FA78966.9040401@arcor.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 07.05.2012 09:13, schrieb Jorgen Lundman: >> If you correctly skip the HW init, you can try booting u-boot from u-boot ... >> (now, WD will hate me for bringing this up :-) ). It's possible, but unsupported >> operation. You might need to do some research on this matter :-) >> > > I was thinking more along the lines of; Since I am testing a filesystem > driver, to have a small test binary I can run and just feed a patch to (be > it block device, or raw file) to test it can traverse, and read the contents. You could use sandbox arch for this purpose and use an image of a zfs filesystem. You can then use your native toolchain to compile and debug u-boot. Reagards Matthias