netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: "� Engel" <joern@dublin.logfs.org>
Cc: David Miller <davem@davemloft.net>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, romieu@fr.zoreil.com
Subject: Re: [Regression] r8169: enable 64-bit DMA by default for PCI Express devices (v2)
Date: Sat, 27 Mar 2010 11:46:12 -0600	[thread overview]
Message-ID: <4BAE4464.9060909@gmail.com> (raw)
In-Reply-To: <20100327063838.GB11959@Dublin.logfs.org>

On 03/27/2010 12:38 AM, � Engel wrote:
> On Fri, 26 March 2010 19:55:44 -0600, Robert Hancock wrote:
>>
>> Well, that one's 36 bits, but it's unclear whether that driver would
>> actually be likely to access anything over 4GB. It's possible that
>> there's just some general problem with 64-bit DMA on that machine.
>
> That may very well be.  I've had trouble using a PCIe card in that
> machine as well.  "Solution" was to buy a different computer.  Sad, I
> know, but not my money.

Hm, do you recall/have the details of what happened with the other card?

It's possible this is some general problem with that machine/motherboard 
and not actually an issue with what the driver is doing. What kind of 
board is that?

>
>> The fact that even stuff like lspci and MII is breaking seems odd,
>> though. It could be that model of card doesn't like the PCIDAC register
>> bit being set (maybe it means something different on that model, or
>> something).
>>
>> I suppose a publicly accessible datasheet for these chips is too much to
>> hope for?
>
> Which chips?
>
> J�rn
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2010-03-27 17:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100315150806.GA15354@Dublin.logfs.org>
     [not found] ` <20100315151041.GA15667@Dublin.logfs.org>
2010-03-15 18:57   ` [Regression] r8169: enable 64-bit DMA by default for PCI Express devices (v2) David Miller
2010-03-15 23:28     ` Robert Hancock
2010-03-16  8:35       ` J�rn Engel
2010-03-16 23:30         ` Robert Hancock
2010-03-16 23:40           ` David Miller
2010-03-26  0:56           ` Robert Hancock
2010-03-26  3:29             ` David Miller
2010-03-26  9:12             ` J�rn Engel
2010-03-27  1:55               ` Robert Hancock
2010-03-27  6:38                 ` J�rn Engel
2010-03-27 17:46                   ` Robert Hancock [this message]
2010-03-27 22:00                     ` J�rn Engel
2010-03-27 11:57                 ` =?unknown-8bit?B?RnJhbsOnb2lz?= Romieu
2010-03-17 20:52         ` Francois Romieu
2010-03-18  9:03           ` J�rn Engel

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=4BAE4464.9060909@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=davem@davemloft.net \
    --cc=joern@dublin.logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=torvalds@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).