From: akpm@linux-foundation•org
To: jeff@garzik•org
Cc: netdev@vger•kernel.org, akpm@linux-foundation•org,
jailbird@alcatraz•fdf.net, ink@jurassic•park.msu.ru,
romieu@fr•zoreil.com
Subject: [patch 04/18] via-rhine: disable rx_copybreak on archs that don't allow unaligned DMA access
Date: Fri, 10 Aug 2007 14:05:15 -0700 [thread overview]
Message-ID: <200708102105.l7AL5FUp008954@imap1.linux-foundation.org> (raw)
From: Dustin Marquess <jailbird@alcatraz•fdf.net>
Patch to disable the rx_copybreak feature on hardware architectures that
don't allow unaligned DMA access.
#ifdef code taken from tulip_core.c. Problem pointed out by Ivan
Kokshaysky.
Signed-off-by: Dustin Marquess <jailbird@alcatraz•fdf.net>
Cc: Francois Romieu <romieu@fr•zoreil.com>
Cc: Ivan Kokshaysky <ink@jurassic•park.msu.ru>
Cc: Jeff Garzik <jeff@garzik•org>
Signed-off-by: Andrew Morton <akpm@linux-foundation•org>
---
drivers/net/via-rhine.c | 6 ++++++
1 files changed, 6 insertions(+)
diff -puN drivers/net/via-rhine.c~via-rhine-disable-rx_copybreak-on-archs-that drivers/net/via-rhine.c
--- a/drivers/net/via-rhine.c~via-rhine-disable-rx_copybreak-on-archs-that
+++ a/drivers/net/via-rhine.c
@@ -42,7 +42,13 @@ static int max_interrupt_work = 20;
/* Set the copy breakpoint for the copy-only-tiny-frames scheme.
Setting to > 1518 effectively disables this feature. */
+#if defined(__alpha__) || defined(__arm__) || defined(__hppa__) \
+ || defined(CONFIG_SPARC) || defined(__ia64__) \
+ || defined(__sh__) || defined(__mips__)
+static int rx_copybreak = 1518;
+#else
static int rx_copybreak;
+#endif
/* Work-around for broken BIOSes: they are unable to get the chip back out of
power state D3 so PXE booting fails. bootparam(7): via-rhine.avoid_D3=1 */
_
next reply other threads:[~2007-08-10 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 21:05 akpm [this message]
2007-08-10 21:33 ` [patch 04/18] via-rhine: disable rx_copybreak on archs that don't allow unaligned DMA access Francois Romieu
2007-08-14 5:27 ` Jeff Garzik
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=200708102105.l7AL5FUp008954@imap1.linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=ink@jurassic$(echo .)park.msu.ru \
--cc=jailbird@alcatraz$(echo .)fdf.net \
--cc=jeff@garzik$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=romieu@fr$(echo .)zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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