All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@openembedded.org>
Subject: Re: [Angstrom-devel] RFC: ipv6 support in angstrom
Date: Sat, 08 Dec 2007 09:35:31 +0100	[thread overview]
Message-ID: <475A5753.3020601@student.utwente.nl> (raw)
In-Reply-To: <841689643.20071207232147@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Sokolovsky schreef:
> Hello Koen,
> 
> Friday, December 7, 2007, 3:44:32 PM, you wrote:
> 
>> -----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.
> 
>   Just one note - ipv6 is set for autoload in kernel.bbclass, not sure
> this is good idea for such circumstances.

That doesn't matter, since the kernel-module won't be shipped by
default, only enabled in the defconfig.

regards,

Koen


- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHWldSMkyGM64RGpERAi41AJ4tUq308n5ofk7agjZZ+pNu3Q/dwgCgikEI
MpjPBM01kSWv4LkjWtGLZqU=
=Gbwi
-----END PGP SIGNATURE-----



      reply	other threads:[~2007-12-08  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 13:44 [Angstrom-devel] RFC: ipv6 support in angstrom Koen Kooi
2007-12-07 21:21 ` Paul Sokolovsky
2007-12-08  8:35   ` Koen Kooi [this message]

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=475A5753.3020601@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.