From: Jody Bruchon <jody@jodybruchon.com>
To: linux-8086@vger.kernel.org
Subject: EMS support will probably never happen
Date: Fri, 17 Feb 2012 09:48:01 -0500 [thread overview]
Message-ID: <4F3E68A1.6080300@jodybruchon.com> (raw)
In-Reply-To: <4F3E65B3.3070401@cowlark.com>
Unfortunately, the LIM EMS specification seems to be an API spec for
programs and drivers, not a hardware interface standardization. IBM,
Intel, AST, and others apparently all use a totally different driver
with different interfaces. Also, based on the extreme price of EMS cards
on eBay and the very small number of them I am finding, EMS support is
probably a waste of time to even think about. There is no standard
hardware interface, and if the hardware is so hard to find that I can't
get it to test with anyway, there's little point in planning to add
support for it. Unless someone has a valid objection, tonight I will
remove the placeholder code for EMS support and the EMS support option
which does nothing anyway.
Just to be clear about what I'm doing, I'm trying to shrink the ELKS
code base by stripping out vaporware and useless code, particularly
since one direction we are interested in taking is porting to a
different compiler, and every single line of code that's not necessary
when such work begins will only be an additional burden at that time.
Plus, novices who look at ELKS and happen to enable those options will
see options for drivers that simply don't exist or aren't functional,
and then be confused when it doesn't work.
Jody Bruchon
prev parent reply other threads:[~2012-02-17 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jXCVB0ylFfhQ.p6tLq6MJ@posti.saunalahti.fi>
2012-02-17 9:35 ` elksfs removed from ELKS kernel; EMS memory needed Kirn Gill
2012-02-17 14:35 ` David Given
2012-02-17 14:48 ` Jody Bruchon [this message]
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=4F3E68A1.6080300@jodybruchon.com \
--to=jody@jodybruchon.com \
--cc=linux-8086@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).