From: dmitry pervushin <dpervushin@gmail.com>
To: Vitaly Wool <vwool@ru.mvista.com>
Cc: Greg KH <greg@kroah.com>, David Brownell <david-b@pacbell.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
akpm@osdl.org, basicmark@yahoo.com, komal_shah802003@yahoo.com,
stephen@streetfiresound.com,
spi-devel-general@lists.sourceforge.net, Joachim_Jaeger@digi.com
Subject: Re: [spi-devel-general] Re: [PATCH/RFC] SPI: add DMAUNSAFE analog to David Brownell's core
Date: Thu, 15 Dec 2005 13:00:17 +0300 [thread overview]
Message-ID: <1134640817.5596.4.camel@fj-laptop> (raw)
In-Reply-To: <43A05C32.3070501@ru.mvista.com>
On Wed, 2005-12-14 at 20:53 +0300, Vitaly Wool wrote:
> Greg KH wrote:
>
> >What is the speed of your SPI bus?
> >
> >And what are your preformance requirements?
> >
> >
> The maximum frequency for the SPI bus is 26 MHz, WLAN driver is to work
> at true 10 Mbit/sec.
My two cents: the faster is better; SPI bus itself can work on 52MHz,
and AFAIK WLAN developers limit the speed due to their firmware
reqiorements.
>
> Vitaly
>
> P. S. I'm speaking not about this particular case during most part of
> this conversation. Sound cards behind the SPI bus will suffer a lot more
> since it's their path to use wXrY functions (lotsa small transfers)
> rather than WLAN's.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> spi-devel-general mailing list
> spi-devel-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/spi-devel-general
>
>
next prev parent reply other threads:[~2005-12-15 10:09 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 15:20 [PATCH 2.6-git 0/4] SPI core refresh Vitaly Wool
2005-12-12 15:22 ` [PATCH 2.6-git 1/4] SPI core refresh: SPI core patch Vitaly Wool
2005-12-12 15:49 ` Russell King
2005-12-12 15:24 ` [PATCH 2.6-git 2/4] SPI core refresh: MTD dataflash driver Vitaly Wool
2005-12-12 15:26 ` [PATCH 2.6-git 3/4] SPI core refresh: SPI/PNX controller Vitaly Wool
2005-12-12 15:27 ` [PATCH 2.6-git 4/4] SPI core refresh: dumb EEPROM driver Vitaly Wool
2005-12-12 18:01 ` [PATCH 2.6-git 0/4] SPI core refresh Rui Sousa
2005-12-13 12:09 ` [spi-devel-general] " dmitry pervushin
2005-12-13 15:11 ` Rui Sousa
2005-12-13 17:06 ` dmitry pervushin
2005-12-14 6:57 ` Vitaly Wool
2005-12-14 14:28 ` Rui Sousa
2005-12-13 16:35 ` David Brownell
2005-12-13 18:02 ` Rui Sousa
2005-12-13 14:06 ` [PATCH/RFC] SPI: add async message handing library to David Brownell's core Vitaly Wool
2005-12-13 16:53 ` [PATCH/RFC] SPI: add DMAUNSAFE analog " Vitaly Wool
2005-12-13 19:01 ` David Brownell
2005-12-13 19:15 ` Greg KH
2005-12-14 13:50 ` Vitaly Wool
2005-12-14 17:18 ` Greg KH
2005-12-14 17:53 ` Vitaly Wool
2005-12-14 18:50 ` [PATCH/RFC] SPI: add DMAUNSAFE analog David Brownell
2005-12-14 19:29 ` Vitaly Wool
2005-12-14 19:02 ` [PATCH/RFC] SPI: add DMAUNSAFE analog to David Brownell's core David Brownell
2005-12-14 19:19 ` Vitaly Wool
2005-12-14 19:33 ` [spi-devel-general] Re: [PATCH/RFC] SPI: add DMAUNSAFE analog David Brownell
2005-12-14 19:34 ` [PATCH/RFC] SPI: add DMAUNSAFE analog to David Brownell's core Vitaly Wool
2005-12-15 6:47 ` Vitaly Wool
2005-12-15 16:44 ` Greg KH
2005-12-15 22:23 ` Vitaly Wool
2005-12-15 23:02 ` Greg KH
2005-12-16 8:37 ` Vitaly Wool
2005-12-16 17:34 ` Greg KH
2005-12-16 18:32 ` [spi-devel-general] Re: [PATCH/RFC] SPI: add DMAUNSAFE analog David Brownell
2005-12-15 20:06 ` David Brownell
2005-12-15 22:17 ` Vitaly Wool
2005-12-15 22:33 ` Greg KH
2005-12-16 3:34 ` Andy Isaacson
2005-12-16 5:17 ` Greg KH
2005-12-14 19:16 ` [PATCH/RFC] SPI: add DMAUNSAFE analog to David Brownell's core Greg KH
2005-12-14 19:30 ` Vitaly Wool
2005-12-15 10:00 ` dmitry pervushin [this message]
2005-12-14 17:22 ` David Brownell
2005-12-14 17:50 ` Vitaly Wool
2005-12-14 19:17 ` [PATCH/RFC] SPI: add DMAUNSAFE analog David Brownell
2005-12-14 20:11 ` Vitaly Wool
2005-12-13 21:47 ` [PATCH/RFC] SPI: add DMAUNSAFE analog to David Brownell's core Vitaly Wool
2005-12-13 22:15 ` Vitaly Wool
2005-12-14 16:55 ` David Brownell
2005-12-14 17:23 ` Vitaly Wool
2005-12-14 18:48 ` [PATCH/RFC] SPI: add async message handing library " Stephen Street
2005-12-14 19:41 ` Vitaly Wool
2005-12-14 21:19 ` Stephen Street
2005-12-14 19:31 ` [PATCH/RFC] SPI: add async message handing library David Brownell
2005-12-15 12:19 ` [PATCH/RFC] SPI: async message handing library update Vitaly Wool
2005-12-18 18:59 ` David Brownell
2005-12-19 15:40 ` [spi-devel-general] " dmitry pervushin
2005-12-20 7:23 ` David Brownell
2005-12-20 18:02 ` Vitaly Wool
2005-12-22 17:28 ` David Brownell
2005-12-22 22:10 ` Vitaly Wool
2005-12-22 23:55 ` David Brownell
2005-12-21 13:17 ` Vitaly Wool
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=1134640817.5596.4.camel@fj-laptop \
--to=dpervushin@gmail.com \
--cc=Joachim_Jaeger@digi.com \
--cc=akpm@osdl.org \
--cc=basicmark@yahoo.com \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=komal_shah802003@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=stephen@streetfiresound.com \
--cc=vwool@ru.mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®