Repository navigation
Replies: 1 comment 7 replies
|
Hello @tyama501,
I'm not sure whether the bigger benefit would be reducing the dependency on BIOS, since that will always be present on PC98, or instead moving from a polling to interrupt-driven keyboard. It's probably not a big deal, but if you'd like to add a PC98 direct keyboard driver, please go right ahead! I notice from the Linux source that their PC98 keyboard driver uses IRQ 1, just like our kbd-scancode.c. Have you ever tried compiling and using the existing kbd-scancode driver from IBM PC for PC98? This may work with little change, other than possibly some special initialization. If the hardware for reading the scancode is much different, it would probably be better to start from scratch, possibly by copying kbd-scancode.c and then adding code from PC98 Linux 7.1. This is because the IBM PC scancode handler also handles console switching, etc you would want. You may also have to build a custom scancode table for it as well, starting from a table in drivers/char/Keymaps/keymaps.h (these allow for international keyboards layouts, not sure if the PC98 has multiple keyboards). I also noticed a PC98 bus mouse driver: https://github.com/awemorris/linux-pc98/blob/master/linux-7.1/drivers/input/mouse/pc98busmouse.c. Is this what you're using for Nano-X, or is that a serial driver? We now support a PS/2 mouse for IBM PC. Thank you! |
|
Yes, pc-98 also uses 765 for the floppy controller. There is lots of great protect mode OS, so I also don't think it is the main target of elks :) |
|
BTW, |
Yes, I have been wanting to release it, but during the last couple of weeks, there seems to have been multiple submissions and/or issues every day. So I hope to get it out ASAP, as soon as this last batch of PRs get committed, and also just after the ftpd issue being discussed. Thank you! |
|
That's great to hear. Out of curiosity, do you have a "wishlist" of things ELKS user would like to see or a "roadmap to release 1.0" -- ie implemented functionality, resolved bugs. etc that once that criteria is met you would designate it the 1.0 release? |
|
No, not really anymore. In the years past, there were so many things not working that I just kept the version number moving up very incrementally. Things work well now. I've been trying to get 0.9.2 out for some time, there's a lot of great new functionality that's been added, but it seems contributors are on a roll, and there hasn't been a calm period but I hope to get the next version out ASAP. We should open a wishlist PR to see what people want, but in general, people expect stability and usability out of the box, and ELKS is doing pretty well in that area, it seems. Fringe features seem less important. A harder part is going to be trying to contain everything to be built on floppy, as booting and installing HD systems removes a large swath of ELKS users, it seems. I would like to see loadable kernel modules as a major feature, but I haven't been able to figure out how to do it without major compiler support, which would likely require switching to OpenWatcom C and using its quasi-16-bit DLL compiler support. What would likely be required would be moving away from a.out format to OS/2 NE. Another nice addition would be documentation or man pages for all comments. But that won't fit on a floppy either. However, man pages come in handy when using |
Uh oh!
There was an error while loading. Please reload this page.
It seems that linux 7.1 kernel and Debian 13 have been ported to PC-98 and these are actually working on the 386/486/Pentium machines.
https://github.com/awemorris/linux-pc98
There is pc-98 keyboard driver and it might be good reference to reduce the dependencies of bios keyboard driver on elks.
https://github.com/awemorris/linux-pc98/blob/master/linux-7.1/drivers/input/keyboard/pc98kbd.c
All reactions