From: Segher Boessenkool <segher@kernel.crashing.org>
To: Doug Maxey <dwm@enoyolf.org>
Cc: Linux PowerPC List <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
Paul Nasrat <pnasrat@redhat.com>,
yaboot-devel@ozlabs.org
Subject: Re: ipv6 in yaboot
Date: Wed, 1 Aug 2007 07:12:15 +0200 [thread overview]
Message-ID: <5682bc7e60187e64d80fd99b4ad573df@kernel.crashing.org> (raw)
In-Reply-To: <18071.1185935876@bebe.enoyolf.org>
>>> I just got asked about ipv6 support in yaboot and a quick
>>> investigation
>>> showed _no_ knowledge of the address formats in the code.
>>>
>>> Should I be submitting an RFC for a full parser that can pick that
>>> apart? Or does has someone have code lurking in the shadows, that
>>> just needed some prompting? :)
>>
>> I would have thought that yaboot would just be passing any network
>> addresses in text form to some OF method, so it's up to OF to
>> understand ipv6 address formats. No?
>
> Yes, yaboot _should_ just pass the text representation around.
> However, there are places that the context determination, for
> disklabels, is a simple check for the presence of ':'.
The network address is passed to OF as (part of) the device
argument for the network device; and colons aren't legal
characters in a device argument, so any OF implementation that
would use colons in IPv6 addresses is terminally broken. This
is completely analogous to the fact that filesystem paths cannot
use forward slashes. (The third disallowed character is the
at-sign, for completeness).
Segher
next prev parent reply other threads:[~2007-08-01 5:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 19:21 ipv6 in yaboot Doug Maxey
2007-07-31 20:11 ` Paul Nasrat
2007-07-31 21:08 ` Doug Maxey
2007-08-01 1:03 ` Paul Mackerras
2007-08-01 2:37 ` Doug Maxey
2007-08-01 5:12 ` Segher Boessenkool [this message]
2007-08-01 21:01 ` Doug Maxey
2007-08-06 18:42 ` Segher Boessenkool
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=5682bc7e60187e64d80fd99b4ad573df@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dwm@enoyolf.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=pnasrat@redhat.com \
--cc=yaboot-devel@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).