Dear Haijun,
Check the below message, plz.
cmd_mmc.c: In function ‘do_mmcops’:
cmd_mmc.c:405:5: warning: comparisons like ‘X=Y=Z’ do not have their
mathematical meaning [-Wparentheses]
cmd_mmc.c:406:5: warning: comparisons like ‘X=Y=Z’ do not have their
mathematical meaning [-Wparentheses]
Hello, Andreas.
I already posted a patch to fix this issue.
http://patchwork.ozlabs.org/patch/285071/
Tom, when would be possible to apply my patch?
Best Regards
Masahiro Yamada
___
U-Boot mailing list
U-Boot@lists.denx.de
Hi, Jaehoon
? 2013/11/8 9:15, Jaehoon Chung ??:
Dear Haijun,
On 11/05/2013 03:23 PM, Haijun Zhang wrote:
Add command class define.
Add mmc erase and secure erase define.
Add secure erase and trim support bit define.
Signed-off-by: Haijun Zhang haijun.zh...@freescale.com
---
include/mmc.h
Add command class define.
Add mmc erase and secure erase define.
Add secure erase and trim support bit define.
Signed-off-by: Haijun Zhang haijun.zh...@freescale.com
---
changes for V2:
- Changed the comment, no other change
include/mmc.h | 50
The max timeout value esdhc host can accept was about 2.69 sec
At 50 Mhz SD_CLK period, the max busy timeout
value = 2^27 * SD_CLK period ~= 2.69 sec.
In case erase command CMD38 timeout is caculate by
mult * 300ms * num(unit by erase group), so the time one erase
group need should be more than
It looks U-Boot is generally built using soft float. I need hard-float in my
system. Is this a general enough need that it'd make sense to have a
CONFIG_SYS_HARD_FLOAT to enable this option?
I made a quick update for mpc85xx (guarded by CONFIG_SYS_HARD_FLOAT) and I seem
to be running fine.
The max timeout value esdhc host can accept was about 2.69 sec
At 50 Mhz SD_CLK period, the max busy timeout
value = 2^27 * SD_CLK period ~= 2.69 sec.
In case erase command CMD38 timeout is caculate by
mult * 300ms * num(unit by erase group), so the time one erase
group need should be more than
Once mmc initialization was faild has_init should be set to 0,
prepard for the next initialization to recover from error.
Once mmcinfo command failed error should point out instead of print
incorrect mmc device information.
Error log:
= mmcinfo
Device: FSL_SDHC
Manufacturer ID: 0
OEM: 0
Name:
Read command class from csd register and secure erase
support bit from ext csd register. Also calculate the erase
timeout and secure erase timeout.
If read ext csd error, error status should be returned instead of
give some incorrect information.
Error log:
=
= mmcinfo
Device: FSL_SDHC
Abandon this, see [PATCH 7/7 V2] powerpc/esdhc: Update esdhc command
execution process
于 2013/11/8 10:06, Haijun Zhang 写道:
The max timeout value esdhc host can accept was about 2.69 sec
At 50 Mhz SD_CLK period, the max busy timeout
value = 2^27 * SD_CLK period ~= 2.69 sec.
In case erase
If the block rang was not algined, We tried to algined the range,
then erase the block. So the block range erased should be less or
equal to the block range send. If error occured during erase procedure
part of them will be erased. And use should resend the block rang to
continue erase the reset
Esdhc host version number is incorrect in host capacity register.
The value read from was 0x14. Correct it to 0x13.
Signed-off-by: Haijun Zhang haijun.zh...@freescale.com
---
Change for V2:
- No changes
arch/powerpc/include/asm/config_mpc85xx.h | 1 +
1 file changed, 1 insertion(+)
Erass sequence:
1. check if erase command is support by card. If not return.
2. Check the erase range to see if it was aligned. The min erase size
should be one erase group. SD card it was one block(512), mmc card
it should be one erase group.
3. If not, aligned the erase rang according to the
Hi, experts:
There is a raise() function implementation in Arch/arm/lib/eabi_compat.c
.
So, it is usually callbed by div0 from the c compiler libgcc ?
If uboot output raise: Signal ..., is it caused by division-by-zero ?
Best wishes,
___
From: Shaohui Xie shaohui@freescale.com
Signed-off-by: Shaohui Xie shaohui@freescale.com
---
include/configs/P4080DS.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/configs/P4080DS.h b/include/configs/P4080DS.h
index b0cd7d5..2f89008 100644
---
Hello Tom,
Am 07.11.2013 14:31, schrieb Tom Rini:
On Thu, Nov 07, 2013 at 10:37:24AM +0100, Andreas Bie?mann wrote:
Hello all together,
On 11/07/2013 09:17 AM, Heiko Schocher wrote:
Am 06.11.2013 08:50, schrieb Wolfgang Denk:
[snip]
So when you're once again doing some change that requires
Dear Saridakis, Dean (US SSA),
In message 20131107230556.589fc4a...@theia.denx.de you wrote:
It looks U-Boot is generally built using soft float. I need
correct.
hard-float in my system. Is this a general enough need that it'd make
sense to have a CONFIG_SYS_HARD_FLOAT to enable this
Hello Wolfgang,
Am 07.11.2013 20:15, schrieb Wolfgang Denk:
Dear Heiko,
In message527b8ba7.2070...@denx.de you wrote:
Agreed too. I doubt if a mailing list makes sense to collect such
data. It would probably be more efficient to provide a web based
service for this. It just has to be easy
Hello Wolfgang,
Am 07.11.2013 20:19, schrieb Wolfgang Denk:
Dear Heiko Schocher,
In message527b8c7f.6060...@denx.de you wrote:
All you want to do here is feed a database with data. This is not
what mailing lists were made for, so we should really use a more
appropriate interface.
Ok.
Hello Wolfgang,
Am 07.11.2013 20:26, schrieb Wolfgang Denk:
Dear Tom,
In message20131107133159.GR5925@bill-the-cat you wrote:
I feel this is the hard part of the problem, and what we're glossing
over. What has to be tested by the board maintainer? What are we going
to leave to their
Hi Tom,
On Thursday 07 November 2013 08:33 PM, Tom Rini wrote:
On Thu, Nov 07, 2013 at 08:17:39PM +0530, Sricharan R wrote:
Currently the DDR3 memory on DRA7 ES1.0 evm board is enabled using
software leveling. This was done since hardware leveling was not
working. Now that the right sequence
Dear Heiko,
In message 527c767d.3070...@denx.de you wrote:
Yes, this is perfectly fine. I just want to allow this at _any_ time,
not only once per release (near the end of the release cycle).
especially for releases where bigger changes get merged it may be
precious information to know
On Nov 7, 2013, at 9:03 PM, FengHua wrote:
I have verified these two changes on Foudation Model. It's ok, very fast.
I have verified this change on emulator, too. I have to enable i-cache first to
speed it up.
York
___
U-Boot mailing
Hi!
1) Is there specific reason why mmc configurations were dropped from this
includ/configs/am335x_evm.h?
2) Why partition number 7 has been skipped in DFU_ALT_INFO_NAND definition
in above file?
-Matti
___
U-Boot mailing list
U-Boot@lists.denx.de
Hello Wolfgang,
Am 08.11.2013 07:20, schrieb Wolfgang Denk:
Dear Heiko,
In message527c767d.3070...@denx.de you wrote:
Yes, this is perfectly fine. I just want to allow this at _any_ time,
not only once per release (near the end of the release cycle).
especially for releases where bigger
Hi,
In u-boot i am passing mtdargs in RW mode only. but still i am unable
to change the values.Yeah its true that mtd4 device is in READ only mode,
but how can i change the access permission of the device, so that i can
set/change the u-boot environment variable values from the Linux
Dear Heiko,
In message 527c7716.8060...@denx.de you wrote:
You, you can use a mailing list for submitting such information, but I
doubt that it would be efficient. And I definitely do not want to see
this on the current U-Boot ML.
Ok, let us discuss the way we collect such
Dear pshambhu,
In message 1383894946586-167013.p...@n7.nabble.com you wrote:
In u-boot i am passing mtdargs in RW mode only. but still i am unable
to change the values.Yeah its true that mtd4 device is in READ only mode,
but how can i change the access permission of the device, so that
Dear Naveen,
On 10/14/2013 08:06 AM, Heiko Schocher wrote:
Hello Naveen,
Am 30.09.2013 08:58, schrieb Naveen Krishna Chatradhi:
This enables CONFIG_SYS_I2C on Samsung, updating existing s3c24x0
i2c driver to support this.
Note: Not for merge, Just for review and suggestions.
Signed-off-by:
101 - 129 of 129 matches
Mail list logo
