From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-kernel@vger.kernel.org, linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH] New IDE/block driver for OCTEON SOC Compact Flash interface.
Date: Fri, 14 Nov 2008 03:15:24 +0300 [thread overview]
Message-ID: <491CC31C.7090606@ru.mvista.com> (raw)
In-Reply-To: <491CC0B6.8020400@ru.mvista.com>
Hello, I wrote:
>> As part of our efforts to get the Cavium OCTEON processor support
>> merged (see: http://marc.info/?l=linux-mips&m=122600487218824), we
>> have this CF driver for your consideration.
>>
>> Most OCTEON variants have *no* DMA or interrupt support on the CF
>> interface so a simple bit-banging approach is taken. Although if DMA is
>> available, we do take advantage of it.
>>
>> The register definitions are part of the chip support patch set
>> mentioned above, and are not included here.
>>
>> At this point I would like to get feedback as to whether this is a
>> good approach for the CF driver, or perhaps generate ideas about other
>> possible approaches.
>
> It's totally unacceptable for drivers/ide/ as this is
> self-containeed driver no using IDE core for anything, so this can
> only fit well to drivers/block/.
I probably need to clarify that it will hardly be accepted into
drivers/block/ as well, being a mere CF driver.
MBR, Sergei
next prev parent reply other threads:[~2008-11-14 0:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 19:25 [PATCH] New IDE/block driver for OCTEON SOC Compact Flash interface David Daney
2008-11-14 0:05 ` Sergei Shtylyov
2008-11-14 0:15 ` Sergei Shtylyov [this message]
2008-11-14 0:31 ` David Daney
2008-11-14 10:22 ` Sergei Shtylyov
2008-11-14 1:18 ` Alan Cox
2008-11-14 10:04 ` Sergei Shtylyov
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=491CC31C.7090606@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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