From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: scripts for testing barebox in qemu
Date: Fri, 12 Aug 2011 09:36:47 +0200 [thread overview]
Message-ID: <20110812073647.GM31404@pengutronix.de> (raw)
In-Reply-To: <CAA4bVAE=a6qD9r_igo3JJFoJ4ojvN=KV9Ocvwd3cEN0pJZxfJw@mail.gmail.com>
On Fri, Aug 12, 2011 at 01:23:36AM +0400, Antony Pavlov wrote:
> Hi!
>
> Some times ago I made the scripts for building mips cross-development
> stuff: toolchain, patched qemu, firmware, linux and small rootfs.
> I named the scripts 'clab'.
>
> Today this scripts work not only for mips, but for arm, pc and
> sparc32 too.
>
> (Yes, yes, I know about the existing projects of such type.
> I'm planning to migrate to buildroot in the future.)
>
> Also clab has a script for running qemu in convenient way.
>
> In this letter I want propose this scripts for very easy testing
> of barebox on MIPS Malta (with initial PCI support) and
> on ARM Versatile.
Maybe you can add this information to the wiki. You need an account
for this which I can create for you (and everyone else who is
interested).
Sascha
>
> A small instruction:
>
> 1. clab will install toolchain and qemu to /opt/clab, so prepare it
>
> sudo mkdir /opt/clab
> sudo chown $USER /opt/clab
>
> 2. get and unpack clab
>
> wget http://prizma.bmstu.ru/~antony/barebox/clab-0.34.tar.gz
> tar vfx clab-0.34.tar.gz
> cd clab-0.34
>
> 3. build toolchain, qemu, firmware, linux & rootfs
>
> ./mk_src_dir.sh
> ./build-all.sh
>
> If you don't want build linux & rootfs you can disable
> options --build_linux and --build-rootfs.
>
> Clab will put all compiled stuff in the directory 'out'.
>
> 4. start barebox
>
> ./start-qemu.sh qemu-configs/versatile-linux-gnueabi/barebox-no-network-stdio
>
> ./start-qemu.sh qemu-configs/malta-linux-gnu/barebox-no-network-stdio
>
> Also you can run linux:
>
> ./start-qemu.sh qemu-configs/versatile-linux-gnueabi/stdio-no-network
>
> ./start-qemu.sh qemu-configs/malta-linux-gnu/stdio-no-network
>
> 5. starting barebox with network support need root
> permissions to setup tap network interface.
>
> So to try barebox with Realtek 8139 on PCI bus run this:
>
> sudo ./start-qemu.sh qemu-configs/versatile-linux-gnueabi/barebox-stdio
>
> --
> Best regards,
> Antony Pavlov
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-08-12 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 21:23 Antony Pavlov
2011-08-12 7:36 ` Sascha Hauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110812073647.GM31404@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox