From: "Alfredo Jesús Delaiti" <alfredodelaiti@netscape.net>
To: linux-media@vger.kernel.org
Subject: Re: How I must report that a driver has been broken?
Date: Fri, 18 May 2012 11:15:17 -0300 [thread overview]
Message-ID: <4FB65975.3000806@netscape.net> (raw)
In-Reply-To: <CAGoCfiyumZmX8PkPU_UQee4kpd82OBKF=1awLAmuL1WOcE=buQ@mail.gmail.com>
Hi
Thank you all for your responses.
Devin, I appreciate the time and labor you do to revise the code.
My previous letters maybe I can help you see where the problem and the
date you began.
I thought of a patch of this type:
if (card != mycard) {
"bad code for my card"}
but unfortunately not so easy for me.
I will be patient.
Thank you.
Alfredo
El 14/05/12 01:51, Devin Heitmueller escribió:
> On Sun, May 13, 2012 at 1:50 AM, Hans de Goede<hdegoede@redhat.com> wrote:
>> Hi,
>>
>>
>> On 05/12/2012 09:26 PM, Alfredo Jesús Delaiti wrote:
>>> Hi
>>>
>>> Thanks for your response Hans and Patrick
>>>
>>> Maybe I doing wrong this, because it reports twice:
>>>
>>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg45199.html
>>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg44846.html
>>
>> In your last message you indicate that you've found the patch causing it,
>> and that you were looking into figuring which bit of the patch actually
>> breaks things, so I guess people reading the thread were / are
>> waiting for you to follow up on it with the results of your attempts
>> to further isolate the cause.
>>
>> What I were do if I were you is send a mail directly to the author
>> of the patch causing the problems, with what you've discovered
>> about the problem sofar in there, and put the list in the CC.
>>
>> Regards,
>>
>> Hans
> Steven loaned me his HVR-1850 board last week, and I'm hoping to debug
> the regression this week (I have an HVR-1800 that is also effected).
> I suspect the problem is related to a codepath for the cx23888's
> onboard DIF being executed for 885 based boards. Steven did a whole
> series of patches to make the cx23888 work properly and I think a
> regression snuck in there. Simply backing out the change isn't the
> correct fix.
>
> I've got all the boards and the datasheets - I just need to find a bit
> of time to get the current tree installed onto a machine and plug in
> the various boards...
>
> In short, it's in my queue so please be patient.
>
> Devin
>
--
Dona tu voz
http://www.voxforge.org/es
next prev parent reply other threads:[~2012-05-18 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 4:26 How I must report that a driver has been broken? Alfredo Jesús Delaiti
2012-05-12 8:17 ` Hans de Goede
2012-05-12 19:26 ` Alfredo Jesús Delaiti
2012-05-13 0:29 ` Patrick Dickey
2012-05-13 5:50 ` Hans de Goede
2012-05-14 4:51 ` Devin Heitmueller
2012-05-18 14:15 ` Alfredo Jesús Delaiti [this message]
2012-05-18 14:26 ` Devin Heitmueller
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=4FB65975.3000806@netscape.net \
--to=alfredodelaiti@netscape.net \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).