From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: PATCH & call for help: Marking ISA only drivers
Date: Fri, 10 May 2002 06:45:56 +0200 [thread overview]
Message-ID: <3CDB5084.5000803@evision-ventures.com> (raw)
In-Reply-To: <E175y7e-0004rI-00@the-village.bc.nu>
Uz.ytkownik Alan Cox napisa?:
>>Ok, I'm assuming that there are no boxes with no ISA slots but VLB slots.
>>I guess that's safe. If someone really has a weird box were that is not true
>>I guess they'll have to live with defining CONFIG_ISA.
>>In theory one could introduce an CONFIG_VLB, but I don't think it is
>>worth it.
>
>
> Agreed
In esp. in face of the fact that VLB was in reality merely the
486 CPU to memmory bus hanging out of the system... so it didn't
have it's own protocol different from inb outb - which logically corresponds
to ISA.
next prev parent reply other threads:[~2002-05-10 5:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 18:37 PATCH & call for help: Marking ISA only drivers Andi Kleen
2002-05-09 18:47 ` William Stearns
2002-05-09 20:08 ` CML2 [was Re: PATCH & call for help: Marking ISA only drivers] Tomas Szepe
2002-05-09 20:22 ` Dave Jones
2002-05-09 20:23 ` Alexander Viro
2002-05-09 20:31 ` Tomas Szepe
2002-05-09 20:49 ` toon
2002-05-10 8:30 ` Sean Hunter
2002-05-10 23:56 ` Andrew Rodland
2002-05-10 2:37 ` jeff millar
2002-05-09 19:51 ` PATCH & call for help: Marking ISA only drivers Martin Dalecki
2002-05-09 22:46 ` Andi Kleen
2002-05-09 20:33 ` Alan Cox
2002-05-09 22:50 ` Andi Kleen
2002-05-09 23:18 ` Alan Cox
2002-05-09 23:11 ` Andi Kleen
2002-05-10 0:18 ` Alan Cox
2002-05-10 4:45 ` Martin Dalecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 3:59 Peter Samuelson
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=3CDB5084.5000803@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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