All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@ee.oulu.fi>
To: Florian Schirmer <jolt@tuxbox.org>
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: b44: add 47xx support
Date: Mon, 26 Jul 2004 17:11:28 +0300	[thread overview]
Message-ID: <20040726141128.GA5435@ee.oulu.fi> (raw)
In-Reply-To: <200407232335.37809.jolt@tuxbox.org>

On Fri, Jul 23, 2004 at 11:35:30PM +0200, Florian Schirmer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> this patch adds support for the BCM47xx device to the b44 driver. Please 
> apply.
> 
> BTW what happened to the 1GB DMA fix? The SiliconBackplane cores _are_ limited 
> to a 1GB DMA window so we need to take that into account. Any reason why 
> those patches where dropped?
Hiya

Looks good (well, won't be able to test that it doesn't break 4401 until
next week :-) ).

As for the 1GB patch going in, I sure hope they would (perhaps in a cleaned
up state, it might be more pretty if I just unconditionally enabled the
workaround and had a b44_alloc_skb() that tries a normal dev_alloc_skb and if
that gives something over 1GB retry with GFP_DMA...

A situation where it breaks even without 4g4g would help in getting the
patch in :-)

 

  reply	other threads:[~2004-07-26 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 21:35 b44: add 47xx support Florian Schirmer
2004-07-26 14:11 ` Pekka Pietikainen [this message]
2004-08-04  0:31   ` [PATCH] b44 1GB DMA workaround (was: b44: add 47xx support) Pekka Pietikainen
2004-08-04  1:39     ` David S. Miller
2004-08-07 22:40       ` Pekka Pietikainen
2004-08-08  0:05         ` David S. Miller
2004-08-08  9:31           ` [PATCH] b44 1GB DMA workaround Pekka Pietikainen

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=20040726141128.GA5435@ee.oulu.fi \
    --to=pp@ee.oulu.fi \
    --cc=jgarzik@pobox.com \
    --cc=jolt@tuxbox.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.