public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andi Kleen <ak@suse.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>,
	discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: RFC: let x86_64 no longer define X86
Date: Fri, 19 Nov 2004 07:37:33 -0500	[thread overview]
Message-ID: <419DE90D.9030509@pobox.com> (raw)
In-Reply-To: <20041119121909.GF21483@wotan.suse.de>

Andi Kleen wrote:
> On Fri, Nov 19, 2004 at 07:12:46AM -0500, Jeff Garzik wrote:
> 
>>Andi Kleen wrote:
>>
>>>I don't know details about the driver, but it's not enabled on x86-64 
>>>because x86-64 doesn't have ISA set.
>>
>>
>>which I disagree with.  CONFIG_ISA should include southbridge devices 
>>behind a PCI<->ISA bridge.  There is zero value to a more stricter 
>>"there is a physical ISA bus in this machine" definition.
> 
> 
> There is. It gets rid of many tens of drivers that are not and will never
> be 64bit clean and have a snowball in hell chances to work on x86-64.
> 
> In theory you could invent a new ISA_SLOT or ISA_BROKEN config for them,
> but since ISA does the job quite well for near everybody except
> for one or two corner cases I don't see any sense in changing it.

The traditional legacy ISA devices -- floppy, serial, parallel, mouse, 
keyboard, IDE -- are still around.  Yet now we need to invent a new name 
to classify ISA devices that have been with us for 20 years?

CONFIG_ISA_BROKEN is more appropriate than pretending devices we've 
called ISA since the 1980's do not imply/depend on CONFIG_ISA.

	Jeff



  reply	other threads:[~2004-11-19 12:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19  0:51 RFC: let x86_64 no longer define X86 Adrian Bunk
2004-11-19  1:14 ` Nick Piggin
2004-11-19  1:19   ` Adrian Bunk
2004-11-19  1:31 ` [discuss] " Paul Menage
2004-11-19 12:28   ` Adrian Bunk
2004-11-19 12:40     ` Andi Kleen
2004-11-19 13:29       ` Adrian Bunk
2004-11-19  8:51 ` Andi Kleen
2004-11-19 10:21   ` Jeff Garzik
2004-11-19 10:34     ` [discuss] " Andi Kleen
2004-11-19 11:28       ` David Woodhouse
2004-11-19 11:55         ` Andi Kleen
2004-11-19 11:50           ` David Woodhouse
2004-11-19 12:05             ` Andi Kleen
2004-11-19 12:12               ` Jeff Garzik
2004-11-19 12:19                 ` Andi Kleen
2004-11-19 12:37                   ` Jeff Garzik [this message]
2004-11-19 12:45                     ` Adrian Bunk
2004-11-19 12:55                     ` linux-os
2004-11-19 13:04                       ` Jeff Garzik
2004-11-19 13:35                         ` Raul Miller
2004-11-19 14:11                   ` Adrian Bunk
2004-11-19 13:58               ` David Woodhouse
2004-11-19 12:05       ` Adrian Bunk
2004-11-19 12:09         ` Andi Kleen
2004-11-19 11:18 ` Takashi Iwai
2004-11-19 22:31   ` Paul Mackerras

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=419DE90D.9030509@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=discuss@x86-64.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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