netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: davem@davemloft.net, netdev@vger.kernel.org, jmorrow@jmorrow.org,
	jmorrow@massspec.com
Subject: Re: [patch 2/2] bugfixes and new hardware support for arcnet driver
Date: Sat, 17 Feb 2007 15:31:39 -0500	[thread overview]
Message-ID: <45D7662B.2020502@garzik.org> (raw)
In-Reply-To: <200702160942.l1G9gRpM026492@shell0.pdx.osdl.net>

akpm@linux-foundation.org wrote:
> From: Jeff Morrow <jmorrow@jmorrow.org>
> 
> The modifications and bug fixes noted below were done by Realtime Control
> Works and Contemporary Control Systems, Inc, Jan 2005.  They were
> incorporated into the 2.6 kernel by Jeff Morrow of Sierra Analytics, Feb
> 2007.  <jmorrow@massspec.com>
> 
> The changes have been tested on a Contemporary Controls PCI20U-4000.
> 
> Summary of changes:
> 
> Arc-rawmode.c:
>       rx():
>       - Fixed error in received packet lengths; 256 byte packets were
>         being received as 257 bytes packets.
> 
>       prepare_tx():
>       - Fixed error in transmit length calcs; 257 byte packets were being
>         transmitted as 260 byte packets.
> 
> com20020.c:
>       com20020_check():
>       - We now load the SETUP2 register if the 'clockm' parameter is
>         non-zero, instead of checking for ARC_CAN_10MBIT. The user is
>         now responsible for whether or not SETUP2 is loaded.  If the
>         clock multiplier is non-zero, this means that the user wants a
>         baud rate greater than 2.5Mbps. This is not possible unless the
>         SETUP2 register is present (COM20020D, or COM20022). So, we're
>         relying on the user to be smart about what kind of chip he's
>         dealing with...
> 
> com20020-pci.c
>       - Added several entries to com20020pci_id_table[].
> 
> Signed-off-by: Jeff Morrow <jmorrow@massspec.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Jeff Garzik <jeff@garzik.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

applied




      reply	other threads:[~2007-02-17 20:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16  9:42 [patch 2/2] bugfixes and new hardware support for arcnet driver akpm
2007-02-17 20:31 ` 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=45D7662B.2020502@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=jmorrow@jmorrow.org \
    --cc=jmorrow@massspec.com \
    --cc=netdev@vger.kernel.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).