From: Alexander Aring <alex.aring@gmail.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: ipv6 support in barebox?
Date: Sat, 7 Dec 2013 07:28:40 +0100 [thread overview]
Message-ID: <20131207062838.GA13787@omega> (raw)
In-Reply-To: <20131206170803.GF27628@ns203013.ovh.net>
On Fri, Dec 06, 2013 at 06:08:03PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 16:39 Thu 05 Dec , Sascha Hauer wrote:
> > On Thu, Dec 05, 2013 at 01:48:35AM +0100, Alexander Aring wrote:
> > > Hi,
> > >
> > > I need a new challenge in my free time. :-)
> > >
> > > So maybe I could try to implement a ipv6 stack for barebox. Are there
> > > some interest to apply a ipv6 stack into barebox?
> > >
> > > I don't need to begin any work if there are no interest to add a ipv6
> > > support.
> > >
> > > ... and yes I know that's maybe a really big project, but I like to get
> > > some new experience.
> >
> > Sooner or later I think we will need ipv6 support, but now I think it's
> > up to you if you have enough interest in it to implement it ;)
>
> I've evaluate it and I does not want to support a custom implementation
>
> I was thinking simply integration uIP stack so we can have ip/tcp v4/v6 stack
>
mhh, yea I know the uIP stack from contiki os. I really don't like
contiki code. :-)
But we can try to use the uIP as basis, of course. Then we could have a
basically ipv6 support.
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-12-07 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 0:48 Alexander Aring
2013-12-05 15:39 ` Sascha Hauer
[not found] ` <CANvTkNby96mKLpMKL47NAKb6q8GyHV2xFrCYDZ3Dh=ixtz=vOQ@mail.gmail.com>
2013-12-05 18:20 ` Alexander Aring
2013-12-05 18:21 ` Alexander Aring
2013-12-06 17:08 ` Jean-Christophe PLAGNIOL-VILLARD
2013-12-07 6:28 ` Alexander Aring [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=20131207062838.GA13787@omega \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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