From: Ian Molton <spyro@armlinux.org>
To: Guest section DW <dwguest@win.tue.nl>
Cc: aia21@cam.ac.uk, aia21@cus.cam.ac.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix floppy io ports reservation
Date: Fri, 8 Feb 2002 18:50:31 +0000 [thread overview]
Message-ID: <20020208185031.0a9c464f.spyro@armlinux.org> (raw)
In-Reply-To: <20020208152348.GA1809@win.tue.nl>
In-Reply-To: <E16Yevs-00054g-00@libra.cus.cam.ac.uk> <E16Yevs-00054g-00@libra.cus.cam.ac.uk> <5.1.0.14.2.20020207231937.00b0cec0@pop.cus.cam.ac.uk> <20020208152348.GA1809@win.tue.nl>
On a sunny Fri, 8 Feb 2002 16:23:48 +0100 Guest section DW gathered a sheaf
of electrons and etched in their motions the following immortal words:
> >> ports 0x3f0 and 0x3f1 are used on certain PS/2 systems
> >> and on some very old AT clones
> >
> > [PS/2] Can you point me to the code for the PS/2 systems in question?
> > [AT] And we care because?
>
> You need not worry - these systems have been dead for over fifteen years.
I dont like that attitude. I have a system that has been 'dead' for a while
(its now 15 years old), and I'm 're'-porting linux to it (Acorn A400).
Linux is meant to be fun, not just 'latest X86 crap'.
Not to say that we should restrict anything for old hardware, but it doesnt
hurt to spare a thought for it. Doing so may even encourage people to write
better code.
next prev parent reply other threads:[~2002-02-08 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 3:09 Anton Altaparmakov
2002-02-07 20:24 ` Guest section DW
2002-02-07 21:54 ` Alan Cox
2002-02-08 0:16 ` Anton Altaparmakov
2002-02-08 0:04 ` Anton Altaparmakov
2002-02-08 15:23 ` Guest section DW
2002-02-08 18:50 ` Ian Molton [this message]
2002-02-08 0:25 Thomas Hood
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=20020208185031.0a9c464f.spyro@armlinux.org \
--to=spyro@armlinux.org \
--cc=aia21@cam.ac.uk \
--cc=aia21@cus.cam.ac.uk \
--cc=dwguest@win.tue.nl \
--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
all inboxes | Powered by JetHome®