From: Doug Maxey <dwm@austin•ibm.com>
To: Paul Nasrat <pnasrat@redhat•com>
Cc: Linux PowerPC List <linuxppc-dev@ozlabs•org>, yaboot-devel@ozlabs•org
Subject: Re: ipv6 in yaboot
Date: Tue, 31 Jul 2007 16:08:49 -0500 [thread overview]
Message-ID: <32757.1185916129@falcon10.austin.ibm.com> (raw)
In-Reply-To: <1185912661.9310.143.camel@enki.eridu>
On Tue, 31 Jul 2007 21:11:01 BST, Paul Nasrat wrote:
>On Tue, 2007-07-31 at 14:21 -0500, Doug Maxey wrote:
>> Howdy!
>>
>> I just got asked about ipv6 support in yaboot and a quick investigation
>> showed _no_ knowledge of the address formats in the code.
>
>We really just use OF for obp-tftp and don't have our own ip stack,
True. Was just curious about the handling of the address formats,
where the xxxx:... will probably be used. Several spots already make
lots of assumptions that the colons are only in the disklabel.
> as
>there is no 1275 standard for ipv6 (although some modern IBM firmwares
>which also have iscsi support it) it's somewhat hard.
Oh, I agree completely. Publication is still being worked. The good
news is that the description is already there. Once folks can see the
whole enchilada.
>
>> 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? :)
>
>Have you tried it with firmware that supports obp-tftp over ipv6?
Heh. Not yet, but RSN.
next prev parent reply other threads:[~2007-07-31 21:08 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 [this message]
2007-08-01 1:03 ` Paul Mackerras
2007-08-01 2:37 ` Doug Maxey
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=32757.1185916129@falcon10.austin.ibm.com \
--to=dwm@austin$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(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