mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Daniele Lacamera <daniele.lacamera@tass.be>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Kristof Roelants <kristof.roelants@tass.be>,
	barebox <barebox@lists.infradead.org>,
	Daniele Lacamera <mlists@danielinux.net>,
	Sam Van Den Berge <sam.van.den.berge@tass.be>
Subject: Re: [RFC] [WIP] incorporate picotcp into barebox: a small demo
Date: Tue, 27 May 2014 09:52:19 +0200	[thread overview]
Message-ID: <CAOngqVWxceLR+LZj4zKW_AQgaQYmQjVdVYFw+c1L_EEQYaAxtQ@mail.gmail.com> (raw)
In-Reply-To: <20140527053045.GL15686@pengutronix.de>

On Tue, May 27, 2014 at 7:30 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:

>> 3. ipv6
>>
>>    Current IPv4 address space is near totaly exhausted
>>    (see https://www.icann.org/news/announcement-2-2014-05-20-en).
>>    I suppose with the lapse of time IPv6 will be used even in bootloaders :)
>>    picotcp gives you IPv6 just now.
>
> These features sound very nice. I hope we can get the binary size
> impacts within sensible limits. Is it possible to disable TCP support in
> picotcp?
>

Yes, you can disable each single component. E.g., to compile TCP out,
use TCP=0, or just leave PICO_SUPPORT_TCP out. Some binary size
figures for picotcp (compiled for arm, with -Os, symbols stripped):

    1433      pico_arp.o (ex ./build/lib/libpicotcp.a)
    1715      pico_dev_loop.o (ex ./build/lib/libpicotcp.a)
    2956      pico_dhcp_client.o (ex ./build/lib/libpicotcp.a)
     284      pico_dhcp_common.o (ex ./build/lib/libpicotcp.a)
    1152      pico_dhcp_server.o (ex ./build/lib/libpicotcp.a)
    2340      pico_dns_client.o (ex ./build/lib/libpicotcp.a)
    1170      pico_icmp4.o (ex ./build/lib/libpicotcp.a)
    1897      pico_icmp6.o (ex ./build/lib/libpicotcp.a)
    3624      pico_igmp.o (ex ./build/lib/libpicotcp.a)
     660      pico_ipfilter.o (ex ./build/lib/libpicotcp.a)
    5560      pico_ipv4.o (ex ./build/lib/libpicotcp.a)
    1216      pico_ipv6_nd.o (ex ./build/lib/libpicotcp.a)
    4089      pico_ipv6.o (ex ./build/lib/libpicotcp.a)
    2476      pico_mdns.o (ex ./build/lib/libpicotcp.a)
    1428      pico_nat.o (ex ./build/lib/libpicotcp.a)
    3294      pico_olsr.o (ex ./build/lib/libpicotcp.a)
     612      pico_slaacv4.o (ex ./build/lib/libpicotcp.a)
     928      pico_sntp_client.o (ex ./build/lib/libpicotcp.a)
     766      pico_socket_tcp.o (ex ./build/lib/libpicotcp.a)
     644      pico_socket_udp.o (ex ./build/lib/libpicotcp.a)
   10542      pico_tcp.o (ex ./build/lib/libpicotcp.a)
     684      pico_udp.o (ex ./build/lib/libpicotcp.a)
    1375      pico_device.o (ex ./build/lib/libpicotcp.a)
     434      pico_frame.o (ex ./build/lib/libpicotcp.a)
     601      pico_protocol.o (ex ./build/lib/libpicotcp.a)
    2636      pico_socket_multicast.o (ex ./build/lib/libpicotcp.a)
    5018      pico_socket.o (ex ./build/lib/libpicotcp.a)
    3079      pico_stack.o (ex ./build/lib/libpicotcp.a)
    1188      pico_tree.o (ex ./build/lib/libpicotcp.a)
   63801      (TOTALS)

/d

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-05-27  7:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-25  9:58 Antony Pavlov
2014-05-26  9:35 ` Daniele Lacamera
2014-05-26  9:45 ` Lucas Stach
2014-05-26 12:09   ` Antony Pavlov
2014-05-27  5:30     ` Sascha Hauer
2014-05-27  7:52       ` Daniele Lacamera [this message]
2014-05-27  9:46     ` Daniele Lacamera
2014-05-27 14:04       ` Antony Pavlov
2014-05-27 17:26         ` Daniele Lacamera
2014-05-29  5:40           ` Antony Pavlov
2014-05-28  6:08         ` Sascha Hauer
2014-05-28  7:23         ` Juergen Borleis
2014-05-28 10:32           ` 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=CAOngqVWxceLR+LZj4zKW_AQgaQYmQjVdVYFw+c1L_EEQYaAxtQ@mail.gmail.com \
    --to=daniele.lacamera@tass.be \
    --cc=barebox@lists.infradead.org \
    --cc=kristof.roelants@tass.be \
    --cc=mlists@danielinux.net \
    --cc=s.hauer@pengutronix.de \
    --cc=sam.van.den.berge@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