From: David Brownell <david-b@pacbell.net>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
linux-kernel@vger.kernel.org,
Shannon Nelson <shannon.nelson@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
kernel@avr32linux.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [RFC 4/4] Atmel MCI: Driver for Atmel on-chip MMC controllers
Date: Sat, 24 Nov 2007 10:48:39 -0800 [thread overview]
Message-ID: <200711241048.39990.david-b@pacbell.net> (raw)
In-Reply-To: <20071124191648.2c2d56c7@siona>
On Saturday 24 November 2007, Haavard Skinnemoen wrote:
> >
> > Why is this needed and is it perhaps something that can be moved to
> > the MMC core?
>
> We used to have lots of problems with overruns and underruns and those
> parameters were useful to limit the transfer rate. Now that the RDPROOF
> and WRPROOF bits seem to have taken care of these problems for good, I
> guess we can remove this parameter.
Not all silicon *has* those bits though, right? Like at91rm9200.
next prev parent reply other threads:[~2007-11-24 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 12:20 [RFC 0/4] dmaengine: Slave DMA interface and example users Haavard Skinnemoen
2007-11-23 12:20 ` [RFC 1/4] dmaengine: Add slave DMA interface Haavard Skinnemoen
2007-11-23 12:20 ` [RFC 2/4] dmaengine: Make DMA Engine menu visible for AVR32 users Haavard Skinnemoen
2007-11-23 12:20 ` [RFC 3/4] dmaengine: Driver for the Synopsys DesignWare DMA controller Haavard Skinnemoen
2007-11-23 12:20 ` [RFC 4/4] Atmel MCI: Driver for Atmel on-chip MMC controllers Haavard Skinnemoen
2007-11-24 17:00 ` Pierre Ossman
2007-11-24 18:16 ` Haavard Skinnemoen
2007-11-24 18:48 ` David Brownell [this message]
2007-11-24 19:24 ` Haavard Skinnemoen
2007-12-03 19:20 ` [RFC 1/4] dmaengine: Add slave DMA interface Dan Williams
2007-12-05 15:53 ` Haavard Skinnemoen
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=200711241048.39990.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=dan.j.williams@intel.com \
--cc=drzeus-list@drzeus.cx \
--cc=hskinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=shannon.nelson@intel.com \
/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.