All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	Anton Blanchard <anton@samba.org>
Subject: Re: [RFC/PATCH] powerpc: Rewrite IO allocation & mapping on powerpc64
Date: Tue, 15 May 2007 01:39:41 +0200	[thread overview]
Message-ID: <200705150139.41722.arnd@arndb.de> (raw)
In-Reply-To: <1179176381.32247.98.camel@localhost.localdomain>

On Monday 14 May 2007, Benjamin Herrenschmidt wrote:
> > Can we make this depend on CONFIG_ISA? Most platforms don't actually want
> > to build in ISA support.
> 
> I'm not too sure about that. CONFIG_ISA means you have legacy devices or
> ISA slots ? or both ?
> 

Good point, it means ISA slots, so it's probably not the right option here:

config ISA
        bool "Support for ISA-bus hardware"
        depends on PPC_PREP || PPC_CHRP
        select PPC_I8259
	help
	  Find out whether you have ISA slots on your motherboard.  ISA is the
	  name of a bus system, i.e. the way the CPU talks to the other stuff
	  inside your box.  If you have an Apple machine, say N here; if you
	  have an IBM RS/6000 or pSeries machine or a PReP machine, say Y.  If
	  you have an embedded board, consult your board documentation.

(side note: funny how it recommends to say Y for pSeries, but doesn't allow it ;-).

Maybe we should instead build the new file depending on a new option and make
the Kconfig read as

config ISA
	def_bool y
	depends on PPC_PREP || PPC_CHRP
	select PPC_I8259
	select LEGACY_IOPORT
	help
	  This option is for actual ISA slots

config LEGACY_IOPORT
	bool
	# maybe convert some of these into select statements
	default y if PPC_UDBG_16550
	default y if SERIO_I8042  || PPC_I8259 || PARPORT_PC 
	default y if MAPLE || MPC8641_HPCN
	default y if BLK_DEV_FD || PATA_LEGACY || IDE
	default y if VGA_CONSOLE || FB
	help
          This option enables the use of hardcoded PIO port numbers
	  in device drivers.

An interesting case is the frame buffer, most fb drivers use hardcoded
register numbers for the VGA ports, without calling check_legacy_ioport,
but rely on PCI probing to detect the presence of the device.
Some IDE drivers do the same, but libata does not. Apparently, these
are already broken if you plug such hardware into a secondary PCI bus.

	Arnd <><

  reply	other threads:[~2007-05-14 23:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  7:53 [RFC/PATCH] powerpc: Rewrite IO allocation & mapping on powerpc64 Benjamin Herrenschmidt
2007-05-14  7:59 ` Benjamin Herrenschmidt
2007-05-14  8:03 ` Benjamin Herrenschmidt
2007-05-14  9:18 ` Benjamin Herrenschmidt
2007-05-14 13:50 ` Segher Boessenkool
2007-05-14 20:53   ` Benjamin Herrenschmidt
2007-05-15  0:17   ` Paul Mackerras
2007-05-15  4:33     ` Segher Boessenkool
2007-05-15  6:04       ` Benjamin Herrenschmidt
2007-05-14 14:37 ` Arnd Bergmann
2007-05-14 15:04   ` Segher Boessenkool
2007-05-14 23:56     ` Arnd Bergmann
2007-05-15  0:05       ` Olof Johansson
2007-05-14 20:59   ` Benjamin Herrenschmidt
2007-05-14 23:39     ` Arnd Bergmann [this message]
2007-05-15  0:06       ` Benjamin Herrenschmidt
2007-05-15 10:56 ` Christoph Hellwig
2007-05-15 20:42   ` 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=200705150139.41722.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 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.