netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] skge: limit DMA to 32 bit
Date: Wed, 22 Sep 2010 09:34:01 +0200	[thread overview]
Message-ID: <20100922073400.GA9942@redhat.com> (raw)
In-Reply-To: <20100921080253.3d89d60a@nehalam>

On Tue, Sep 21, 2010 at 08:02:53AM -0700, Stephen Hemminger wrote:
> > Is 32bit DMA limit for every skge device acceptable patch?
> 
> No. The device does support 64 bit DMA, the problem is a crap implementation
> of the device the motherboard. Therefore a PCI quirk or module parameter
> is a better solution.

Ok, I will use dmi_check_system() to recognize broken board and limit DMA
address space when detected.

Thanks
Stanislaw

      reply	other threads:[~2010-09-22  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21  7:15 [RFC] skge: limit DMA to 32 bit Stanislaw Gruszka
2010-09-21 15:02 ` Stephen Hemminger
2010-09-22  7:34   ` Stanislaw Gruszka [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=20100922073400.GA9942@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).