* clock.c/bcc bug
@ 2002-12-06 10:15 jb1
2002-12-09 1:01 ` ELKS questions Dan Olson
2002-12-19 23:53 ` Tandy 1000 and IBM PS/2 Dan Olson
0 siblings, 2 replies; 3+ messages in thread
From: jb1 @ 2002-12-06 10:15 UTC (permalink / raw)
To: linux-8086
What appears to be a bug in elkscmd/sys_utils/clock.c is probably a bug in
bcc's parser for #asm/#endasm blocks.
The original clock program does not display the CMOS real-time-clock
correctly. Although the update-in-progress seems to be detected correctly,
each of the time/date registers appears to return the value in the
"seconds" register.
I found that at least "clock", "clock -r" and "clock -s" work correctly if
a semicolon is placed on the line immediately preceding the first "#asm"
or the line immediately following the first "#endasm" in the cmos_read()
function. For example:
unsigned char cmos_read(reg)
unsigned char reg;
{
register unsigned char ret;
; /* <------------- Null-statement workaround for bcc (?) bug -- jb1 */
#asm
cli
#endasm
outb (reg | 0x80, 0x70);
...
As far as I know, such a null statement should generate no code, yet the
filesize is increased from 7528 to 7544 bytes.
While this workaround seems to have fixed clock.c, there are probably
other programs that compile incorrectly!
^ permalink raw reply [flat|nested] 3+ messages in thread
* ELKS questions
2002-12-06 10:15 clock.c/bcc bug jb1
@ 2002-12-09 1:01 ` Dan Olson
2002-12-19 23:53 ` Tandy 1000 and IBM PS/2 Dan Olson
1 sibling, 0 replies; 3+ messages in thread
From: Dan Olson @ 2002-12-09 1:01 UTC (permalink / raw)
To: linux-8086
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Tandy 1000 and IBM PS/2
2002-12-06 10:15 clock.c/bcc bug jb1
2002-12-09 1:01 ` ELKS questions Dan Olson
@ 2002-12-19 23:53 ` Dan Olson
1 sibling, 0 replies; 3+ messages in thread
From: Dan Olson @ 2002-12-19 23:53 UTC (permalink / raw)
To: linux-8086
Hi,
Sorry if this is already answered somewhere. I have a Tandy 1000
that I'd like to get ELKS on. I remember that there were issues in the
past with the 1000 because it shares video memory with base memory, as the
PCjr does. I know there's been some work on these systems, does ELKS now
work on them by any chance? I also have an IBM PS/2 and I recall the
keyboard didn't work for some reason. The machine is in storage, but I
thought I might as well ask is anyone know the lastest on it too, as both
are somewhat unusual systems. Thanks.
Dan
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-12-19 23:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-06 10:15 clock.c/bcc bug jb1
2002-12-09 1:01 ` ELKS questions Dan Olson
2002-12-19 23:53 ` Tandy 1000 and IBM PS/2 Dan Olson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox