[U-Boot] [RFC PATCH v3 09/11] net: IPv6 documentation

Luka Kovačič luka.kovacica at gmail.com
Sat Jan 28 20:59:09 CET 2017


Sounds good to me. I will start testing soon and I am going to automate it.

V sob., 28. jan. 2017 8:51 pop. je oseba Tom Rini <trini at konsulko.com>
napisala:

> On Wed, Jan 25, 2017 at 10:56:20PM +1300, Chris Packham wrote:
> > Signed-off-by: Chris Packham <judge.packham at gmail.com>
> > ---
> >
> > Changes in v3:
> > - Add brief testing section
> [snip]
> > +Testing using QEMU
> > +------------------
> > +Refer to README.x86 for instructions on building u-boot for QEMU. Add
> > +the relevant IPv6 configuration to the configuration (CONFIG_CMD_NET6,
> > +CONFIG_CMD_PING6) and build.
> > +
> > +On the host system run
> > +
> > +  sudo qemu-system-i386 -nographic -bios u-boot.rom -net nic -net tap
> > +
> > +At the u-boot command line run
> > +
> > +  setenv ipaddr 192.168.1.100
> > +  setenv ip6addr 3ffe::100/64
> > +
> > +On the host system run
> > +
> > +  sudo ip addr add 3ffe::1/64 dev tap0
> > +  sudo ip addr add 192.168.1.1
> > +
> > +It should now be possible to use ping6 and tftpboot6 to communicate with
> > +the host system from the emulated u-boot environment.
>
> So we can test this under qemu? Cool!  That means we should get some
> test.py tests written to match up with the ipv4 tests we have today.  My
> gut reaction is that qemu-ppce500 should also be able to work too as
> it's also using the E1000 driver.
>
> --
> Tom
>


More information about the U-Boot mailing list