<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/arch/x86/cpu, branch v2017.05</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/arch/x86/cpu?h=v2017.05</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/arch/x86/cpu?h=v2017.05'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2017-04-30T17:40:57Z</updated>
<entry>
<title>fs: Kconfig: Add a separate config for FS_CBFS</title>
<updated>2017-04-30T17:40:57Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-04-27T04:27:59Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=deb959991528bee05079426c189f538ad3850337'/>
<id>urn:sha1:deb959991528bee05079426c189f538ad3850337</id>
<content type='text'>
Rather than using CMD_CBFS for both the filesystem and its command, we
should have a separate option for each. This allows us to enable CBFS
support without the command, if desired, which reduces U-Boot's size
slightly.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
[trini: imply FS_CBFS on SYS_COREBOOT]
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>fs: Convert CONFIG_CMD_CBFS to Kconfig</title>
<updated>2017-04-30T17:40:56Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-04-27T04:27:58Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=d66a10fc00407fda3c5091ca38c090dc055f7953'/>
<id>urn:sha1:d66a10fc00407fda3c5091ca38c090dc055f7953</id>
<content type='text'>
This converts the following to Kconfig:
   CONFIG_CMD_CBFS

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
[trini: imply CMD_CBFS on SYS_COREBOOT]
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>x86: Drop leading spaces in cpu_x86_get_desc()</title>
<updated>2017-04-18T07:51:21Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-03-19T18:59:20Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a6eb6769c6baa28d7cfaf04ebab0e9fa5b5b834f'/>
<id>urn:sha1:a6eb6769c6baa28d7cfaf04ebab0e9fa5b5b834f</id>
<content type='text'>
The Intel CPU name can have leading spaces. Remove them since they are not
useful.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>board_f: Drop setup_dram_config() wrapper</title>
<updated>2017-04-05T20:36:51Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-03-31T14:40:32Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=76b00aca4f1c13bc8f91a539e612abc70d0c692f'/>
<id>urn:sha1:76b00aca4f1c13bc8f91a539e612abc70d0c692f</id>
<content type='text'>
By making dram_init_banksize() return an error code we can drop the
wrapper. Adjust this and clean up all implementations.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>board_f: x86: Use checkcpu() for CPU init</title>
<updated>2017-04-05T17:55:09Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-03-28T16:27:30Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=76d1d02fd280ef7ad63a97c3a80bd765bf5596fa'/>
<id>urn:sha1:76d1d02fd280ef7ad63a97c3a80bd765bf5596fa</id>
<content type='text'>
At present we misuse print_cpuinfo() do so CPU init on x86. This is done
because it is the next available call after the console is enabled. But
several arches use checkcpu() instead. Despite the horrible name (which
we can fix), it seems a better choice.

Adjust the various x86 CPU implementations to move their init code into
checkcpu() and use print_cpuinfo() only for printing CPU info.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>dm: core: Add flags parameter to device_remove()</title>
<updated>2017-04-05T02:15:10Z</updated>
<author>
<name>Stefan Roese</name>
<email>sr@denx.de</email>
</author>
<published>2017-03-20T11:51:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=706865afe54eee83c1f3d7e9ea2f51db8e986d7b'/>
<id>urn:sha1:706865afe54eee83c1f3d7e9ea2f51db8e986d7b</id>
<content type='text'>
This patch adds the flags parameter to device_remove() and changes all
calls to this function to provide the default value of DM_REMOVE_NORMAL
for "normal" device removal.

This is in preparation for the driver specific pre-OS (e.g. DMA
cancelling) remove support.

Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
Cc: Simon Glass &lt;sjg@chromium.org&gt;
Acked-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>x86: Intel MID platforms has no microcode update</title>
<updated>2017-02-21T07:10:56Z</updated>
<author>
<name>Andy Shevchenko</name>
<email>andriy.shevchenko@linux.intel.com</email>
</author>
<published>2017-02-17T13:49:00Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=308c75e08deac2933fbc63a1e9521343e710279c'/>
<id>urn:sha1:308c75e08deac2933fbc63a1e9521343e710279c</id>
<content type='text'>
There is no microcode update available for SoCs used on Intel MID
platforms.

Use conditional to bypass it.

Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>x86: Force 32-bit jumps in interrupt handlers</title>
<updated>2017-02-21T06:53:29Z</updated>
<author>
<name>J. Tang</name>
<email>tang@jtang.org</email>
</author>
<published>2017-02-10T02:54:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3c03f4928e96dce4c6cd14fb630dacad13a141ae'/>
<id>urn:sha1:3c03f4928e96dce4c6cd14fb630dacad13a141ae</id>
<content type='text'>
Depending upon the compiler used, IRQ entries could vary in sizes. With
GCC 5.x, the code generator will use short jumps for some IRQ entries
but near jumps for others. For example, GCC 5.4.0 generates the
following:

$ objdump -d interrupt.o
&lt;snip&gt;
00000207 &lt;irq_18&gt;:
207:   6a 12                   push   $0x12
209:   eb 85                   jmp    190 &lt;irq_common_entry&gt;

0000020b &lt;irq_19&gt;:
20b:   6a 13                   push   $0x13
20d:   eb 81                   jmp    190 &lt;irq_common_entry&gt;

0000020f &lt;irq_20&gt;:
20f:   6a 14                   push   $0x14
211:   e9 7a ff ff ff          jmp    190 &lt;irq_common_entry&gt;

00000216 &lt;irq_21&gt;:
216:   6a 15                   push   $0x15
218:   e9 73 ff ff ff          jmp    190 &lt;irq_common_entry&gt;

This causes a problem in cpu_init_interrupts(), because the IDT setup
assumed same sizes for all IRQ entries. GCC 4.x always generated 32-bit
jumps, so this previously was not a problem.

The fix is to force 32-bit near jumps for all entries within the
inline assembly. This works for GCC 5.x, and 4.x was already using
that form of jumping.

Signed-off-by: Jason Tang &lt;tang@jtang.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>dm: core: Replace of_offset with accessor</title>
<updated>2017-02-08T13:12:14Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-01-17T23:52:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e160f7d430f163bc42757aff3bf2bcac0a459f02'/>
<id>urn:sha1:e160f7d430f163bc42757aff3bf2bcac0a459f02</id>
<content type='text'>
At present devices use a simple integer offset to record the device tree
node associated with the device. In preparation for supporting a live
device tree, which uses a node pointer instead, refactor existing code to
access this field through an inline function.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>x86: make LOAD_FROM_32_BIT visible for platforms</title>
<updated>2017-02-07T05:36:50Z</updated>
<author>
<name>Andy Shevchenko</name>
<email>andriy.shevchenko@linux.intel.com</email>
</author>
<published>2017-02-05T13:52:00Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=446d4e048ee3b00f7907e15cd02aa404cc714c77'/>
<id>urn:sha1:446d4e048ee3b00f7907e15cd02aa404cc714c77</id>
<content type='text'>
This option is useful not only for development, but for the platforms
where U-Boot is run from custom ROM bootloader. For example, Intel
Edison is that board.

Make this option visible that platforms can select it if needed.

Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
</feed>
