From: Doug Maxey <dwm@enoyolf•org>
To: Paul Mackerras <paulus@samba•org>
Cc: Linux PowerPC List <linuxppc-dev@ozlabs•org>,
Paul Nasrat <pnasrat@redhat•com>,
yaboot-devel@ozlabs•org
Subject: Re: ipv6 in yaboot
Date: Tue, 31 Jul 2007 21:37:56 -0500 [thread overview]
Message-ID: <18071.1185935876@bebe.enoyolf.org> (raw)
In-Reply-To: <18095.56272.4647.158912@cargo.ozlabs.ibm.com>
On Wed, 01 Aug 2007 11:03:12 +1000, Paul Mackerras wrote:
> Doug Maxey writes:
>
> > 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 ':'.
When I did the original work for building in the tests for determining
if the network device was really an iscsi block device, I may have been
over-concerned that the non-disklabel parts of the IQN, which can and
does have colons, could confuse the parsing. In the block device path,
there was only a single questionable use. That usage was fixed by
switching from strchr() to strrchr().
I expect the same syntax issues for the pure network side, as there is
no chance to not take the network path for a pure ipv6 network boot.
In my mind anyway. Which is always questionable. ;)
++doug
next prev parent reply other threads:[~2007-08-01 2:37 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 [this message]
2007-08-01 5:12 ` Segher Boessenkool
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=18071.1185935876@bebe.enoyolf.org \
--to=dwm@enoyolf$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=pnasrat@redhat$(echo .)com \
--cc=yaboot-devel@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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