From: Emmanuel BOUAZIZ <ebouaziz@neotion.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] busybox: add 1.19.4 / 1.20.2 fixes
Date: Wed, 30 Jan 2013 15:48:05 +0100 [thread overview]
Message-ID: <510932A5.4080303@neotion.com> (raw)
In-Reply-To: <20120904110844.1439997180@busybox.osuosl.org>
On 09/04/2012 01:08 PM, Peter Korsgaard wrote:
> commit: http://git.buildroot.net/buildroot/commit/?id=9ec1c5d9d31b4f377c91a0451efd3ba67416d6f8
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
> ---
> .../busybox-1.19.4/busybox-1.19.4-udhcp.patch | 164 ++++++++++++++++++++
> .../busybox-1.20.2/busybox-1.20.2-kernel_ver.patch | 25 +++
> 2 files changed, 189 insertions(+), 0 deletions(-)
>
> diff --git a/package/busybox/busybox-1.19.4/busybox-1.19.4-udhcp.patch b/package/busybox/busybox-1.19.4/busybox-1.19.4-udhcp.patch
> new file mode 100644
> index 0000000..94d5f34
> --- /dev/null
> +++ b/package/busybox/busybox-1.19.4/busybox-1.19.4-udhcp.patch
> [...]
> + //TODO: must be combined with 'sname' and 'file' handling:
> +- { OPTION_STRING , 0x42 }, /* DHCP_TFTP_SERVER_NAME */
> ++ { OPTION_STRING_HOST , 0x42 }, /* DHCP_TFTP_SERVER_NAME */
> + { OPTION_STRING , 0x43 }, /* DHCP_BOOT_FILE */
> [...]
>
Hi,
I don't know what this patch is for, but it breaks the TFTP_SERVER_NAME option for me. The $tftp variable now contains
"bad" instead or the TFTP server name (I use it in udhcpc.script). When I remove the patch, it works fine again.
regards,
--
Emmanuel
next prev parent reply other threads:[~2013-01-30 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 11:08 [Buildroot] [git commit] busybox: add 1.19.4 / 1.20.2 fixes Peter Korsgaard
2013-01-30 14:48 ` Emmanuel BOUAZIZ [this message]
2013-01-30 15:06 ` Thomas Petazzoni
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=510932A5.4080303@neotion.com \
--to=ebouaziz@neotion.com \
--cc=buildroot@busybox.net \
/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