From: David Lawyer <dave@lafn.org>
To: linux-serial@vger.kernel.org
Subject: Re: PnP Rage.
Date: Sun, 23 Feb 2003 20:24:21 -0800 [thread overview]
Message-ID: <20030224042421.GB417@lafn.org> (raw)
In-Reply-To: <20030223104525.A206@lnx2.w8mch.ampr.org>
On Sun, Feb 23, 2003 at 10:45:25AM -0500, Hal MacArgle wrote:
> Greetings: Does anyone care that I LONG for the good old days of
> hardware with jumpers and silk screened instructions?
>
> The "someone" who came up with PnP, eliminating ALL the problems we
> had with port addresses and IRQ's has done a number on us judging
> from the bazillion messages asking for help.. It seems to me the help
> messages before paled to what we have now, not to mention all the
> tools designed to help with the help.. Ugh.
PnP enables the user not to worry about setting jumpers, etc. provided
of course that the various drivers are able to recognize the myriad of
PnP devices and PnP configure them. For MS Windows the device
manufacturer provide such a driver. But they usually don't provide such
drivers for Linux. So what is a boon to MS Windows becomes a bane for
Linux. For devices used primarily on servers such as several digital
modems on a card, Linux drivers will likely be provided since Linux has
about 25% of the server market. But for devices primarily used on
desktops, the manufacturer is unlikely to support Linux and then someone
else needs to hopefully write the driver. This is a major problem for
Linux.
David Lawyer
next prev parent reply other threads:[~2003-02-24 6:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 20:09 serial port speeds >115k; PnP modem ID must contain modem substring Tim
2003-02-22 4:56 ` whitnl73
2003-02-22 9:20 ` David Lawyer
2003-02-23 15:45 ` PnP Rage Hal MacArgle
2003-02-24 4:24 ` David Lawyer [this message]
2003-02-24 14:05 ` Hal MacArgle
2003-02-24 5:59 ` serial port speeds >115k; PnP modem ID must contain modem substring rich+ml
2003-02-24 7:11 ` David Lawyer
2003-02-24 22:50 ` rich+ml
2003-02-24 17:57 ` port speeds >115k Tim
2003-02-25 1:25 ` whitnl73
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=20030224042421.GB417@lafn.org \
--to=dave@lafn.org \
--cc=linux-serial@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