From: Philip Balister <philip@balister.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Ben Hilburn <ben@ettus.com>, meta-ti@lists.yoctoproject.org
Subject: Re: [PATCH] linux-ti33x-psp 3.1: add dto patch to fix problems with various sd cards
Date: Thu, 26 Jan 2012 15:35:23 -0500 [thread overview]
Message-ID: <4F21B90B.9020103@balister.org> (raw)
In-Reply-To: <F17AE0E2-A005-4000-A122-3C7BA4393875@dominion.thruhere.net>
On 01/26/2012 01:12 PM, Koen Kooi wrote:
>
> Op 26 jan. 2012, om 19:01 heeft Tom Rini het volgende geschreven:
>
>> On Thu, Jan 26, 2012 at 10:38 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
>>
>> I know the patch isn't yours but should we perhaps go in and make the
>> patch more obvious? The function we're patching does a lot of
>> guesswork to find 'dto' and then we just say 'use the max'. Why not
>> also go rip out that logic?
>
> I was having the same conversation with Philip Balister on IRC just now :) It seems that this patch is being used by various TI customers to magically fix things so we do need to come up with a proper solution.
Basically, we are pissed of with really annoying SD card failures. (This
is an understatement, the problem cost me a lot of sleep at ELCE)
Unless someone has a better solution, we should rip out the hairy
calculation and set dto to 14 al the time and send the patch upstream.
Does anyone see any reason not to do this?
Philip
next prev parent reply other threads:[~2012-01-26 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 17:38 [PATCH] linux-ti33x-psp 3.1: add dto patch to fix problems with various sd cards Koen Kooi
2012-01-26 18:01 ` Tom Rini
2012-01-26 18:12 ` Koen Kooi
2012-01-26 20:35 ` Philip Balister [this message]
2012-01-26 20:37 ` Maupin, Chase
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F21B90B.9020103@balister.org \
--to=philip@balister.org \
--cc=ben@ettus.com \
--cc=koen@dominion.thruhere.net \
--cc=meta-ti@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.