linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	gregkh@linuxfoundation.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig option
Date: Wed, 13 Apr 2016 16:38:38 +0200	[thread overview]
Message-ID: <20160413143838.GD5867@gmail.com> (raw)
In-Reply-To: <20160413121515.GA23870@sophia>


* William Breathitt Gray <vilhelm.gray@gmail.com> wrote:

> On Wed, Apr 13, 2016 at 09:26:02AM +0200, Ingo Molnar wrote:
> >What's the practical motivation of this? What exact hardware is this for?
> >
> >Thanks,
> >
> >	Ingo
> 
> The PC/104 bus is equivalent to the ISA bus regarding software
> communication. Many small form factor systems have a PC/104 bus where
> PC/104 cards may be stacked. Nowadays, these systems are commonly
> running 64-bit processors such as the Intel Atom.
> 
> I would like to utilize the ISA bus driver to support these PC/104
> devices (see http://lkml.org/lkml/2016/4/7/418), but the ISA
> configuration option has an arbitrary X86_32 dependency. Decoupling the
> X86_32 dependency from the ISA configuration option will allow these
> PC/104 drivers to build for 64-bit architectures.
> 
> The existing kernel drivers which I intend to utilize the ISA bus driver
> in a X86_64 architecture for PC/104 support are the ACCES 104-DIO-48E
> GPIO driver, the ACCES 104-IDI-48 GPIO driver, the ACCES 104-IDIO-16
> GPIO driver, and the Apex Embedded Systems STX104 DAC driver. I have
> several more PC/104 devices for which I wish to write drivers, but I
> would like to resolve this ISA bus driver situation before submitting
> new code.

Ah, ok, so it's for enabling real hardware, not just a cleanup, right? You might 
want to put that info into the boilerplate mail or so.

I'm perfectly fine with all the patches that touch x86 code:

  Acked-by: Ingo Molnar <mingo@kernel.org>

I suppose you'd like to have these in the driver tree, all in one place?

Thanks,

	Ingo

  reply	other threads:[~2016-04-13 14:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 13:25 [PATCH 0/4] Decouple X86_32 dependency from the ISA Kconfig option William Breathitt Gray
2016-04-11 13:25 ` [PATCH 1/4] pnp: pnpbios: Add explicit X86_32 dependency to PNPBIOS William Breathitt Gray
2016-04-22 23:51   ` Rafael J. Wysocki
2016-04-23 14:53     ` William Breathitt Gray
2016-05-01 15:52     ` William Breathitt Gray
2016-04-11 13:25 ` [PATCH 2/4] sound: isa: sscape: Use correct format identifier for size_t William Breathitt Gray
2016-04-11 13:54   ` [alsa-devel] " Takashi Iwai
2016-04-11 13:25 ` [PATCH 3/4] scsi: ultrastor: Use correct format identifier for kernel pointer William Breathitt Gray
2016-04-11 13:25 ` [PATCH 4/4] isa: Remove the ISA_BUS Kconfig option William Breathitt Gray
2016-04-13  7:26 ` [PATCH 0/4] Decouple X86_32 dependency from the ISA " Ingo Molnar
2016-04-13 12:15   ` William Breathitt Gray
2016-04-13 14:38     ` Ingo Molnar [this message]
2016-04-13 14:48       ` William Breathitt Gray
2016-04-13 15:18         ` Greg KH
2016-05-01 16:17           ` William Breathitt Gray
2016-05-01 21:25             ` 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=20160413143838.GD5867@gmail.com \
    --to=mingo@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=vilhelm.gray@gmail.com \
    --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 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).