From: Andi Kleen <andi@firstfloor.org>
To: Arnd Bergmann <public-arnd-r2nGTMty4D4@plane.gmane.org>
Cc: Wolfgang Grandegger
<public-wg-5Yr1BZd7O62+XT7JhA+gdA@plane.gmane.org>,
SocketCAN Core Mailing List
<public-socketcan-core-0fE9KPoRgkgATYTw5x5z8w@plane.gmane.org>,
Willy Lambert
<public-lambert.willy-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org>,
public-x86-DgEjT+Ai2ygdnm+yROfE0A@plane.gmane.org,
public-Valdis.Kletnieks-PjAqaU27lzQ@plane.gmane.org,
LKML <public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org>
Subject: Re: [PATCH] x86_64: permit to configure ISA support also for x86_64 systems
Date: Wed, 21 Sep 2011 15:13:42 -0700 [thread overview]
Message-ID: <m239fpee7d.fsf@firstfloor.org> (raw)
In-Reply-To: <11382509.BgAkVknI9a@wuerfel> (Arnd Bergmann's message of "Wed, 21 Sep 2011 11:24:44 +0200")
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org> writes:
>
> The other point is that you are probably using inb/outb operations,
> which I'm trying to provide only on ISA/PCMCIA/PCI based systems in
> the future. Once I finish that work, you will also need to depend on
> HAS_IOPORT (which currently means something else).
What does that mean? Most PCs need at least some ioport usage
during boot.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2011-09-21 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 9:22 [PATCH] x86_64: permit to configure ISA support also for x86_64 systems Wolfgang Grandegger
2011-09-16 19:19 ` Valdis.Kletnieks
2011-09-16 19:31 ` Wolfgang Grandegger
2011-09-20 15:47 ` Arnd Bergmann
2011-09-21 8:33 ` Wolfgang Grandegger
2011-09-21 9:24 ` Arnd Bergmann
2011-09-21 22:13 ` Andi Kleen [this message]
2011-09-22 6:43 ` Wolfgang Grandegger
2011-09-22 14:20 ` Arnd Bergmann
2011-09-22 14:57 ` Wolfgang Grandegger
2011-09-18 23:19 ` Calvin Walton
2011-09-16 22:33 ` Andi Kleen
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=m239fpee7d.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=public-Valdis.Kletnieks-PjAqaU27lzQ@plane.gmane.org \
--cc=public-arnd-r2nGTMty4D4@plane.gmane.org \
--cc=public-lambert.willy-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org \
--cc=public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org \
--cc=public-socketcan-core-0fE9KPoRgkgATYTw5x5z8w@plane.gmane.org \
--cc=public-wg-5Yr1BZd7O62+XT7JhA+gdA@plane.gmane.org \
--cc=public-x86-DgEjT+Ai2ygdnm+yROfE0A@plane.gmane.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.