OSDev.org

crunch wrote:Is your plan to just post about every single step in os development? Obviously you are not picking up on the fact that you MUST be able to read documentation and then be able to translate that into code.

There is no problem with asking questions. This stuff can be difficult to grasp. If you're getting stuck here, you're not going to make it much farther (without significant handholding) until you learn how to rtfm

NunoLava1998 wrote:"IDTR(Limit) ← SRC[0:15];
IDTR(Base) ← SRC[16:47]; "

The thing is, how do i implement this?

Velko wrote:

NunoLava1998 wrote:"IDTR(Limit) ← SRC[0:15];
IDTR(Base) ← SRC[16:47]; "

The thing is, how do i implement this?

You have already implemented this. Function lidt() in your mainf.c, starting at line 104 does exactly that. (Assuming your Github DixiumOS repo is up to date).

Or did you copy the code from somewhere, without knowing what it is for? You have to quit that habit.

It is normal to look at other peoples code to see how things are done. Or even copy some, but you must always understand what it does.
Get inspired from it, play around, break it, fix it, break it again, but never copy blindly.

That being said, are you familiar with JamesM or Bran's kernel development tutorials?

NunoLava1998 wrote: I meant how to make something like:

"char limit[16];
char base[16..47];"

NunoLava1998 wrote:I meant how to make something like:

"char limit[16];
char base[16..47];"

struct {
        uint16_t length;
        void*    base;
} __attribute__((packed))

NunoLava1998 wrote: I meant how to make something like:

"char limit[16];
char base[16..47];"