linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Tim Yamin" <plasm@roo.me.uk>
To: "Daniel Schnell" <daniel.schnell@marel.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH]: [MPC5200] Add ATA DMA support
Date: Wed, 6 Aug 2008 13:18:13 +0100	[thread overview]
Message-ID: <792f5f410808060518r5e2c0124i2cfef450e264f012@mail.gmail.com> (raw)
In-Reply-To: <DD39B5C3F4963040ADC9768BE7E430CB03202EDF@is-hdq-exchange.marel.net>

On Wed, Aug 6, 2008 at 12:58 PM, Daniel Schnell
<daniel.schnell@marel.com> wrote:
> Hi,
>
> Sorry for testing this patch so late, but I get these if I apply your
> patch to 2.6.24.7 and use it with my Sandisk Extreme IV 4GB card:

Hi,

What board are you using? DMA requires a few more signals to be routed
through correctly to the CF card slot so maybe that's your problem...

Tim

  reply	other threads:[~2008-08-06 12:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17  8:28 [PATCH]: [MPC5200] Add ATA DMA support Tim Yamin
2008-08-06 11:58 ` Daniel Schnell
2008-08-06 12:18   ` Tim Yamin [this message]
2008-08-06 13:26     ` Daniel Schnell
2008-08-06 14:31       ` Daniel Schnell
     [not found] <DD39B5C3F4963040ADC9768BE7E430CB03202F4F@is-hdq-exchange.marel.net>
     [not found] ` <DD39B5C3F4963040ADC9768BE7E430CB03203863@is-hdq-exchange.marel.net>
     [not found]   ` <792f5f410808111319m20d6e09bi8e9782da1fdd4aab@mail.gmail.com>
     [not found]     ` <DD39B5C3F4963040ADC9768BE7E430CB0320387D@is-hdq-exchange.marel.net>
     [not found]       ` <792f5f410808111431g8fafba1n3b10468da0d165bf@mail.gmail.com>
     [not found]         ` <DD39B5C3F4963040ADC9768BE7E430CB03203A7B@is-hdq-exchange.marel.net>
     [not found]           ` <792f5f410808120643md72e679o39692c4bfa3f285e@mail.gmail.com>
     [not found]             ` <DD39B5C3F4963040ADC9768BE7E430CB03203A94@is-hdq-exchange.marel.net>
     [not found]               ` <792f5f410808120730j7b4be4f2n7a40de880178ccca@mail.gmail.com>
     [not found]                 ` <DD39B5C3F4963040ADC9768BE7E430CB03203ADC@is-hdq-exchange.marel.net>
     [not found]                   ` <792f5f410808120830v311e0446kc8fddfb97d0b9ea6@mail.gmail.com>
2008-08-12 17:30                     ` Daniel Schnell
2008-08-13  5:57                       ` Tim Yamin
2008-08-13  6:02                         ` Grant Likely
2008-08-13  6:06                           ` Tim Yamin
2008-08-13  6:11                             ` Grant Likely
2008-08-13  9:07                               ` Tim Yamin
2008-09-15  5:54                                 ` Grant Likely
2008-10-29 15:34                                   ` Matt Sealey
2008-11-11 14:04                                 ` Lehmann, Hans (Ritter Elektronik)
2008-11-11 14:35                                   ` Matt Sealey
  -- strict thread matches above, loose matches on Subject: below --
2008-09-05 18:29 WITTROCK
     [not found] <AclPDG6qSkF9cHawTOKR6zBfDIjvgg==>
2008-11-25 14:45 ` AW: " Lehmann, Hans (Ritter Elektronik)
2008-11-25 15:19   ` Matt Sealey
2008-12-20  7:15     ` Grant Likely
2008-12-20  7:18   ` Grant Likely
2009-01-05  9:25     ` AW: " Lehmann, Hans (Ritter Elektronik)
2009-01-05 15:31       ` Grant Likely
2009-07-09 14:24         ` Roman Fietze

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=792f5f410808060518r5e2c0124i2cfef450e264f012@mail.gmail.com \
    --to=plasm@roo.me.uk \
    --cc=daniel.schnell@marel.com \
    --cc=linuxppc-dev@ozlabs.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).