[Eric-develop] Eric' s VM Arch. and My Source

[Ismail PAZARBASI<paz...@my...>]

Guys,

  I was talking with FreeBSD kernel coders, while they are struggling 
with 4.4 stuff :/

Anyway, I asked few questions. and some are answered, as below:
<Linsux> does btx switch into protected mode?
<BigKnife> Linsux: yes
<Linsux> if btx loads kernel into protected mode, kernel cannot 
access interrupts. so, how freebsd kernel can check if a keypressed, 
for example? how can it use interrupt vectors(or what else?)
<BigKnife> Linsux: it handles interrutps via vm86 mode
<Linsux> oh! hmm ok.. it is btx code?
<BigKnife> Linsux: yes
<Linsux> thx :)
<BigKnife> also, the kernel sets up its own idt fairly early
<BigKnife> and doesn't use the BIOS ISR's at all
<BigKnife> it uses driver interrupt handlers

btx code is in /usr/src/sys/boot/i386/btx/btx/btx.s in any FreeBSD 
distribution.

This is why I cannot handle interrupts (about keyboard). Because BTX 
is working in protected mode. So, I must make lille hacking stuff to 
load our own ISRs, not BSDs. I have made some changes in code. I 
created  dirs named /dev and /objs. dev is main device dir, and there 
is only kbd.cpp and kbd.h are there. but, I will add vga.cpp there 
too. I have made little hacking on sys/types.h (actually, not hacking 
but rewriting it) from BSDs one. All compiled objects are placed 
under objs dir. and kernel linked under root of sources.

You can download the zip file from 
http://pazarbasi.com/filemanager/list/7/

Guys, i think we need to handle that interrupts and related isrs to 
write drivers. Do you have docs about these stuff? I have seen many 
things on the net. I am just reading now. I will try to hack btx code 
2 days later.

PS: Gavin, what is that "Bad News" mail exactly? I dont understand at 
all i think :/


Regards.

__________________________________________________
=DCCRETS=DDZ E-MAIL ALDINIZ MI?
T=FCrk=E7e ilk Portal  http://www.mynet.com