So no, for each of our driver, if you explore the Halo fight, so we have look up conflict, OK,
this is what North and EPA, which will be present in almost all the periphery.
And we need to pass one argument to here, right?
So once you apply an argument, this will return the expropriated conflict structure.
So whatever data that we have in this structure is written by look upon.
So this will always be a first step when we try to initialize up, say, look, we're just looking for
a driver and we will be searching for Luca Quantic, right?
So as soon as we have a look local conflict, OK, here we need to pass device eight.
And where you will be getting a device I.D. So all the hardware related information could be easily
accessed from X parameters.
Dark H funny, right?
So you just need to include this.
And when you press 50, this will take you inside this chamber and you then you just need to find out
the specific benefit and related information.
So if you are looking for GPI related information, you just need to place control to find GPI.
OK?
You just need to think that you then you will be automatically reaching to all the data so that the
first transmission will always be a device.
So once you find out the device, you just need to copy that and you need to specify A. Where here?
Right.
So once you splice a device, hey, this will retain a config structure right now.
These two are the mandatory thing for initializing a paper and then utilizing lookup config by a single
device.
OK.
We will be getting this force structure right.
The next is the experiment, right?
So.
How we initialize the devices, you have CFD initialize function, right?
This is the second function, right?
No, this will be useful in initializing not very polite, and this requires three argument.
First, the document is the structure which will be handling all the data off your, for instance,
so will be simply repeating it's an instance structure, right?
That basically means it will hold all the data specific to the page.
Right.
So first argument is the structure which have all the data related to an instance, right to first document
it, the structure which will all the data related to an end.
The second argument is this config structure right to structure.
Then we have a conflict and the last one is the said is no.
The good part is the config structure itself consist of Obi, etc. So we could just use struct config.
OK, and then we have this obliterates the SUDESH and then greeted that.
So this and then we will see be said today that these are the three argument which are messy right now.
You could see why we are focusing on the page that is instance structure and the config structure,
because the function that we have to initialize almost all the drivers cmg initialize, right?
And that will require three argument.
First one is the instance structure.
Second one is the config structure and third one is the no BS that this could also be found out from
its parameter.
Nottage.
OK.
So we have a three argument which are mandatory for initializing any of the very first rate.
The first argument is instance, instance structure, OK.
The second argument is the one fixed structure.
And the last one is to be said right now, what we will be doing is for an instance of after we will
just be declaring an independent structure.
OK, so that will usually be found out from the device.
So we'll just be declaring and insta a structure that is the first thing that we do to initialize.
The second thing that we do is to add a conflict structure.
Now, just citing a conflict structure won't help us until unless we get the data related to a very
foreign land that could be found out by utilizing utilizing look up config API.
Right.
And once you force your device idea over here, which could be found out from its parameter.
So once you add a device, you will hear this basically written the config structure.
So once you declare this to structure, the first thing that we will be doing, little do we declare
the one function that will be handling all the dos related to initialization.
Right?
So here what we going to do is the first step is to connect our config structure.
OK, so we have a config structure.
And this will be connected to the look up config function.
Or an API that will be getting in and try to find right now the need for lookup on King API will be
different, but you will be finding this key will lookup config.
You just need to look for the specific drivers that are available for line here.
You just need to buy a device, right?
That is the first step.
So outside, this function will all already be declaring one instance structure.
OK.
And what is the config structure, so this will already be declared?
Right.
So want this to are clear?
This is the next step that is finding out an EPA, which consists of lookup config, specify the device
ID and this will retain the quality structure, right?
Once you complete this process, the next step is to utilize the next API that is CFD.
Initially, right, so you just need to look for Trailer and then find out this kind of keyword CMG
initially.
This will require three arguments.
First one is the instant structure to your first argument and is expecting a pointer from us.
So we'll just be utilizing Annapolis and then passing a structure, right?
So instant structure.
The second argument is the key point for a config structure and only thing that we'll be doing when
we declare an instance of children.
Config structures will be declaring config structure as a pointer itself.
So this will just for our convenience.
So when we add a second argument here, because this function do read in the context of your pointer.
OK, so and then and I think handling an entire thing becomes very, very easy.
So here we just need to add a config structure because we declared it itself as a pointer.
OK, the last argument is that we set this, which could be taken out from a config structure, right?
So config structure that will be added.
And then we just need to use this operator and then be sectors.
Or you could just go ahead and look for X parameter knowledge and find out the base had just for your
benefit.
So these are the series of steps that you need to remember, and these are eligible for almost all the
drivers.
OK, so the data related to config structure or, for instance, structure miway for a very pretty vocal,
depending on whether it is simple, intermediate or complex, but the procedure to initialize it is
common for all right.
So if initialization is successful, this basically returns existing sexists so OK, or it is basically
written zero, which we represent an existing service, so we define a micro way racist, sexist is
equal to Z.
So what are we going to do next?
We will also be verifying whether I initialization is successful or not.