From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Keith Owens <kaos@ocs.com.au>,
James.Bottomley@HansenPartnership.com,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.10-pre10
Date: Mon, 17 Sep 2001 00:01:48 -0500 [thread overview]
Message-ID: <200109170501.f8H51mv04975@localhost.localdomain> (raw)
In-Reply-To: Message from Tom Rini <trini@kernel.crashing.org> of "Sun, 16 Sep 2001 21:03:14 PDT." <20010916210314.C14279@cpe-24-221-152-185.az.sprintbbd.net>
trini@kernel.crashing.org said:
> Well, I guess my question is, is this arch-specific or driver
> specific? The lasi700 driver is hppa-only. The NCR_D700 doesn't have
> any restrictions. James?
Well, the original intent was to separate the chip core logic from the actual
board driver. To that end, I needed two cores, one which was io mapped and
one which was mem mapped. In theory, set up the way it is, I can keep
architectural dependencies out of the chip core (53c700.c). The two file
strategy was the only way I could think to do this.
lasi700 is completely parisc specific. NCR_D700 is and x86 microchannel card.
Actually, the way you're suggesting will work with some modifications: All I
have to do in Config.in is require the lasi700 and the NCR_D700 to do a
define_bool CONFIG_53C700_MEM_MAPPED y and define_bool CONFIG_53C700_IO_MAPPED
y respectively when they're selected and insist that one or other of these
flags be present in the core driver before it will compile.
I've got a big sync to do with the work I've been doing on the parisc driver,
so I'll put that in too.
James
next prev parent reply other threads:[~2001-09-17 5:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 22:00 Linux-2.4.10-pre10 Linus Torvalds
2001-09-17 1:15 ` Linux-2.4.10-pre10 Keith Owens
2001-09-17 2:17 ` Linux-2.4.10-pre10 Tom Rini
2001-09-17 2:56 ` Linux-2.4.10-pre10 Keith Owens
2001-09-17 4:03 ` Linux-2.4.10-pre10 Tom Rini
2001-09-17 5:01 ` James Bottomley [this message]
2001-09-17 22:20 ` Linux-2.4.10-pre10 Andreas Steinmetz
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=200109170501.f8H51mv04975@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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).