<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/common/console.c, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2018-11-26T13:25:36Z</updated>
<entry>
<title>sandbox: Allow puts() output before global_data is set up</title>
<updated>2018-11-26T13:25:36Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2018-11-16T01:44:04Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=36bcea62af98145e6859cabec9c8f82d1d057bf9'/>
<id>urn:sha1:36bcea62af98145e6859cabec9c8f82d1d057bf9</id>
<content type='text'>
We support putc() in this case but not puts(), but this is more useful
since it is what printf() uses.

This particularly affects debugging early in SPL, where currently printf()
statements result in no output. Fix this by adding a special case into
puts() for sandbox, just like putc().

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
</entry>
<entry>
<title>console: unify fgetc function when console MUX is deactivated</title>
<updated>2018-09-11T00:20:34Z</updated>
<author>
<name>Patrick Delaunay</name>
</author>
<published>2018-08-03T11:38:44Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=273a12526c6b6278a79f1bdf7f6cc50a32938b28'/>
<id>urn:sha1:273a12526c6b6278a79f1bdf7f6cc50a32938b28</id>
<content type='text'>
Unify the fgetc function when MUX is activated or not:
- always call tstc() : it is the normal behavior expected
  by serial uclass (call tstc then getc) and that avoids
  issue when SERIAL_RX_BUFFER is activated
- reload WATCHDOG in the char waiting loop

This patch allow to have the same behavior when CONSOLE_MUX is activated
or not and avoid regression when this feature is deactivated.

Signed-off-by: Patrick Delaunay &lt;patrick.delaunay@st.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Don't disable ctrlc() on sandbox if in raw mode</title>
<updated>2018-07-26T19:08:17Z</updated>
<author>
<name>Joe Hershberger</name>
</author>
<published>2018-07-03T01:06:49Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=82a115fdec875d7e8dc601fe0e1b12859814c91c'/>
<id>urn:sha1:82a115fdec875d7e8dc601fe0e1b12859814c91c</id>
<content type='text'>
In raw mode, handle ctrl-c as normal. This allows normal ctrl-c behavior
such as aborting a command that is timing out without completely
terminating the sandbox executable.

In [1], Simon disabled this.  His reason for it was that it interferes
with piping test scripts. Piping should be done in cooked mode, so this
change should still not interfere.

[1] commit 8969ea3e9f2db04a6b3675 ("sandbox: Disable Ctrl-C")

Signed-off-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>console: Remember if ctrlc is disabled in console_tstc()</title>
<updated>2018-07-26T19:08:16Z</updated>
<author>
<name>Joe Hershberger</name>
</author>
<published>2018-07-03T01:06:48Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=b2f58d8ee090ccf15b1366ac46a075c02a01f4fc'/>
<id>urn:sha1:b2f58d8ee090ccf15b1366ac46a075c02a01f4fc</id>
<content type='text'>
We don't necessarily want to re-enable ctrl-c if it was already disabled
when calling tstc().

Signed-off-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>console: Fix handling of NULL global_data</title>
<updated>2018-06-18T18:43:14Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2018-06-12T06:04:56Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=af880e247d502844e01219995cbdbee4b3e6d204'/>
<id>urn:sha1:af880e247d502844e01219995cbdbee4b3e6d204</id>
<content type='text'>
Both putc() and puts() can be called before global_data is set up. Some of
the code paths don't handle this correctly. Add an explicit test before
any member is accessed.

Reported-by: Coverity (CID: 169030)
Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
</content>
</entry>
<entry>
<title>SPDX: Convert all of our single license tags to Linux Kernel style</title>
<updated>2018-05-07T13:34:12Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-05-06T21:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=83d290c56fab2d38cd1ab4c4cc7099559c1d5046'/>
<id>urn:sha1:83d290c56fab2d38cd1ab4c4cc7099559c1d5046</id>
<content type='text'>
When U-Boot started using SPDX tags we were among the early adopters and
there weren't a lot of other examples to borrow from.  So we picked the
area of the file that usually had a full license text and replaced it
with an appropriate SPDX-License-Identifier: entry.  Since then, the
Linux Kernel has adopted SPDX tags and they place it as the very first
line in a file (except where shebangs are used, then it's second line)
and with slightly different comment styles than us.

In part due to community overlap, in part due to better tag visibility
and in part for other minor reasons, switch over to that style.

This commit changes all instances where we have a single declared
license in the tag as both the before and after are identical in tag
contents.  There's also a few places where I found we did not have a tag
and have introduced one.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>stdio_names: Ensure MAX_NAMES is defined before use, don't use 3 directly</title>
<updated>2018-05-06T17:35:16Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-05-03T13:12:26Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=27b4225b3c81aefc0ded9bf62d0873e72725664d'/>
<id>urn:sha1:27b4225b3c81aefc0ded9bf62d0873e72725664d</id>
<content type='text'>
With tighter build flags the fact that &lt;stdio_dev.h&gt; doesn't have a
reference back to MAX_NAMES causes an error.  Include &lt;stdio.h&gt; here and
then in common/console.c use MAX_NAMES rather than 3 when working with
stdio_names.

Reported-by: Peter Robinson &lt;pbrobinson@gmail.com&gt;
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
Tested-by: Peter Robinson &lt;pbrobinson@gmail.com&gt;
</content>
</entry>
<entry>
<title>Revert "sandbox: Drop special case console code for sandbox"</title>
<updated>2017-12-07T20:17:00Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2017-12-04T20:48:19Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=64e9b4f346f113dec984eaab226a44d35e38d7ce'/>
<id>urn:sha1:64e9b4f346f113dec984eaab226a44d35e38d7ce</id>
<content type='text'>
While sandbox works OK without the special-case code, it does result in
console output being stored in the pre-console buffer while sandbox starts
up. If there is a crash or a problem then there is no indication of what
is going on.

For ease of debugging it seems better to revert this change also.

This reverts commit d8c6fb8cedbc35eee27730a7fa544e499b3c81cc.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>Revert "console: simplify puts()"</title>
<updated>2017-11-12T21:18:16Z</updated>
<author>
<name>Soeren Moch</name>
</author>
<published>2017-11-04T15:14:09Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=be135cc5eb4499f5eedd1b6d968ca51aa79df684'/>
<id>urn:sha1:be135cc5eb4499f5eedd1b6d968ca51aa79df684</id>
<content type='text'>
This reverts commit c61d0009feb966e0e93254a8c435a1889085e6b8.

A tbs2910 board user reported a very slow console frambuffer as
regression in current u-boot. I could bisect this down to the
above mentioned commit.

This revert brings back the fast framebuffer console (one
cache flush per string in puts(), not after each char).

Reported-by: Uwe Scheffler &lt;scheffler.u@web.de&gt;
Signed-off-by: Soeren Moch &lt;smoch@web.de&gt;
Tested-by: Uwe Scheffler &lt;scheffler.u@web.de&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>common: console: Fix duplicated CONFIG in silent env callback</title>
<updated>2017-08-28T11:19:12Z</updated>
<author>
<name>Wilson Lee</name>
</author>
<published>2017-08-25T07:06:29Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=5daf6e56d36ccbdb7a3b160f9bd0f0c572c18eaf'/>
<id>urn:sha1:5daf6e56d36ccbdb7a3b160f9bd0f0c572c18eaf</id>
<content type='text'>
The silent environment callback function does not update the silent
flag during silent env set or unset. That is because of duplicated
CONFIG keyword at preprocessor condition in silent environment
callback function and cause silent env callback unable to work.

This patch is to remove the duplicated CONFIG keywork in silent
environment callback function.

Signed-off-by: Wilson Lee &lt;wilson.lee@ni.com&gt;
Cc: Keng Soon Cheah &lt;keng.soon.cheah@ni.com&gt;
Cc: Chen Yee Chew &lt;chen.yee.chew@ni.com&gt;
Cc: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
</entry>
</feed>
