public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ISA stubs for ia64
Date: Wed, 07 Apr 2004 17:42:13 +0000	[thread overview]
Message-ID: <16500.15733.693223.140954@napali.hpl.hp.com> (raw)
In-Reply-To: <200404061630.20264.bjorn.helgaas@hp.com>

>>>>> On Wed, 7 Apr 2004 09:09:12 -0600, Bjorn Helgaas <bjorn.helgaas@hp.com> said:

  Bjorn> On Tuesday 06 April 2004 5:18 pm, David Mosberger wrote:
  >> I don't like this patch at all.  The #defines to
  >> unsupported_isa_dma_interface() turn compile-time errors into
  >> potential runtime errors.  With a properly abstracted interface, the
  >> ISA-compatibility-macros should not lead to any code in ISA-free
  >> systems (and hence there would be no possibility of runtime errors).

  Bjorn> True.  I actually started by modifying drivers to use CONFIG_ISA to
  Bjorn> determine whether to use ISA interfaces, but (a) that leads to a lot
  Bjorn> of changes, most of which I can't test and have the potential to break
  Bjorn> other arches, and (b) somebody suggested that ISA is sort of a special
  Bjorn> case because it hasn't been converted to the driver model.

  Bjorn> But I certainly agree that it would be a lot cleaner.

If it's not possible to define ISA-compatibility macros that expand
into no runtime code, I don't see an easy solution.  Perhaps we could
at least provide macros such that a driver _can_ be converted to such
a model.  It will still require fixing some/many/most drivers with
ISA-support, but to get allmodonf to work, we could just disable a
driver altogether if it depends on ISA and the platform doesn't
support ISA.  The cleanup/conversion can then be done incrementally,
as the need arises.

	--david

      parent reply	other threads:[~2004-04-07 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06 22:30 [PATCH] ISA stubs for ia64 Bjorn Helgaas
2004-04-06 23:18 ` David Mosberger
2004-04-07 15:09 ` Bjorn Helgaas
2004-04-07 17:42 ` David Mosberger [this message]

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=16500.15733.693223.140954@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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