From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: Baruch Siach <baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Claudio Lanconelli
<lanconelli.claudio-DtroZxfa9uMAvxtiuMwx3w@public.gmane.org>,
Shachar Shemesh <shachar-bEkjeIDUMOLQT0dZR+AlfA@public.gmane.org>,
Network development list
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] enc28j60: Fix sporadic packet loss (correction)
Date: Tue, 2 Dec 2008 14:44:02 -0800 [thread overview]
Message-ID: <200812021444.03225.david-b@pacbell.net> (raw)
In-Reply-To: <20081202213459.GA3361@tarshish>
On Tuesday 02 December 2008, Baruch Siach wrote:
> Hi David,
>
> On Tue, Dec 02, 2008 at 01:05:05PM -0800, David Brownell wrote:
> > Seems plausible to me, but network patches should be submitted
> > to the netdev list. :)
>
> So I did after Claudio suggested the same (and acked the patch).
Good, thanks.
> > p.s. Just for info ... what kind of Linux system are you using
> > this driver on?
>
> I'm using this driver on a custom chip that includes ARM926 core. The kernel
> version is (currently) 2.6.26. The SPI bus on this chip is the only way to
> connect peripherals. That's way we're stuck with this Ethernet interface.
It's a bit sub-optimal ... but I'm glad you've got that option! :)
> Our on-chip SPI master is the Synopsys DesignWare one. I wrote a driver for
> this SPI master. This driver is somewhat usable, but not complete yet. I'm now
> in the process of adding DMA support to the driver (PL080) to overcome some
> nasty design peculiarities of this SPI master.
>
> Peter Pearse has poster a (incomplete) patch set with a driver for the PL080
> DMA controller to the LAKL last week, but I see no push for integrating it
> into the mainline. So I doubt there's any great value in this SPI master
> driver as of now.
I certainly wouldn't expect that on the ARM list. It's
not exactly the responsibility of that list to address
anything other than arch/arm/* goodies.
Post it to the SPI list instead. If it's useful to you,
it could well be useful to others... I'd have no problems
merging such a driver, if it's reasonably clean/correct
and is known to work well enough to support enc28j60.
- Dave
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
next prev parent reply other threads:[~2008-12-02 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081202085947.GB24490@diamond.tkos.co.il>
2008-12-02 21:05 ` [spi-devel-general] [PATCH] enc28j60: Fix sporadic packet loss (correction) David Brownell
2008-12-02 21:35 ` Baruch Siach
2008-12-02 22:44 ` David Brownell [this message]
2008-12-03 6:22 ` Baruch Siach
2008-12-03 7:04 ` David Brownell
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=200812021444.03225.david-b@pacbell.net \
--to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
--cc=baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org \
--cc=lanconelli.claudio-DtroZxfa9uMAvxtiuMwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shachar-bEkjeIDUMOLQT0dZR+AlfA@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).