From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Cc: Daniele Lacamera <daniele.lacamera@tass.be>
Subject: [RFC] picotcp.20140530
Date: Fri, 30 May 2014 13:18:33 +0400 [thread overview]
Message-ID: <20140530131833.e6960587743c31fd85cd7788@gmail.com> (raw)
Hi All!
My new barebox with picotcp support brunch is pushed to github:
https://github.com/frantony/barebox/tree/picotcp.20140530
For this version reworked content of Daniele Lacamera's push request
is used (see https://github.com/frantony/barebox/pull/1).
Changes since picotcp.20140525:
* rebased over latest barebox;
* the latest picotcp is used (warnings and big-endian
tests fixed);
* add picotcp dhcp client support by Daniele Lacamera
* qemu mips malta defconfig is dropped as barebox qemu
malta has no network device support (you can rebase
over experimental pci branch but it is very different story ...)
* other small fixes.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-05-30 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 9:18 Antony Pavlov [this message]
2014-06-02 8:46 ` Sascha Hauer
2014-06-02 16:56 ` Antony Pavlov
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=20140530131833.e6960587743c31fd85cd7788@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=daniele.lacamera@tass.be \
/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