From: Joe Hershberger Date: Fri, 17 Aug 2012 10:34:38 +0000 (+0000) Subject: fdt: Identify scripts in ITBs as printable strings X-Git-Tag: v2013.01-rc1~89^2^2~2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=8805beec8f51e861996860db71a831e4c263cf4c;p=kernel%2Fu-boot.git fdt: Identify scripts in ITBs as printable strings Scripts in the ITB format will have spaces in them and will end in a newline charachter. Make sure that these are considered printable. Signed-off-by: Joe Hershberger --- diff --git a/common/cmd_fdt.c b/common/cmd_fdt.c index 2997452..a5e2cfc 100644 --- a/common/cmd_fdt.c +++ b/common/cmd_fdt.c @@ -754,12 +754,12 @@ static int is_printable_string(const void *data, int len) if (len == 0) return 0; - /* must terminate with zero */ - if (s[len - 1] != '\0') + /* must terminate with zero or '\n' */ + if (s[len - 1] != '\0' && s[len - 1] != '\n') return 0; /* printable or a null byte (concatenated strings) */ - while (((*s == '\0') || isprint(*s)) && (len > 0)) { + while (((*s == '\0') || isprint(*s) || isspace(*s)) && (len > 0)) { /* * If we see a null, there are three possibilities: * 1) If len == 1, it is the end of the string, printable