From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: [Angstrom-devel] RFC: ipv6 support in angstrom
Date: Fri, 07 Dec 2007 14:44:32 +0100 [thread overview]
Message-ID: <47594E40.2090201@student.utwente.nl> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The following RFC was accepted by all angstrom developers, so moving it
to OE now:
I want to propose the following:
* enabling the ipv6 kernel module on all network capable devices
angstrom wants to support.
* enabling the mip6 kernel module on capable kernels (afaik vanilla
2.6.23 or patches 2.6.x)
* have ipv6 support enabled in the c library and busybox
Some machines already do all this, but afaik we don't have a policy for
it yet.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHWU5AMkyGM64RGpERAsh/AJ9VUBvUDeHrDuxiDvh/s07k9kToCgCeNZNJ
pBcIC8RShN/oZwwsEYvHq2g=
=EKF4
-----END PGP SIGNATURE-----
next reply other threads:[~2007-12-07 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 13:44 Koen Kooi [this message]
2007-12-07 21:21 ` [Angstrom-devel] RFC: ipv6 support in angstrom Paul Sokolovsky
2007-12-08 8:35 ` Koen Kooi
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=47594E40.2090201@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.