From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libwebsockets: add option to enable/disable ipv6 support
Date: Fri, 25 Sep 2015 14:06:11 +0200 [thread overview]
Message-ID: <20150925140611.13ec8719@free-electrons.com> (raw)
In-Reply-To: <0dc07792d2e04be6b1628563695e9e28@LysExc01.nanotronic.local>
Hello Andreas,
On Fri, 25 Sep 2015 11:12:00 +0000, Wetzel Andreas wrote:
> Ok, I was not aware that you made IPv6 mandantory. Sorry for that.
>
> Currently, IPv6 is always enabled for libwebsockets.
> In a project we used a kernel without support for IPv6. libwebsockets (with ipv6 support) seem to cause problems if the kernel does not support IPv6 at all. That's why I thought such configuration option would make sense.
>
> Size is no reason. Including IPv6 support is a matter of a few kilobytes.
>
> So my resolution is to add IPv6 support to the linux kernel we use to.
What is the size difference of the kernel with/without IPv6 enabled? If
it's very significant, then maybe we need to revisit this? Gustavo?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-25 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 13:16 [Buildroot] [PATCH 1/1] libwebsockets: add option to enable/disable ipv6 support Andreas Wetzel
2015-09-23 14:08 ` Vicente Olivert Riera
2015-09-23 14:43 ` Wetzel Andreas
2015-09-23 14:51 ` Vicente Olivert Riera
2015-09-23 15:12 ` Wetzel Andreas
2015-09-23 15:42 ` Vicente Olivert Riera
2015-09-23 21:02 ` Thomas Petazzoni
2015-09-25 11:12 ` Wetzel Andreas
2015-09-25 12:06 ` Thomas Petazzoni [this message]
2015-09-25 12:27 ` Gustavo Zacarias
2015-09-25 12:33 ` Thomas Petazzoni
2015-10-03 18:57 ` Peter Korsgaard
2015-10-05 8:18 ` Wetzel Andreas
2015-10-10 17:24 ` Thomas Petazzoni
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=20150925140611.13ec8719@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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