From: Murray.Jensen at csiro.au <Murray.Jensen@csiro.au>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] dhcp vendor fields - support opt bootfile, ignore tftp server
Date: Thu, 30 Jun 2005 16:20:11 +1000 [thread overview]
Message-ID: <29183.1120112411@gerd> (raw)
This patch adds support for the dhcp vendor optional bootfile (#67). It also
ignores the vendor tftp server name option (#66). Both of these are supplied
by the DEC Tru64 Unix dhcp server (called "join"), and in the case of the
bootfile, it is the only place the boot file name is supplied. There is a
perfectly good, 128 byte, field in the main bootp/dhcp packet where the
boot file name could have been stored, but it wasn't used - go figure.
Cheers!
Murray...
--
Murray Jensen, CSIRO Manufacturing & Infra. Tech. Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853
Internet: Murray.Jensen at csiro.au
To the extent permitted by law, CSIRO does not represent, warrant and/or
guarantee that the integrity of this communication has been maintained or
that the communication is free of errors, virus, interception or interference.
The information contained in this e-mail may be confidential or privileged.
Any unauthorised use or disclosure is prohibited. If you have received this
e-mail in error, please delete it immediately and notify Murray Jensen on
+61 3 9662 7763. Thank you.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DHCP-VEN.PAT
Type: text/x-patch
Size: 2204 bytes
Desc: dhcp-vendor-bootfile.patch
Url : http://lists.denx.de/pipermail/u-boot/attachments/20050630/5d5227e0/attachment.bin
next reply other threads:[~2005-06-30 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 6:20 Murray.Jensen at csiro.au [this message]
2006-03-12 17:27 ` [U-Boot-Users] [PATCH] dhcp vendor fields - support opt bootfile, ignore tftp server Wolfgang Denk
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=29183.1120112411@gerd \
--to=murray.jensen@csiro.au \
--cc=u-boot@lists.denx.de \
/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