public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rogério Brito" <rbrito@ime.usp.br>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jeff Garzik <jeff@garzik.org>, Michael Tokarev <mjt@tls.msk.ru>,
	Mark Lord <lkml@rtr.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: Quick question about libata and hdparm
Date: Thu, 23 Apr 2009 02:56:19 -0300	[thread overview]
Message-ID: <20090423055618.GA23042@ime.usp.br> (raw)
In-Reply-To: <200904211459.26965.bzolnier@gmail.com>

Hi, Bart, Alan.

On Apr 21 2009, Bartlomiej Zolnierkiewicz wrote:
> Incremental patch (a certain theory to verify).
(...)
> +	/* FIXME: this thrashes internal UDMA timings previously set by
> +	   controller on SET FEATURES - XFER MODE command "snooping" */
>  	/* The DMA clocks may have been trashed by a reset. FIXME: make conditional
>  	   and move to qc_issue ? */
> -	pdc202xx_set_dmamode(ap, qc->dev);
> +	/* pdc202xx_set_dmamode(ap, qc->dev); */

This didn't work. I still get those same messages. If you want, I can try
compiling the 2.6.30-rc3 kernel that was released now (as I mentioned
before, I was using 2.6.29).

I can test whatever you want me to.


Thanks,

-- 
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org

  reply	other threads:[~2009-04-23  6:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  0:22 Quick question about libata and hdparm Rogério Brito
2009-04-19  6:31 ` Robert Hancock
2009-04-19 12:33 ` Mark Lord
2009-04-19 12:44   ` Michael Tokarev
2009-04-19 12:57     ` Jeff Garzik
2009-04-19 13:06       ` Michael Tokarev
2009-04-19 20:11       ` Rogério Brito
2009-04-19 21:27         ` Jeff Garzik
2009-04-20 17:35           ` Rogério Brito
2009-04-20 18:40             ` Alan Cox
2009-04-20 20:41               ` Rogério Brito
2009-04-20 21:16                 ` Alan Cox
2009-04-20 20:31             ` Bartlomiej Zolnierkiewicz
2009-04-20 20:45               ` Rogério Brito
2009-04-20 21:19               ` Alan Cox
2009-04-20 22:57                 ` Rogério Brito
2009-04-21  5:32                 ` Rogério Brito
2009-04-21 12:59                   ` Bartlomiej Zolnierkiewicz
2009-04-23  5:56                     ` Rogério Brito [this message]
2009-04-23 21:31                       ` Bartlomiej Zolnierkiewicz
2009-04-24  3:00                         ` Rogério Brito
2009-05-01  9:18                           ` Rogério Brito
2009-05-01 10:31                             ` Alan Cox
2009-05-01 11:50                               ` Rogério Brito
2009-05-01 13:16                                 ` Alan Cox
2009-05-01 14:19                                 ` Rogério Brito
2009-05-01 11:20                             ` Bartlomiej Zolnierkiewicz
2009-05-11 18:34               ` Jeff Garzik
2009-04-19 20:03   ` Rogério Brito
2009-04-19 23:41     ` Mark Lord

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=20090423055618.GA23042@ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=mjt@tls.msk.ru \
    /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