Newbie question...
Posted: Thu Mar 28, 2013 1:38 am
Hello everybody.
To give a bit of background, I've been working with C++/C for the last two years or so as a hobby, and I thought that creating something to boot to would be a fun, educational and daunting task. Plus there's the obvious bonus of being able to control my hardware at a low level. (I say "something to boot to" because when I think of "operating system" I sort of mentally face palm myself
)
I'm finding myself having the same issue I had when I first began with C++, when I first started I looked up a hello world tutorial. I found that the best that the tutorials could offer was a simple, one line explanation of each of the lines and why they exist. Looking back on this I would have done the same thing. Although, I'm wondering if this is the same for assembly (and in extension to learning the tricks of the trade of operating system development.) What I'm really asking is, do I continue and hope some of the underlying meaning to be presented later?
I feel that I have a firm grasp on the basics, I've been reading the first three 'baby steps' tutorials for the last week as well as reading up on the stack and the various modes that must be set during the lifespan of the operating system (over and over, got to make it stick haha) and I'm able to write comments beside each line on why it's important to the bootloader.
Thanks for reading.
Oh, and huge PS:
Any recommendations for assembly PDFs? No books please, unfortunately I don't have the money to buy books.
To give a bit of background, I've been working with C++/C for the last two years or so as a hobby, and I thought that creating something to boot to would be a fun, educational and daunting task. Plus there's the obvious bonus of being able to control my hardware at a low level. (I say "something to boot to" because when I think of "operating system" I sort of mentally face palm myself
)I'm finding myself having the same issue I had when I first began with C++, when I first started I looked up a hello world tutorial. I found that the best that the tutorials could offer was a simple, one line explanation of each of the lines and why they exist. Looking back on this I would have done the same thing. Although, I'm wondering if this is the same for assembly (and in extension to learning the tricks of the trade of operating system development.) What I'm really asking is, do I continue and hope some of the underlying meaning to be presented later?
I feel that I have a firm grasp on the basics, I've been reading the first three 'baby steps' tutorials for the last week as well as reading up on the stack and the various modes that must be set during the lifespan of the operating system (over and over, got to make it stick haha) and I'm able to write comments beside each line on why it's important to the bootloader.
Thanks for reading.
Oh, and huge PS:
Any recommendations for assembly PDFs? No books please, unfortunately I don't have the money to buy books.