From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: subrata@linux.vnet.ibm.com
Cc: Sachin P Sant <sachinp@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
netdev@vger.kernel.org,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
Linux-Next <linux-next@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH][BUILD FAILURE 03/04] Next June 04:PPC64 randconfig [drivers/net/lance.o]
Date: Mon, 15 Jun 2009 19:43:01 +1000 [thread overview]
Message-ID: <1245058981.12400.3.camel@pasglop> (raw)
In-Reply-To: <1245050509.5239.11.camel@subratamodak.linux.ibm.com>
On Mon, 2009-06-15 at 12:51 +0530, Subrata Modak wrote:
> On Mon, 2009-06-15 at 17:11 +1000, Benjamin Herrenschmidt wrote:
> > On Mon, 2009-06-15 at 12:21 +0530, Subrata Modak wrote:
> >
> > > Benjamin,
> > >
> > > I am not sure whether you liked the following patch to solve the above
> > > problem. Do, you want me address some other issue(s)/fixes for this ?
> >
> > I suppose ... in fact some old PReP machines can even have ISA slots
> > iirc, but it's not going to do good with machines that have an iommu...
> >
> > IE. Nobody should use that crap, period.
>
> Great,
>
> Can you please make some changes at drivers/net/Kconfig so that this guy
> does not build for the PPC64 systems ?
When I said "that crap" I was talking about those interfaces which I
-hope- are deprecated :-)
I suspect we never really sorted out the issue of DMA mapping for old
legacy ISA stuff... pci_map_* should work to some extent, though you
have to pass it the ISA bridge pci_dev.
Maybe it's time for somebody to start exposing a -proper- abstraction
accross all platforms for that :-)
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: subrata@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
Sachin P Sant <sachinp@linux.vnet.ibm.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Linux-Next <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH][BUILD FAILURE 03/04] Next June 04:PPC64 randconfig [drivers/net/lance.o]
Date: Mon, 15 Jun 2009 19:43:01 +1000 [thread overview]
Message-ID: <1245058981.12400.3.camel@pasglop> (raw)
In-Reply-To: <1245050509.5239.11.camel@subratamodak.linux.ibm.com>
On Mon, 2009-06-15 at 12:51 +0530, Subrata Modak wrote:
> On Mon, 2009-06-15 at 17:11 +1000, Benjamin Herrenschmidt wrote:
> > On Mon, 2009-06-15 at 12:21 +0530, Subrata Modak wrote:
> >
> > > Benjamin,
> > >
> > > I am not sure whether you liked the following patch to solve the above
> > > problem. Do, you want me address some other issue(s)/fixes for this ?
> >
> > I suppose ... in fact some old PReP machines can even have ISA slots
> > iirc, but it's not going to do good with machines that have an iommu...
> >
> > IE. Nobody should use that crap, period.
>
> Great,
>
> Can you please make some changes at drivers/net/Kconfig so that this guy
> does not build for the PPC64 systems ?
When I said "that crap" I was talking about those interfaces which I
-hope- are deprecated :-)
I suspect we never really sorted out the issue of DMA mapping for old
legacy ISA stuff... pci_map_* should work to some extent, though you
have to pass it the ISA bridge pci_dev.
Maybe it's time for somebody to start exposing a -proper- abstraction
accross all platforms for that :-)
Ben.
next prev parent reply other threads:[~2009-06-15 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 3:50 [PATCH][BUILD FAILURE 03/04] Next June 04:PPC64 randconfig [drivers/net/lance.o] Subrata Modak
2009-06-11 3:50 ` Subrata Modak
2009-06-15 6:51 ` Subrata Modak
2009-06-15 6:51 ` Subrata Modak
2009-06-15 7:11 ` Benjamin Herrenschmidt
2009-06-15 7:11 ` Benjamin Herrenschmidt
2009-06-15 7:21 ` Subrata Modak
2009-06-15 7:21 ` Subrata Modak
2009-06-15 9:43 ` Benjamin Herrenschmidt [this message]
2009-06-15 9:43 ` Benjamin Herrenschmidt
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=1245058981.12400.3.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=subrata@linux.vnet.ibm.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.