From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Olaf Hering <olaf@aepfle.de>
Subject: Re: [PATCH] generic check_legacy_ioport
Date: Wed, 18 Apr 2007 01:28:18 +0200 [thread overview]
Message-ID: <17b634b08cf34bfd093dda9fe2e18d14@kernel.crashing.org> (raw)
In-Reply-To: <200704172322.23362.arnd@arndb.de>
> I could be wrong, but I think I've seen fake 'isa' bus nodes in the
> device tree
> for machines that don't actually have isa. I probably saw this on very
> early
> cell blades (not the ones currently shipping), but perhaps others have
> made the same mistake.
JS2x SLOF pretends the LPC bus is ISA (although the two
are not completely compatible!) because otherwise
Linux wouldn't find the serial ports. I suppose I could
have fixed the Linux code instead but it was hard enough
to understand already, and really hard to change (since
that would require testing on all previously supported
platforms).
> How about simply defining a new common function like
>
> int generic_deny_legacy_ioport(unsigned long base_port)
> {
> return -EINVAL;
> }
>
> so that not every platform has to define their own but can either
> set ppc_md.check_legacy_ioport to NULL, to generic_deny_legacy_ioport
> or their own function if they do something fancy?
I'd rather deny everything legacy x86 by default, and
only allow a few ranges on the few platforms that really
want that.
Segher
next prev parent reply other threads:[~2007-04-17 23:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 21:07 [PATCH] generic check_legacy_ioport Olaf Hering
2007-04-17 21:22 ` Arnd Bergmann
2007-04-17 23:28 ` Segher Boessenkool [this message]
2007-04-20 18:51 ` Olaf Hering
2007-04-22 5:15 ` Milton Miller
2007-04-22 6:46 ` Olaf Hering
2007-04-23 8:15 ` [PATCH] " Olaf Hering
2007-04-24 0:53 ` Benjamin Herrenschmidt
2007-04-24 11:25 ` Olaf Hering
2007-04-24 15:45 ` Milton Miller
2007-04-24 18:54 ` Olaf Hering
2007-04-24 22:01 ` Arnd Bergmann
2007-04-25 0:12 ` Benjamin Herrenschmidt
2007-04-25 1:54 ` Segher Boessenkool
2007-04-25 7:49 ` Arnd Bergmann
2007-04-25 13:33 ` Segher Boessenkool
2007-04-25 22:02 ` Arnd Bergmann
2007-04-25 0:09 ` Benjamin Herrenschmidt
2007-04-24 22:34 ` Benjamin Herrenschmidt
2007-04-25 20:36 ` Olaf Hering
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=17b634b08cf34bfd093dda9fe2e18d14@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=olaf@aepfle.de \
/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).