I actually ended up checking how to read and write a sector, but more than anything else at them moment I have been reading multiple articles+ the indispensable hardware book, Im past chapter 6 now+ have made sure I have covered all the theory in the brokenthorn articles as off today so my brain is kinda on information overload
Just for anyone thats interested in the indispensablle hardware book well now that I am getting into the interesting stuff I can 100% say that its an absolute brilliant reference coupled with brans tutorial. What Ive done is jumped between brans guide paging theory+ TI_PC _HW_Book+ brokenthorn paging articles and Im alot happier with paging now .Im kinda unsure how to start my memory management though
. I am thinking along the lines of creating a heap then divide the memory up, decide what parts of memory are to get used for what but Im unsure of how to go beyond just slicing memory into blocks to making it so some kind of running task gives out memory to apps.
I am maybe thinking of it all wrong but I am thinking maybe I need to figure out how to have mini programs that run in their own part of virtual memory(e.g each program being its own independent task) before a memory manager is warranted? Its just currently I have memset and memcpy implemented and Im wandering whether to just go on and try and do the multitasking guide thats on osdev(I saw it in the tutorial list but haven't had a chance to read it so not sure how good it is). I have been reading a fair bit about paging and it seems to put alot of things in place(Which Im still digesting all that info hehe) so Im wandering what exactly I can provide by chopping up memory into blocks.
I know a memory manager is needed I actually am unsure of how to go about it though so Im away to see what I can find
- its tempting just to use my basic memset, memcpy to set memory and try and get some form of multi-tasking setup. I know little of multi-tasking except that the TSS statement can come into play, I will have to check that out but Im am afraid to because the more I read makes me realize I need to read even 10* more lol
edit-----------------------
Checking out
http://www.jamesmolloy.co.uk/tutorial_h ... 0Heap.html and all those guides now, those seem a good continuation of what I was doing and answer some of my dumb assumptions and questions in this latter post hehe
It would be nice to know what books and such some of the article writers had to read before they were able to confidently handle all this stuff(Hopefully in an honest way, not "I read the intel manual once when I was 5 and it all just came to me"
, Im just curious to know , Im kinda assuming most of them are computer science students doing Bsc or Msc but still would be good to know for sure and what books really they felt benefited them - I know about the books thread but thats not just specific to the article writers)
To write articles on such a subject in an interesting way which they have achieved in my view must be tricky and to make it understandable. To me that says if they write articles they have a really good grasp of it and must have read some specialist books above and beyond what your average joe reads . I wasn't happy about the high price I paid for the indispensable PC hardware book but now that I have it and Im only at chapter 6 part way through, I realize it is a gem of a book,its already tieing in with some guides.(I'm not sure if it has more code later but Im assuming just well explained theory with minimum code)
Either way looking through
http://www.jamesmolloy.co.uk/tutorial_h ... 0Heap.html
I can see I am going to have to be studying that for a few days minimum. It uses kmalloc which I need to get to grips with all that why its using that, will start on that tomorrow. Also seems to be more stuff for handling paging so I better go through it before I consider writing a memory manager+ it shows how to setup a heap
[Seems alot of stuff to consider in this guide though, which is good! but at the same time I think I am going to be reading for months yet lol)
