Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: mips config.in patch 1 of N - Check for completeness
Date: Mon, 3 Apr 2000 10:39:44 +0200	[thread overview]
Message-ID: <20000403103944.A278@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10004031028110.22512-100000@dandelion.sonytel.be>; from Geert Uytterhoeven on Mon, Apr 03, 2000 at 10:29:31AM +0200

On Mon, Apr 03, 2000 at 10:29:31AM +0200, Geert Uytterhoeven wrote:
> On Sun, 2 Apr 2000, Florian Lohoff wrote:
> > +	#Architectures possibly having pcmcia should include this
> > +        #source drivers/pcmcia/Config.in
> 
> i.e. CONFIG_PCI || CONFIG_ISA

I didnt want to do that because i dont think anyone has seen
a RM200C with PCMCIA ? So i thought architectures explecitely 
having a PCMCIA (Like probably the Handhelds like Aero, Cassiopaia etc)
would enable it with "CONFIG_AERO" or something.

> > +	#Architectures having PC Style Parports - please include
> > +        #source drivers/parport/Config.in
> 
> i.e. CONFIG_ISA
> 
> Note that here are also non-PC style parport drivers (e.g. for Amiga), but for
> MIPS I think the PC-style parports are the only ones that matter.

Are they represented in the above config ? ...

Flo
-- 
Florian Lohoff		flo@rfc822.org		      	+49-5241-470566
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."

  reply	other threads:[~2000-04-03  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-02  7:24 mips config.in patch 1 of N - Check for completeness Florian Lohoff
2000-04-03  8:29 ` Geert Uytterhoeven
2000-04-03  8:39   ` Florian Lohoff [this message]
2000-04-03  9:09     ` Geert Uytterhoeven

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=20000403103944.A278@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=linux@cthulhu.engr.sgi.com \
    /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