From: "John W. Linville" <linville@tuxdriver.com>
To: Andrew Morton <akpm@osdl.org>
Cc: hch@infradead.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [patch 2.6.13 2/2] 3c59x: add option for using memory-mapped PCI I/O resources
Date: Tue, 6 Sep 2005 18:57:46 -0400 [thread overview]
Message-ID: <20050906225744.GB26003@tuxdriver.com> (raw)
In-Reply-To: <20050906151546.4d5ed4db.akpm@osdl.org>
On Tue, Sep 06, 2005 at 03:15:46PM -0700, Andrew Morton wrote:
> "John W. Linville" <linville@tuxdriver.com> wrote:
> >
> > I fully intend to have have a flag in the private data set based on
> > the PCI ID when I accumulate some data on which devices support this
> > and which don't. So far I've only got a short list... Do you think
> > such a flag should be based on which ones work, or which ones break?
>
> The ones which are known to work.
>
> Bear in mind that this is an old, messy and relatively stable driver which
> handles a huge number of different NICs. Caution is the rule here.
I definitely agree. That is another part of why I defaulted to "use_mmio=0".
I'll post PCI ID based patches as I determine supported cards.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-09-06 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 20:41 [patch 2.6.13 1/2] 3c59x: convert to use of pci_iomap API John W. Linville
2005-09-06 20:44 ` [patch 2.6.13 2/2] 3c59x: add option for using memory-mapped PCI I/O resources John W. Linville
2005-09-06 20:54 ` Christoph Hellwig
2005-09-06 21:04 ` Andrew Morton
[not found] ` <20050906220922.GA26003@tuxdriver.com>
2005-09-06 22:15 ` Andrew Morton
2005-09-06 22:57 ` John W. Linville [this message]
2005-09-06 23:13 ` Andrew Morton
2005-09-12 14:48 ` [patch 2.6.13] 3c59x: enable use of memory-mapped PCI I/O John W. Linville
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=20050906225744.GB26003@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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).