1 00:00:00,100 --> 00:00:09,230 So no, for each of our driver, if you explore the Halo fight, so we have look up conflict, OK, 2 00:00:09,240 --> 00:00:14,130 this is what North and EPA, which will be present in almost all the periphery. 3 00:00:14,400 --> 00:00:17,450 And we need to pass one argument to here, right? 4 00:00:17,490 --> 00:00:25,290 So once you apply an argument, this will return the expropriated conflict structure. 5 00:00:26,530 --> 00:00:31,370 So whatever data that we have in this structure is written by look upon. 6 00:00:31,530 --> 00:00:38,570 So this will always be a first step when we try to initialize up, say, look, we're just looking for 7 00:00:38,570 --> 00:00:42,780 a driver and we will be searching for Luca Quantic, right? 8 00:00:42,780 --> 00:00:49,100 So as soon as we have a look local conflict, OK, here we need to pass device eight. 9 00:00:49,550 --> 00:00:55,680 And where you will be getting a device I.D. So all the hardware related information could be easily 10 00:00:55,680 --> 00:00:58,230 accessed from X parameters. 11 00:00:58,920 --> 00:01:00,960 Dark H funny, right? 12 00:01:00,990 --> 00:01:02,490 So you just need to include this. 13 00:01:02,490 --> 00:01:10,500 And when you press 50, this will take you inside this chamber and you then you just need to find out 14 00:01:10,500 --> 00:01:13,830 the specific benefit and related information. 15 00:01:13,840 --> 00:01:21,270 So if you are looking for GPI related information, you just need to place control to find GPI. 16 00:01:21,660 --> 00:01:21,920 OK? 17 00:01:21,960 --> 00:01:29,370 You just need to think that you then you will be automatically reaching to all the data so that the 18 00:01:29,370 --> 00:01:31,440 first transmission will always be a device. 19 00:01:31,650 --> 00:01:37,520 So once you find out the device, you just need to copy that and you need to specify A. Where here? 20 00:01:37,600 --> 00:01:37,890 Right. 21 00:01:37,890 --> 00:01:43,080 So once you splice a device, hey, this will retain a config structure right now. 22 00:01:43,080 --> 00:01:49,890 These two are the mandatory thing for initializing a paper and then utilizing lookup config by a single 23 00:01:49,890 --> 00:01:50,310 device. 24 00:01:51,090 --> 00:01:51,480 OK. 25 00:01:51,510 --> 00:01:53,940 We will be getting this force structure right. 26 00:01:54,210 --> 00:01:56,990 The next is the experiment, right? 27 00:01:57,000 --> 00:01:57,330 So. 28 00:01:58,320 --> 00:02:06,960 How we initialize the devices, you have CFD initialize function, right? 29 00:02:06,990 --> 00:02:08,870 This is the second function, right? 30 00:02:09,230 --> 00:02:14,280 No, this will be useful in initializing not very polite, and this requires three argument. 31 00:02:14,280 --> 00:02:21,410 First, the document is the structure which will be handling all the data off your, for instance, 32 00:02:21,630 --> 00:02:25,020 so will be simply repeating it's an instance structure, right? 33 00:02:25,920 --> 00:02:30,030 That basically means it will hold all the data specific to the page. 34 00:02:30,270 --> 00:02:30,570 Right. 35 00:02:30,910 --> 00:02:38,280 So first argument is the structure which have all the data related to an instance, right to first document 36 00:02:38,280 --> 00:02:42,240 it, the structure which will all the data related to an end. 37 00:02:42,600 --> 00:02:47,250 The second argument is this config structure right to structure. 38 00:02:47,790 --> 00:02:52,020 Then we have a conflict and the last one is the said is no. 39 00:02:52,920 --> 00:03:00,680 The good part is the config structure itself consist of Obi, etc. So we could just use struct config. 40 00:03:00,720 --> 00:03:06,000 OK, and then we have this obliterates the SUDESH and then greeted that. 41 00:03:06,240 --> 00:03:14,400 So this and then we will see be said today that these are the three argument which are messy right now. 42 00:03:14,400 --> 00:03:20,700 You could see why we are focusing on the page that is instance structure and the config structure, 43 00:03:20,700 --> 00:03:26,850 because the function that we have to initialize almost all the drivers cmg initialize, right? 44 00:03:27,180 --> 00:03:29,310 And that will require three argument. 45 00:03:29,310 --> 00:03:32,010 First one is the instance structure. 46 00:03:32,280 --> 00:03:38,460 Second one is the config structure and third one is the no BS that this could also be found out from 47 00:03:38,460 --> 00:03:39,180 its parameter. 48 00:03:39,180 --> 00:03:39,650 Nottage. 49 00:03:39,990 --> 00:03:40,350 OK. 50 00:03:40,650 --> 00:03:47,250 So we have a three argument which are mandatory for initializing any of the very first rate. 51 00:03:47,340 --> 00:03:53,400 The first argument is instance, instance structure, OK. 52 00:03:53,790 --> 00:03:56,970 The second argument is the one fixed structure. 53 00:03:58,120 --> 00:04:07,930 And the last one is to be said right now, what we will be doing is for an instance of after we will 54 00:04:07,930 --> 00:04:10,750 just be declaring an independent structure. 55 00:04:11,000 --> 00:04:15,870 OK, so that will usually be found out from the device. 56 00:04:16,540 --> 00:04:22,670 So we'll just be declaring and insta a structure that is the first thing that we do to initialize. 57 00:04:23,230 --> 00:04:27,460 The second thing that we do is to add a conflict structure. 58 00:04:27,510 --> 00:04:32,760 Now, just citing a conflict structure won't help us until unless we get the data related to a very 59 00:04:32,800 --> 00:04:39,130 foreign land that could be found out by utilizing utilizing look up config API. 60 00:04:39,160 --> 00:04:39,500 Right. 61 00:04:39,520 --> 00:04:45,410 And once you force your device idea over here, which could be found out from its parameter. 62 00:04:46,300 --> 00:04:51,220 So once you add a device, you will hear this basically written the config structure. 63 00:04:51,520 --> 00:04:58,360 So once you declare this to structure, the first thing that we will be doing, little do we declare 64 00:04:58,360 --> 00:05:05,000 the one function that will be handling all the dos related to initialization. 65 00:05:05,020 --> 00:05:05,350 Right? 66 00:05:05,650 --> 00:05:11,680 So here what we going to do is the first step is to connect our config structure. 67 00:05:12,010 --> 00:05:14,020 OK, so we have a config structure. 68 00:05:15,040 --> 00:05:19,390 And this will be connected to the look up config function. 69 00:05:20,710 --> 00:05:27,130 Or an API that will be getting in and try to find right now the need for lookup on King API will be 70 00:05:27,130 --> 00:05:29,830 different, but you will be finding this key will lookup config. 71 00:05:29,840 --> 00:05:34,810 You just need to look for the specific drivers that are available for line here. 72 00:05:34,990 --> 00:05:37,710 You just need to buy a device, right? 73 00:05:37,720 --> 00:05:38,650 That is the first step. 74 00:05:38,950 --> 00:05:44,230 So outside, this function will all already be declaring one instance structure. 75 00:05:45,670 --> 00:05:46,030 OK. 76 00:05:46,270 --> 00:05:50,710 And what is the config structure, so this will already be declared? 77 00:05:50,890 --> 00:05:51,160 Right. 78 00:05:51,790 --> 00:05:53,680 So want this to are clear? 79 00:05:53,740 --> 00:05:59,920 This is the next step that is finding out an EPA, which consists of lookup config, specify the device 80 00:05:59,920 --> 00:06:02,500 ID and this will retain the quality structure, right? 81 00:06:02,890 --> 00:06:10,360 Once you complete this process, the next step is to utilize the next API that is CFD. 82 00:06:11,340 --> 00:06:17,570 Initially, right, so you just need to look for Trailer and then find out this kind of keyword CMG 83 00:06:17,580 --> 00:06:18,150 initially. 84 00:06:18,600 --> 00:06:20,400 This will require three arguments. 85 00:06:20,580 --> 00:06:26,160 First one is the instant structure to your first argument and is expecting a pointer from us. 86 00:06:26,160 --> 00:06:30,870 So we'll just be utilizing Annapolis and then passing a structure, right? 87 00:06:30,870 --> 00:06:32,070 So instant structure. 88 00:06:32,880 --> 00:06:40,140 The second argument is the key point for a config structure and only thing that we'll be doing when 89 00:06:40,140 --> 00:06:41,820 we declare an instance of children. 90 00:06:41,820 --> 00:06:46,440 Config structures will be declaring config structure as a pointer itself. 91 00:06:46,650 --> 00:06:48,870 So this will just for our convenience. 92 00:06:49,560 --> 00:06:55,290 So when we add a second argument here, because this function do read in the context of your pointer. 93 00:06:55,770 --> 00:07:00,150 OK, so and then and I think handling an entire thing becomes very, very easy. 94 00:07:00,180 --> 00:07:06,150 So here we just need to add a config structure because we declared it itself as a pointer. 95 00:07:06,390 --> 00:07:12,250 OK, the last argument is that we set this, which could be taken out from a config structure, right? 96 00:07:12,300 --> 00:07:14,310 So config structure that will be added. 97 00:07:14,850 --> 00:07:18,830 And then we just need to use this operator and then be sectors. 98 00:07:18,840 --> 00:07:24,720 Or you could just go ahead and look for X parameter knowledge and find out the base had just for your 99 00:07:24,720 --> 00:07:25,250 benefit. 100 00:07:25,530 --> 00:07:31,920 So these are the series of steps that you need to remember, and these are eligible for almost all the 101 00:07:31,920 --> 00:07:32,390 drivers. 102 00:07:32,400 --> 00:07:39,020 OK, so the data related to config structure or, for instance, structure miway for a very pretty vocal, 103 00:07:39,060 --> 00:07:45,060 depending on whether it is simple, intermediate or complex, but the procedure to initialize it is 104 00:07:45,840 --> 00:07:47,490 common for all right. 105 00:07:47,520 --> 00:07:55,260 So if initialization is successful, this basically returns existing sexists so OK, or it is basically 106 00:07:55,260 --> 00:08:02,160 written zero, which we represent an existing service, so we define a micro way racist, sexist is 107 00:08:02,160 --> 00:08:02,960 equal to Z. 108 00:08:02,970 --> 00:08:04,350 So what are we going to do next? 109 00:08:05,100 --> 00:08:09,810 We will also be verifying whether I initialization is successful or not.