--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 06, 2004 at 04:19:47PM -0500, Gary Thorpe wrote:
>  --- Jason Thorpe <thorpej@wasabisystems.com> wrote: >=20
> > On Feb 6, 2004, at 10:34 AM, Gary Thorpe wrote:
> >=20
> > I don't quite understand what you're getting at.... alpha, mips,=20
> > powerpc, etc. systems already use "pckbc" and "pcppi".  What's wrong=20
> > with "pcppc"?
> >=20
> > The fact is, they *ARE* "PC-style" devices, and these other non-PC=20
> > platforms specifically chose the PC-class hardware because it's cheap
> >=20
> > and available.
>=20
> And in the spirit of true pedantism, I should point out that pckbc
> supports PS/2 mice (pms device). From the man page:
> "The pckbc driver handles resource allocation and device attachment for
>  the traditional PC/AT keyboard controller." [so there is some
> reference to AT].

Gary, why are you fighting this fight?

A lot of people said, "pcppc makes more sense." I think it's because they=
=20
think if the hardware as "PCs". Not "PS/2s" nor "PC/ATs". "PCs".

> But the PS/2 mouse appeared in...the IBM PS/2, not the IBM PC.
> Therefore, pms should be at least pcpms or preferrably ps2pms (or maybe
> ibmpms would sound more informative).
>=20
> The manual page for pckbd also indicates support for a PC/AT keyboard,
> so maybe it should be pc_atkbd? What about PS/2 keyboards: shouldn't
> they be ps2kbd? Can you tell the difference in a device probe anyway?
>=20
> Doesn't all of this sound enitrely useless and unhelpful? Does it make
> things magically clearer for PC/AT hardware? That's my point. I would
> agree that the rename may make sense in terms of what everything else
> is named pc*. [Why isn't com called pccom, atcom, or ps2com or why
> bother with com at all since that is MS-DOS's serial port? Hope this
> underscores my point some more.]

Actually, it completely muddles your point. Sorry.

Take care,

Bill

--n8g4imXOkfNTN/H1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAJamaWz+3JHUci9cRAj8kAJwMNr691O5muvmwSZ64va+TkOChmACghltH
q4Rb9xEFuLAYi9WXQuWQxt4=
=6Tj0
-----END PGP SIGNATURE-----

--n8g4imXOkfNTN/H1--