public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [BUG] base: isa: ISA bus functionality not compiled for X86_64 architecture
Date: Wed, 20 Jan 2016 09:00:03 -0500	[thread overview]
Message-ID: <20160120140003.GA19600@sophia> (raw)

Hello,

I'm developing drivers for devices accessible over a PC/104 bus (a bus
specification derived from ISA). Up until now I've used the
platform_driver structure in my drivers, but I believe it would be more
appropriate to use the isa_driver structure located in the
include/linux/isa.h file.

I discovered that the relevant ISA bus functions located in the
drivers/base/isa.c file are conditionally compiled based on the
CONFIG_ISA option declared in the arch/x86/Kconfig file. Unfortunately,
the CONFIG_ISA option can only be set to Y if the CONFIG_X86_32 option
is set to Y; I'm running a 64-bit X86 processor, so I naturally have
CONFIG_X86_32 set to N.

Would it be proper to remove the CONFIG_X86_32 dependency from the
CONFIG_ISA option? Motherboards with the PC/104 bus are effectively
motherboards with the ISA bus. Alternatively, I can submit a respective
pc104.c and pc104.h patch to implement a PC/104 bus driver, but it would
essentially be a virtually vertabim copy of the ISA bus implementation
(e.g. s/isa/pc104/g).

What are your thoughts?

Sincerely,

William Breathitt Gray

             reply	other threads:[~2016-01-20 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 14:00 William Breathitt Gray [this message]
2016-01-20 23:09 ` [BUG] base: isa: ISA bus functionality not compiled for X86_64 architecture Greg KH

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=20160120140003.GA19600@sophia \
    --to=vilhelm.gray@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox