<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git, branch v2013.07</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<entry>
<title>Prepare v2013.07</title>
<updated>2013-07-23T11:58:13+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@ti.com</email>
</author>
<published>2013-07-22T19:57:32+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=62c175fbb8a0f9a926c88294ea9f7e88eb898f6c'/>
<id>62c175fbb8a0f9a926c88294ea9f7e88eb898f6c</id>
<content type='text'>
Signed-off-by: Tom Rini &lt;trini@ti.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Tom Rini &lt;trini@ti.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>fs/ext4: fix log2blksz un-initialized error, by cacaulating its value from blksz</title>
<updated>2013-07-22T14:09:56+00:00</updated>
<author>
<name>Lan Yixun (dlan)</name>
<email>dennis.yxun@gmail.com</email>
</author>
<published>2013-07-20T00:17:59+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=50ffc3b64aa3c8113f0a9fc31ea96e596d60054a'/>
<id>50ffc3b64aa3c8113f0a9fc31ea96e596d60054a</id>
<content type='text'>
The problem here is that uboot can't mount ext4 filesystem with
commit "50ce4c07df1" applied. We use hard-coded "SECTOR_SIZE"(512)
before this commit, now we introduce (block_dev_desc_t *)-&gt;log2blksz
to replace this macro. And after we calling do_ls()-&gt;fs_set_blk_dev(),
the variable log2blksz is not initialized, which it's not correct.

And this patch try to solve the problem by caculating the value of
log2blksz from variable blksz.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The problem here is that uboot can't mount ext4 filesystem with
commit "50ce4c07df1" applied. We use hard-coded "SECTOR_SIZE"(512)
before this commit, now we introduce (block_dev_desc_t *)-&gt;log2blksz
to replace this macro. And after we calling do_ls()-&gt;fs_set_blk_dev(),
the variable log2blksz is not initialized, which it's not correct.

And this patch try to solve the problem by caculating the value of
log2blksz from variable blksz.
</pre>
</div>
</content>
</entry>
<entry>
<title>ext4fs: le32_to_cpu() used on a 16-bit field</title>
<updated>2013-07-22T14:09:30+00:00</updated>
<author>
<name>Rommel Custodio</name>
<email>sessyargc+uboot@gmail.com</email>
</author>
<published>2013-07-21T08:53:25+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8b415f703f88d1d3b0466830047affbbf7f24913'/>
<id>8b415f703f88d1d3b0466830047affbbf7f24913</id>
<content type='text'>
Fix reading ext4_extent_header struture on BE machines.  Some 16 bit
fields where converted to 32 bit fields, due to the byte swap on BE
machines the containing value was corrupted. Therefore reading ext4
filesystems on BE machines where broken before.

Signed-off-by: Rommel Custodio &lt;sessyargc+uboot@gmail.com&gt;
[sent via git-send-email; rework commit message]
Signed-off-by: Andreas Bießmann &lt;andreas.devel@googlemail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Tested-by: Simon Glass &lt;sjg@chromium.org&gt;
Tested-by: Lukasz Majewski &lt;l.majewski@samsung.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix reading ext4_extent_header struture on BE machines.  Some 16 bit
fields where converted to 32 bit fields, due to the byte swap on BE
machines the containing value was corrupted. Therefore reading ext4
filesystems on BE machines where broken before.

Signed-off-by: Rommel Custodio &lt;sessyargc+uboot@gmail.com&gt;
[sent via git-send-email; rework commit message]
Signed-off-by: Andreas Bießmann &lt;andreas.devel@googlemail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Tested-by: Simon Glass &lt;sjg@chromium.org&gt;
Tested-by: Lukasz Majewski &lt;l.majewski@samsung.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>arm: at91sam9n12: change EBI IO to high drive mode</title>
<updated>2013-07-22T12:20:14+00:00</updated>
<author>
<name>Bo Shen</name>
<email>voice.shen@atmel.com</email>
</author>
<published>2013-07-17T09:14:17+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=b899fa39019c8fecb508f747525dd8c22622e804'/>
<id>b899fa39019c8fecb508f747525dd8c22622e804</id>
<content type='text'>
As both the DDR SDRAM and NAND flash connect to EBI on at91sam9n12
and share the lower 8 bits data line. If use low drive of the data
line, it will cause DDR data access corrupt in lower address, so
change the data line to high drive mode

This will fix the Linux kernel boot issue when use Lower address

Signed-off-by: Bo Shen &lt;voice.shen@atmel.com&gt;
Acked-by: Andreas Bießmann &lt;andreas.devel@googlemail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
As both the DDR SDRAM and NAND flash connect to EBI on at91sam9n12
and share the lower 8 bits data line. If use low drive of the data
line, it will cause DDR data access corrupt in lower address, so
change the data line to high drive mode

This will fix the Linux kernel boot issue when use Lower address

Signed-off-by: Bo Shen &lt;voice.shen@atmel.com&gt;
Acked-by: Andreas Bießmann &lt;andreas.devel@googlemail.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ddr cfg: DRAM_RESET needs 0x00020030</title>
<updated>2013-07-20T16:14:09+00:00</updated>
<author>
<name>Troy Kisky</name>
<email>troy.kisky@boundarydevices.com</email>
</author>
<published>2013-07-17T19:46:15+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fdf86c202c17adfc6f6313dc35f685b1d22b8125'/>
<id>fdf86c202c17adfc6f6313dc35f685b1d22b8125</id>
<content type='text'>
The old value of 0x000e0030 will cause ethernet
timeout issues on the sabrelite and possibly other
boards using the KSZ9021.
I have no explanation as to why.

But this is a correct change, the TRM will be updated
to show that 00b is the only valid setting for bits
19-18 of DRAM_RESET.

My thanks go to Liu Hui(Jason) for this information.

Acked-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Acked-by: Stefano Babic &lt;sbabic@denx.de&gt;
Signed-off-by: Troy Kisky &lt;troy.kisky@boundarydevices.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The old value of 0x000e0030 will cause ethernet
timeout issues on the sabrelite and possibly other
boards using the KSZ9021.
I have no explanation as to why.

But this is a correct change, the TRM will be updated
to show that 00b is the only valid setting for bits
19-18 of DRAM_RESET.

My thanks go to Liu Hui(Jason) for this information.

Acked-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Acked-by: Stefano Babic &lt;sbabic@denx.de&gt;
Signed-off-by: Troy Kisky &lt;troy.kisky@boundarydevices.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>net: phy: Set SUPPORTED_1000baseX_Half flag in ESTATUS_1000_XHALF case</title>
<updated>2013-07-19T21:12:20+00:00</updated>
<author>
<name>Fabio Estevam</name>
<email>fabio.estevam@freescale.com</email>
</author>
<published>2013-07-19T13:01:34+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9a5dad239332537a5689131bbcc705c1f9c0cb41'/>
<id>9a5dad239332537a5689131bbcc705c1f9c0cb41</id>
<content type='text'>
Commit de1d786e (add support for Xilinx 1000BASE-X phy (GTX)) introduced the
checking for ESTATUS_1000_XHALF, but it incorrectly sets the
SUPPORTED_1000baseX_Full flag in this case.

Set the SUPPORTED_1000baseX_Half flag instead.

Acked-by: Charles Coldwell &lt;coldwell@gmail.com&gt;
Reviewed-By: Sascha Silbe &lt;t-uboot@infra-silbe.de&gt;
Reviewed-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
Signed-off-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Commit de1d786e (add support for Xilinx 1000BASE-X phy (GTX)) introduced the
checking for ESTATUS_1000_XHALF, but it incorrectly sets the
SUPPORTED_1000baseX_Full flag in this case.

Set the SUPPORTED_1000baseX_Half flag instead.

Acked-by: Charles Coldwell &lt;coldwell@gmail.com&gt;
Reviewed-By: Sascha Silbe &lt;t-uboot@infra-silbe.de&gt;
Reviewed-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
Signed-off-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>phy: fix 10/100Mbps operation on 1Gbps-capable links</title>
<updated>2013-07-19T21:12:16+00:00</updated>
<author>
<name>Sascha Silbe</name>
<email>t-uboot@infra-silbe.de</email>
</author>
<published>2013-07-19T10:25:10+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9ba30f6bc2741ae4d49724cdd32ca1c9a48f6155'/>
<id>9ba30f6bc2741ae4d49724cdd32ca1c9a48f6155</id>
<content type='text'>
de1d786 [add support for Xilinx 1000BASE-X phy (GTX)] introduced a
check for the extended status register in order to support
1Gbps-capable PHYs that don't have the 1000BASE-T registers. Since
Extended Status only indicates what the PHY (i.e. the local side) is
capable of, this broke communication with non-1Gbps peers.

Only check the extended status if the 1000BASE-T registers are
actually missing so we don't end up setting speed to 1Gbps even though
the previous test (for the combination of local and peer support for
1Gbps) already indicated we can't do 1Gbps with the current peer.

Signed-off-by: Sascha Silbe &lt;t-uboot@infra-silbe.de&gt;
Tested-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Reviewed-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
de1d786 [add support for Xilinx 1000BASE-X phy (GTX)] introduced a
check for the extended status register in order to support
1Gbps-capable PHYs that don't have the 1000BASE-T registers. Since
Extended Status only indicates what the PHY (i.e. the local side) is
capable of, this broke communication with non-1Gbps peers.

Only check the extended status if the 1000BASE-T registers are
actually missing so we don't end up setting speed to 1Gbps even though
the previous test (for the combination of local and peer support for
1Gbps) already indicated we can't do 1Gbps with the current peer.

Signed-off-by: Sascha Silbe &lt;t-uboot@infra-silbe.de&gt;
Tested-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Reviewed-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>mkimage: Use board config to get CONFIG_FIT_SIGNATURE value</title>
<updated>2013-07-19T13:45:19+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2013-07-17T22:10:59+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=971c450a446a60daf276b9d2adf243be6048c421'/>
<id>971c450a446a60daf276b9d2adf243be6048c421</id>
<content type='text'>
The value of this config variable is not available to image.h on the host,
since the board config is not actually included. Bring this in so that
mkimage will be built with image-signing support for sandbox at least.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The value of this config variable is not available to image.h on the host,
since the board config is not actually included. Bring this in so that
mkimage will be built with image-signing support for sandbox at least.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>arm:trats:fix: Correction of loaddtb environment variable.</title>
<updated>2013-07-19T12:30:10+00:00</updated>
<author>
<name>Łukasz Majewski</name>
<email>l.majewski@samsung.com</email>
</author>
<published>2013-07-18T11:14:22+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=4ef400b9f84af699cfeef60c871174b6e1defc59'/>
<id>4ef400b9f84af699cfeef60c871174b6e1defc59</id>
<content type='text'>
Missing space for loaddtb command has been added. When missing, ext4load
fails with wrong number of passed parameters.

Acked-by: Minkyu Kang &lt;mk7.kang@samsung.com&gt;
Signed-off-by: Lukasz Majewski &lt;l.majewski@samsung.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Missing space for loaddtb command has been added. When missing, ext4load
fails with wrong number of passed parameters.

Acked-by: Minkyu Kang &lt;mk7.kang@samsung.com&gt;
Signed-off-by: Lukasz Majewski &lt;l.majewski@samsung.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>bootm: Move fixup_silent_linux() earlier in the bootm stages</title>
<updated>2013-07-17T14:37:11+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2013-07-17T03:09:59+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=576aacdb915242dc60977049528b546fbe6135cc'/>
<id>576aacdb915242dc60977049528b546fbe6135cc</id>
<content type='text'>
Before the bootm refactor, fixup_silent_linux() was done only in the
monolithic bootm case, not in the subcommand case. With the refactor, it
is done always, which is good. Unfortunately it is done too late, since it
is the PREP or CMDLINE stages that set up the command line for Linux.

Move fixup_silent_linux() into the LOADOS stage, which is where we find
out the OS being used, and can thus decide whether to perform this step.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Before the bootm refactor, fixup_silent_linux() was done only in the
monolithic bootm case, not in the subcommand case. With the refactor, it
is done always, which is good. Unfortunately it is done too late, since it
is the PREP or CMDLINE stages that set up the command line for Linux.

Move fixup_silent_linux() into the LOADOS stage, which is where we find
out the OS being used, and can thus decide whether to perform this step.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</pre>
</div>
</content>
</entry>
</feed>
