On Tue, Mar 27, 2012 at 01:02:38PM +0900, Magnus Damm wrote:
Hi Chris,
On Tue, Mar 27, 2012 at 12:20 PM, Chris Ball c...@laptop.org wrote:
Hi,
On Mon, Mar 26 2012, Magnus Damm wrote:
Do you have a feeling of if it it worth trying to start with a value close
to 400kHz or if it would
Hi Simon,
On Tue, Mar 27, 2012 at 3:01 PM, Simon Horman ho...@verge.net.au wrote:
On Tue, Mar 27, 2012 at 01:02:38PM +0900, Magnus Damm wrote:
Hi Chris,
On Tue, Mar 27, 2012 at 12:20 PM, Chris Ball c...@laptop.org wrote:
Hi,
On Mon, Mar 26 2012, Magnus Damm wrote:
Do you have a
Hi Magnus,
On Tue, Mar 27, 2012 at 03:37:42PM +0900, Magnus Damm wrote:
Hi Simon,
On Tue, Mar 27, 2012 at 3:01 PM, Simon Horman ho...@verge.net.au wrote:
On Tue, Mar 27, 2012 at 01:02:38PM +0900, Magnus Damm wrote:
[snip]
Anyway, I was mainly wondering about the setup of the clocks in
On Mon, 26 Mar 2012, Magnus Damm wrote:
On Mon, Mar 26, 2012 at 2:52 PM, Simon Horman ho...@verge.net.au wrote:
On Mon, Mar 26, 2012 at 02:45:30PM +0900, Yusuke Goda wrote:
Hi Simon-san, Guennadi-san
(2012/03/26 7:30), Simon Horman wrote:
On Sat, Mar 24, 2012 at 07:06:31PM +0100,
G'day
This is still present, and we have absolutely no idea where to continue
searching for the solution of the problem. Any pointers? Any git trees
of mmc driver changes we could try? Anybody else with a MX25 that has
this issue?
Hi:
-110 is the timeout problem.
You can dump the esdhc
On Mon, 26 Mar 2012, Guennadi Liakhovetski wrote:
On Mon, 26 Mar 2012, Magnus Damm wrote:
On Mon, Mar 26, 2012 at 2:52 PM, Simon Horman ho...@verge.net.au wrote:
On Mon, Mar 26, 2012 at 02:45:30PM +0900, Yusuke Goda wrote:
Hi Simon-san, Guennadi-san
(2012/03/26 7:30), Simon
ADDENDUM:
On Tue, 27 Mar 2012 09:32:36 +0200, joancarles wrote:
G'day
This is still present, and we have absolutely no idea where to
continue searching for the solution of the problem. Any pointers? Any
git trees of mmc driver changes we could try? Anybody else with a
MX25
that has this
Hi,
Le Tue, 27 Mar 2012 09:32:36 +0200,
joancarles joancar...@fqingenieria.es a écrit :
G'day
This is still present, and we have absolutely no idea where to continue
searching for the solution of the problem. Any pointers? Any git trees
of mmc driver changes we could try? Anybody else
On Tue, Mar 27, 2012 at 09:53:33AM +0200, Guennadi Liakhovetski wrote:
On Mon, 26 Mar 2012, Guennadi Liakhovetski wrote:
On Mon, 26 Mar 2012, Magnus Damm wrote:
On Mon, Mar 26, 2012 at 2:52 PM, Simon Horman ho...@verge.net.au wrote:
On Mon, Mar 26, 2012 at 02:45:30PM +0900, Yusuke
Hi Eric
G'day
This is still present, and we have absolutely no idea where to
continue
searching for the solution of the problem. Any pointers? Any git
trees
of mmc driver changes we could try? Anybody else with a MX25 that
has
this issue?
does that attached patch fix your problem ?
Hi Joan Carles,
Le Tue, 27 Mar 2012 10:46:45 +0200,
joancarles joancar...@fqingenieria.es a écrit :
This is still present, and we have absolutely no idea where to
continue
searching for the solution of the problem. Any pointers? Any git
trees
of mmc driver changes we could try?
does that attached patch fix your problem ?
YES, indeed it does to a certain degree. The timeout errors do not
occur anymore and I can successfully perform many fs-ops, such as
Interesting question is now why it worked on your older kernel? The code
around BROKEN_TIMEOUT is there for much
Hi Wolfram,
Le Tue, 27 Mar 2012 11:01:49 +0200,
Wolfram Sang w.s...@pengutronix.de a écrit :
does that attached patch fix your problem ?
YES, indeed it does to a certain degree. The timeout errors do not
occur anymore and I can successfully perform many fs-ops, such as
Interesting
Interesting question is now why it worked on your older kernel? The code
around BROKEN_TIMEOUT is there for much longer, I'd think.
not in fact it seems to have been broken from a long time and I think
I know and you are saying the same, in fact :) Your patch came in around
2.6.37 and
Le Tue, 27 Mar 2012 11:14:25 +0200,
Wolfram Sang w.s...@pengutronix.de a écrit :
Interesting question is now why it worked on your older kernel? The code
around BROKEN_TIMEOUT is there for much longer, I'd think.
not in fact it seems to have been broken from a long time and I think
Hi
Interesting question is now why it worked on your older kernel? The
code
around BROKEN_TIMEOUT is there for much longer, I'd think.
not in fact it seems to have been broken from a long time and I think
I'm responsible of that in 37865fe91582582a6f6c00652f6a2b1ff71f8a78
mmc:
well I should have said enough extensive tests as I did a lot of tests
on the 3 archs (i.MX25, i.MX35 and i.MX51). What I see here is that on
i.MX35 and i.MX51 the problem is very easy to reproduce without
extensive tests (card not detected) and that on i.MX25 it needs more
tests as the card
Hi,
Le Tue, 27 Mar 2012 11:33:57 +0200,
joancarles joancar...@fqingenieria.es a écrit :
Interesting question is now why it worked on your older kernel? The
code
around BROKEN_TIMEOUT is there for much longer, I'd think.
not in fact it seems to have been broken from a long time and I
Might be unrelated, however I have been keeping my eyes on the fix
of ENGcm07207 quirk introduced with 16a790bcc. According to the
IMX25CE.pdf, to abort data transfers on the AHB, software can reset
the eSDHC by writing 1 to SYSCTL[24] (RSTA), which currently is not
done with
Hi
Might be unrelated, however I have been keeping my eyes on the fix
of
ENGcm07207 quirk introduced with 16a790bcc. According to the
IMX25CE.pdf, to abort data transfers on the AHB, software can reset
the
eSDHC by writing 1 to SYSCTL[24] (RSTA), which currently is not done
with
Hi Eric:
I'm on my business trip out of my FSL office, can't reproduce this issue on
i.MX25 board now.
Sorry about that.
Best Regards
Richard Zhu
-Original Message-
From: Eric Bénard [mailto:e...@eukrea.com]
Sent: 2012年3月27日 3:58
To: joancarles
Cc: Zhu Richard-R65037;
Hi Kukjin,
On Tue, Feb 21 2012, Chris Ball wrote:
On Tue, Feb 21 2012, Kukjin Kim wrote:
I created topic branch for this we talked. You can pull that following:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
v3.4-for-cjb
If any problems, please kindly let me know.
On Tuesday 31 January 2012, Thomas Abraham wrote:
+
+Optional Board Specific Properties:
+- samsung,sdhci-bus-width: Number of data lines connected to the controller.
+ Note: This excludes the clock,command and card detect lines. If this
property
+ is not specified, default value is 1.
+
On Tuesday 31 January 2012, Thomas Abraham wrote:
+
+Optional Board Specific Properties:
+- samsung,sdhci-bus-width: Number of data lines connected to the controller.
+ Note: This excludes the clock,command and card detect lines. If this
property
+ is not specified, default value is 1.
+
Hi,
On Mon, Mar 26, 2012 at 12:00:27PM +0530, Subhash Jadavani wrote:
Actually we are already printing the HS200/DDR (for eMMC) bus speed mode
along with card detected print. So why not bus speed mode for UHS-I cards.
It really gives good impression to user what this card is capable of
--- Original Message ---
Sender : Jongman Heojongman@samsung.com S5/Senior Engineer/STB S/W RD
Lab./Samsung Electronics
Date : 2012-03-20 11:07 (GMT+09:00)
Title : mmc_blk_ioctl_cmd: cmd error -110, when I try set writeprotect to
user data area
Hi, all,
I'm seeing weird
26 matches
Mail list logo
