From: Wolfgang Grandegger <wg@grandegger.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: SocketCAN Core Mailing List <socketcan-core@lists.berlios.de>,
Willy Lambert <lambert.willy@gmail.com>,
x86@kernel.org, Valdis.Kletnieks@vt.edu,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: permit to configure ISA support also for x86_64 systems
Date: Wed, 21 Sep 2011 10:33:10 +0200 [thread overview]
Message-ID: <4E79A146.2040204@grandegger.com> (raw)
In-Reply-To: <201109201747.50130.arnd@arndb.de>
On 09/20/2011 05:47 PM, Arnd Bergmann wrote:
> On Friday 16 September 2011, Wolfgang Grandegger wrote:
>> On 09/16/2011 09:19 PM, Valdis.Kletnieks@vt.edu wrote:
>>> On Fri, 16 Sep 2011 11:22:45 +0200, Wolfgang Grandegger said:
>>>> There are 64-bit systems out there, like the ATOM N450, which
>>>> have ISA slots.
>>>
>>> That's a scary thought...
>>
>> Well. Actually we need it for Intel Atom N450 PC/104-Plus SBCs.
>
> I would assume that you have a small set of ISA add-on cards that
> you actually need to support, right?
Yes, various PC/104 compatible boards can be connected to the ISA bus on
such systems (via PC/104 connector). I personally do only care about the
CAN devices (as maintainer).
> Since most ISA drivers don't actually use isa_register_driver
> (for good or bad), how about changing the Kconfig entry for
> the ones you need to 'depends on ISA || PLAT_GRANDEGGER_PC104_ATOM'
> or similar?
What should the PLAT_GRANDEGGER_PC104_ATOM be good for? If I replace
isa_register_driver() with platform_driver_register(), like the serial
8250 driver does, HAS_IOMEM should be just fine. This would then also
avoid the 64-bit trouble expected with old ISA drivers (enabled via
ISA). Or have I missed something?
Wolfgang.
next prev parent reply other threads:[~2011-09-21 8:33 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 [this message]
2011-09-21 9:24 ` Arnd Bergmann
2011-09-21 22:13 ` Andi Kleen
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=4E79A146.2040204@grandegger.com \
--to=wg@grandegger.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arnd@arndb.de \
--cc=lambert.willy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=socketcan-core@lists.berlios.de \
--cc=x86@kernel.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.