From: Jeff Garzik <jeff@garzik.org>
To: Pierre TARDY <pierre.tardy@freescale.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] smc911x
Date: Tue, 26 Dec 2006 16:30:22 -0500 [thread overview]
Message-ID: <4591946E.2000404@garzik.org> (raw)
In-Reply-To: <45881B41.1070109@freescale.com>
Pierre TARDY wrote:
> Attached a patch on smc911x driver, which corrects obvious errors in the
> 16bit chips support of this driver.
>
> Please note that this driver still do NOT support 16bit chips (9115 and
> 9117), as it claims to, there may be mistakes in the data fifo
> managment, this patch enable the driver to init the chip, but the data
> is then corrupted.
>
> I managed to make my chip work with the driver smsc911x (out of the
> box), from smsc, which has been refused to be included in the kernel tree.
> http://thread.gmane.org/gmane.linux.network.general/10498/focus=40384
>
> I think it my be a good idea to reconsider this choice
> - smsc911x has more chance to be supported as it has originally been
> made by the manufacturer of the chip.
> - smc911x is mono chip (do not work with 9117 at least), mono arch and
> mono plateform (restricted to PXA), while smsc911x has been tested on
> various chips by smsc
>
> The only thing that is missing in smsc911x is dma support, which is very
> architecture dependant ( There is one way to do dma with the pxa,
> another on the freescale mxc plateforms, another on the x86..)
ACK the patch, but please follow standard patch format
(http://linux.yyz.us/patch-format.html), chiefly you should always
include a Signed-off-by line, and avoid MIME attachments.
Jeff
prev parent reply other threads:[~2006-12-26 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 17:02 [PATCH] smc911x Pierre TARDY
2006-12-26 21:30 ` Jeff Garzik [this message]
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=4591946E.2000404@garzik.org \
--to=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=pierre.tardy@freescale.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;
as well as URLs for NNTP newsgroup(s).