linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ben Collins <bcollins@debian.org>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
	linux1394-devel@lists.sourceforge.net
Subject: Re: PCILynx driver on big-endian
Date: Tue, 20 Jul 2004 13:43:08 +0200	[thread overview]
Message-ID: <20040720114308.GA20521@suse.de> (raw)
In-Reply-To: <Pine.GSO.4.58.0407201327150.20387@waterleaf.sonytel.be>


 On Tue, Jul 20, Geert Uytterhoeven wrote:

> On Tue, 20 Jul 2004, Olaf Hering wrote:
> > Did the pcilynx driver ever work on ppc?
> > The B&W G3 Macs have an onboard Opti chip, I doubt it ever worked.
> >
> > Its better to hide it.
> >
> >
> > Index: Kconfig
> > ===================================================================
> > --- Kconfig	(revision 1233)
> > +++ Kconfig	(working copy)
> > @@ -72,7 +72,7 @@
> >
> >  config IEEE1394_PCILYNX
> >  	tristate "Texas Instruments PCILynx support"
> > -	depends on PCI && IEEE1394 && I2C
> > +	depends on PCI && IEEE1394 && I2C && !PPC_PMAC
>
> Or to better show there's a problem: ... && (!PPC_PMAC || BROKEN)

That will hide it everywhere? && (0 || 1)

--
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-07-20 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040305235832.GA1082@phunnypharm.org>
     [not found] ` <20040306144215.GA23771@suse.de>
     [not found]   ` <20040306171629.GC1082@phunnypharm.org>
2004-07-20 10:47     ` PCILynx driver on big-endian Olaf Hering
2004-07-20 11:28       ` Geert Uytterhoeven
2004-07-20 11:43         ` Olaf Hering [this message]
2004-07-20 13:08           ` Geert Uytterhoeven

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=20040720114308.GA20521@suse.de \
    --to=olh@suse.de \
    --cc=bcollins@debian.org \
    --cc=geert@linux-m68k.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@lists.linuxppc.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).