public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Olson <dano@agora.rdrop.com>
To: linux-8086@vger.kernel.org
Subject: ELKS questions
Date: Sun, 8 Dec 2002 17:01:16 -0800 (PST)	[thread overview]
Message-ID: <20021208163800.S83751-100000@agora.rdrop.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212060150050.11113-100000@olympus.btstream.com>

Hi,
	I've got a number of questions that I'm just going to stick into
one message, hope it doesn't get too long!

First off, I was wondering what would be involved in getting SCSI support
in ELKS.  I assume that it would require code compiled into the Kernal
(for CD-ROM and tape support, beyond hard drives which have BIOS code)
which would probably be an involved project and not a practical one.  Is
it easier than I think?

I've noticed recently under Linux when I tried to use an 84 key keyboard,
it behaved as if the numlock was always on, so I had no arrows.  I suspect
I told the OS that I had a 101 key keyboard as I did have when I
installed.  Does ELKS have any configuration for keyboard types (besides
country differences)?  I would expect it to behave like MS-DOS where both
types can be interchanged without the OS being told.

Is there any advantage to using a 286 aside from things like bus width
and clock speed, etc?  In otherwords, is protected mode supported in any
way, or is there any code that uses the extended memory?  Anything
planned?  I don't neccessarly care either way, but I do have a number of
286s around and it occured to me that of course they won't run Linux, and
I wasn't aware of any advantage of them over an 8086 for ELKS.

I tried to get Lilo installed on an ELKS disk yesterday with no luck.  I
am able to take a slakware boot disk, stick it in my IBM XT, and get a
boot screen and a prompt allowing me to pass parameters to the Kernal if
needed.  This makes me think that Lilo is running on my V20 but I couldn't
figure out how to install it on disk...I've always used the default
from the installer for my Linux installs.  Has anyone looked into Lilo for
ELKS?  Is it even useful if it does work?

Under Linux supposedly it's not possible to have RS-232 ports sharing
IRQs, as they do under DOS.  Will ELKS support more than two serial ports,
and if so, can 1 and 3 or 2 and 4 share IRQs?

I'd love to have something similar to GPM under ELKS, has anyone thought
about such a program?  Is it possible?  Would it just be a command line
program or more involved, making it difficult to implement?

I booted up ELKS on the XT a couple days ago, made a directory, did and
"ls -l", and of course it was dated 1970 or whatever the default date is.
Okay, so yesterday I'm in the surplus section of the electronics store,
and there's a little 8 bit card with a few chips and a battery...I assume
a clock card.  First off, are RTC cards supported?  If so, is it just set
with "date"?  Are there different types of clocks to choose from, or will
any work?  I'll try my new card the next time I boot ELKS.

Again, sorry for how long this mail is, hopefully someone else will find
all of this interesting :)

	Dan


  reply	other threads:[~2002-12-09  1:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 10:15 clock.c/bcc bug jb1
2002-12-09  1:01 ` Dan Olson [this message]
2002-12-19 23:53 ` Tandy 1000 and IBM PS/2 Dan Olson

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=20021208163800.S83751-100000@agora.rdrop.com \
    --to=dano@agora.rdrop.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