From: Colin Leitner <colin.leitner@googlemail.com>
To: Daniele Lacamera <daniele.lacamera@tass.be>,
Antony Pavlov <antonynpavlov@gmail.com>
Cc: Colin Leitner <colin.leitner@googlemail.com>,
PicoTCP <picotcp@tass.be>, barebox <barebox@lists.infradead.org>
Subject: Re: Adding IPv4 multicast support
Date: Tue, 15 Jul 2014 20:17:25 +0200 [thread overview]
Message-ID: <53C57035.5090207@gmail.com> (raw)
In-Reply-To: <CAOngqVV-PcbsowH9iOHXpxXNvJEb_k7KyWakQVVGT9FMm4iFLw@mail.gmail.com>
> What would you need for "network discovery"? Currently picotcp
> - mDNS (at the moment over v4 only)
That's what you want (with DNS-SD over mDNS). Sounds great and would save me lots of work :)
Thanks for your effort!
-Colin
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-07-15 18:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 10:11 Adding IPv4 multicast support Colin Leitner
2014-07-13 10:55 ` Antony Pavlov
2014-07-13 10:52 ` Colin Leitner
2014-07-13 13:15 ` Colin Leitner
2014-07-13 14:28 ` Daniele Lacamera
2014-07-15 7:01 ` picotcp tftp support [was Adding IPv4 multicast support] Antony Pavlov
2014-07-15 9:31 ` Daniele Lacamera
2014-07-15 10:27 ` Antony Pavlov
2014-07-15 10:57 ` Daniele Lacamera
2014-07-15 12:57 ` Antony Pavlov
2014-07-15 15:55 ` Daniele Lacamera
2014-07-15 19:02 ` Antony Pavlov
2014-07-16 6:30 ` Sascha Hauer
2014-07-16 6:48 ` Daniele Lacamera
2014-09-04 17:14 ` Antony Pavlov
2014-09-05 7:37 ` Daniele Lacamera
2014-09-26 9:27 ` PicoTCP
2014-09-28 14:22 ` Antony Pavlov
2014-09-29 9:45 ` Daniele Lacamera
2014-09-29 10:10 ` Michele Di Pede
2014-09-29 10:19 ` Antony Pavlov
2014-07-15 18:17 ` Colin Leitner [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=53C57035.5090207@gmail.com \
--to=colin.leitner@googlemail.com \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=daniele.lacamera@tass.be \
--cc=picotcp@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 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.