http://developer.intel.com/ - Search for Manuals
http://www.x86.org
http://www.sandpile.org
Do not rejoice that ur code works.
it might be a special case of an error :-(
I hope ur problem arises because of 2 OSes.If u
read and write via 1 OS, then caching
should not be a problem.
But since u r write for One OS and read
from Other, the problem persists.
Try to do both reads and writes via a single
OS. Thats the solution.
Otherwise, probablu u may need to...
Guys,
Any1 aware of good web-sites for learning
powerPC architecture and assembly lanugage
progamming.
Thanx in advance
sarnath
Do not rejoice that ur code works.
it might be a special case of an error :-(
Hey,
Just compile "C" code (statically along
with library ). Link it using LD as a "BINARY'
and relocate the code address( say 0x1000 ) appropriartely..
Now load ur C code into the empty 8086 machine at
address 0x1000.
Note: u need to initialize segment registers
as...
I honour ur views but
i dont agree with them.
Fine,
All the best for ur OS
adventures.
ciao
Sarnath
Do not rejoice that ur code works.
it might be a special case of an error :-(
Hey AMKG,
This is really interesting..
It is like "Monkey -> Man" and then "Man -> Monkey".
Appln programs can't be expected to be innocent.
If u release an OS with appln having more responsibilities, i agree everything would be fast.. But how about security...
Ekanth,
I fear u have mis-understood PM address genereation
Its is not like seg-offset addressing.
I'll put it crisply.
1.
I dont find a LGDT instruction in ur code.
Thats the first problem. ( If u r using MASM in DOS,
then u need to explicitly use a .386p directive.
otherwise MASM wont...
Hey ekaanth,
Try doing ur kernel as an ELF image.
I m not sure how complicated loading would be then.
But When u r an ELF, u will have lot of advantages
like, u can make Page-level protection for ur code,
and RODATA (read-only data) etc.. (trapping of bugs
in kernel code can b done in early...
Ekaanth,
Compiler ur C code into Binary.
U can use gcc/ld which would be a very
powerful tool to do all such work.
Ur Entry Point in the "C" code should
know about certain things. For exp, it
might need to asssume that PM and paging
are already setup. Ur memory map during bootup...
Hi Ekaanth, ( Tamilian ?? )
Writing a PM boot strap should b cool yaar.
Let ur BootSector load 3 sectors at a time into
real memory, then switch to PM swapout the memory into
wherever u wanna ur kernel to load and then return back
and continue with it..
If u want a code to beleive it,
u...
Hey ,
DOnt take peter abbel.. Its not for beginners,
altho he may claim so..
I think u can study a book on assemblers..( Leyland Beck's
system software book.) and then get on to PeterNorton.
Else
Take "Art of assembly" => Thats the most fantastic
i had ever seen
Do not...
An OS standard ?!?!
Have u ever tried reading the POSIX ?
If u dont have protection in place, any APP program
can crash ur kernel. Whats the fun in doing such
a kernel ? I dont really understand that part. Is it
intended to be a RT-OS ?
I think probably u need to read a OS text book.
Jus...
Does QBASIC prepend an "_" b4 its symbols.. ??
Try putting an "_" before NASM symbols...HEy, a minute..
u said QBASIC right..Is it not interpretted ???
If ur QBASIC code is interpretted rather than compiled,
then i fear there is no way to call ur ASM routines :(
Sarnath
Do...
Hi,
The EXE file structure of DOS has fields reserved
for StackPointer. So, ur initial SP would already
be loaded by the EXE file loader. Moreover the loader
loads the Segment register with value of ur PSP.
(Program segment prefix ). hence the observation
Sarnath
Do not rejoice that ur code...
AMKG,
U r right that deadlock problems can occur
only in Multi-Processing systems.., where there are
multiple-processors running concurrently.
In a single-processor systems, INTERRUPTS are the
only problem. Hence UNIX type OSes have
sthg called Software Privilege levels for selectively...
1. What does ESI point to ?
Is it a valid pointer in ur program's address space.
2. While using inline assembly with GCC, u need to be
careful about few things. For exp, the COMPILER never
knows anything about the registers u r destroying.
If u dont inform GCC that u r destroying a...
I think "..start" is the problem.
Jus say "start:"
That would do..
If this works, vote me as the TIP Master of the week..
ha ha ha...
just joking..
Sarnath
Do not rejoice that ur code works.
it might be a special case of an error :-(
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.