On 1 June 2012 09:35, Adrian Hunter adrian.hun...@intel.com wrote:
On 29/05/12 05:32, Ben Hutchings wrote:
On Mon, 2012-05-28 at 18:31 +0100, Torne (Richard Coles) wrote:
From: Torne (Richard Coles) to...@google.com
MMC CSD info can specify very large, ridiculous timeouts, big enough
On 1 June 2012 10:31, Torne (Richard Coles) to...@google.com wrote:
On 1 June 2012 09:35, Adrian Hunter adrian.hun...@intel.com wrote:
On 29/05/12 05:32, Ben Hutchings wrote:
On Mon, 2012-05-28 at 18:31 +0100, Torne (Richard Coles) wrote:
From: Torne (Richard Coles) to...@google.com
MMC CSD
On 1 June 2012 11:09, Adrian Hunter adrian.hun...@intel.com wrote:
On 01/06/12 12:32, Torne (Richard Coles) wrote:
On 1 June 2012 10:31, Torne (Richard Coles) to...@google.com wrote:
On 1 June 2012 09:35, Adrian Hunter adrian.hun...@intel.com wrote:
On 29/05/12 05:32, Ben Hutchings wrote
On 1 June 2012 13:59, Adrian Hunter adrian.hun...@intel.com wrote:
On 01/06/12 13:20, Torne (Richard Coles) wrote:
On 1 June 2012 11:09, Adrian Hunter adrian.hun...@intel.com wrote:
On 01/06/12 12:32, Torne (Richard Coles) wrote:
On 1 June 2012 10:31, Torne (Richard Coles) to...@google.com
From: Torne (Richard Coles) to...@google.com
MMC CSD info can specify very large, ridiculous timeouts, big enough to
overflow timeout_ns. This can result in the card timing out on every
operation because the wrapped timeout value is far too small.
Fix the overflow by capping the result
On 31 May 2012 11:00, Ulf Hansson ulf.hans...@linaro.org wrote:
Hi Richard,
On 29 May 2012 17:02, Torne (Richard Coles) to...@google.com wrote:
From: Torne (Richard Coles) to...@google.com
MMC CSD info can specify very large, ridiculous timeouts, big enough to
overflow timeout_ns on 32-bit
On 29 May 2012 03:32, Ben Hutchings b...@decadent.org.uk wrote:
On Mon, 2012-05-28 at 18:31 +0100, Torne (Richard Coles) wrote:
From: Torne (Richard Coles) to...@google.com
MMC CSD info can specify very large, ridiculous timeouts, big enough to
overflow timeout_ns on 32-bit machines. This can
From: Torne (Richard Coles) to...@google.com
MMC CSD info can specify very large, ridiculous timeouts, big enough to
overflow timeout_ns on 32-bit machines. This can result in the card
timing out on every operation because the wrapped timeout value is far
too small.
Fix the overflow by capping
From: Torne (Richard Coles) to...@google.com
MMC CSD info can specify very large, ridiculous timeouts, big enough to
overflow timeout_ns on 32-bit machines. This can result in the card
timing out on every operation because the wrapped timeout value is far
too small.
Fix the overflow by capping
From: Torne (Richard Coles) to...@google.com
MMC CSD info can specify very large, ridiculous timeouts, big enough to
overflow timeout_ns on 32-bit machines. This can result in the card
timing out on every operation because the wrapped timeout value is far
too small.
Fix the overflow
Ping.. anyone interested in this patch? :) It's been a couple weeks
with no response.
It still applies cleanly to the current tree.
On 6 March 2012 10:27, Torne (Richard Coles) to...@google.com wrote:
From: Torne (Richard Coles) to...@google.com
Some MMC cards specify timeouts that are larger
From: Torne (Richard Coles) to...@google.com
Some MMC cards specify timeouts that are larger than the highest
possible timeout in the host controller. sdhci is the only host
controller driver which complains about this; remove the warning to
match the behaviour of the other drivers.
Signed-off
12 matches
Mail list logo
