1
00:00:00,060 --> 00:00:06,270
So we'll just be prosecuting like this, so we will declare will be declaring one variable religious

2
00:00:06,600 --> 00:00:07,930
name this status.

3
00:00:07,950 --> 00:00:16,080
OK, this is the variable that we declare and then we will be attaching this to the judicial function

4
00:00:16,290 --> 00:00:23,130
to whatever value that I see of judicial function will be stewarding into a status and then we'll just

5
00:00:23,130 --> 00:00:28,820
be checking whether it is is equal to existing success rate.

6
00:00:28,830 --> 00:00:32,040
You would also compare this with the Z or see if that is the case.

7
00:00:32,460 --> 00:00:40,850
We'll just be utilizing the reporting mechanism to convey the message that device initialization is

8
00:00:40,950 --> 00:00:43,000
successful, right?

9
00:00:43,110 --> 00:00:44,340
LS ls.

10
00:00:44,340 --> 00:00:48,660
What are we going to do is we'll just be adding the plaintiff again.

11
00:00:49,120 --> 00:00:49,470
OK.

12
00:00:49,800 --> 00:00:55,120
And then the mentioning that device unit fee, right?

13
00:00:55,140 --> 00:01:01,460
So this helps to debug an entire thing if our devices successfully initialize on.

14
00:01:01,860 --> 00:01:07,260
So these are the series of processes that we're going to follow to initialize our base rate.

15
00:01:07,260 --> 00:01:12,330
So we start with declaration of structure, instant structure and config structure.

16
00:01:12,340 --> 00:01:17,280
So conflict structure will be declaring as a pointer will be utilizing a separate function.

17
00:01:17,280 --> 00:01:22,050
We will be mentioning all the initialization related work, right?

18
00:01:22,080 --> 00:01:25,120
So we declared a status, which is of intent.

19
00:01:25,140 --> 00:01:26,760
No, this could also.

20
00:01:28,290 --> 00:01:31,950
This returns you 32, so you could declare you 32 are.

21
00:01:32,130 --> 00:01:33,090
Doesn't make it right.

22
00:01:33,630 --> 00:01:39,120
So golfing structure the value of one fixed structure will be receiving by utilizing look up config

23
00:01:39,390 --> 00:01:41,910
function where we need to pass device.

24
00:01:42,480 --> 00:01:48,660
So after you complete declaration of a structure, we just need to look for a lookup config keyword

25
00:01:48,720 --> 00:01:49,580
inner driver.

26
00:01:49,680 --> 00:01:50,090
OK.

27
00:01:50,140 --> 00:01:52,460
And as soon as you find out that is the great.

28
00:01:52,460 --> 00:01:56,010
So this is the first step and this returns the pointer rank.

29
00:01:56,010 --> 00:02:01,380
For that reason, we declare here iwconfig structure as a pointer because then we do not need to do

30
00:02:01,380 --> 00:02:06,690
any conversion rate or the next step is when we consider it a studio.

31
00:02:06,700 --> 00:02:13,980
So when we consider the next step is to use c f g initialize, which requires the argument.

32
00:02:13,980 --> 00:02:18,710
First one is an instance structure the config structure and to be set Free State.

33
00:02:18,960 --> 00:02:21,630
So here insert structure as well as on fixed structure.

34
00:02:21,630 --> 00:02:26,640
Our point of no, since we can't declare conflict center itself as a pointer, we just need to pass

35
00:02:26,640 --> 00:02:27,540
through times, is it?

36
00:02:27,970 --> 00:02:31,440
Whereas if you consider the structure, we just need to use.

37
00:02:32,800 --> 00:02:33,870
That was interpreted.

38
00:02:34,240 --> 00:02:36,830
And then you will be mentioning incident structure.

39
00:02:36,880 --> 00:02:37,150
Right.

40
00:02:37,450 --> 00:02:44,830
The said this could be followed by utilizing to the looking for the sector in experimental or or we

41
00:02:44,830 --> 00:02:50,540
could just go to a conflict structure, use this operator OK and then specify the B side.

42
00:02:50,820 --> 00:02:52,960
Right now, this returns you 32.

43
00:02:53,140 --> 00:02:59,260
So we could just declare once you did very well in our nick function and then we will be connecting

44
00:02:59,260 --> 00:03:00,190
it to sea of genes.

45
00:03:00,490 --> 00:03:01,420
So whatever value.

46
00:03:01,720 --> 00:03:07,910
And so if initialization is successful at an altitude and so right, so we'll just be checking that

47
00:03:07,960 --> 00:03:10,120
this status is equal to access to success.

48
00:03:10,120 --> 00:03:12,910
So this is by default declared at zero.

49
00:03:13,150 --> 00:03:16,480
OK, in our tribe of sixes to succes is equal to zero.

50
00:03:16,780 --> 00:03:23,200
So if status is equal to zero or x success, then you will just be mentioning device initialization

51
00:03:23,200 --> 00:03:23,920
is successful.

52
00:03:23,950 --> 00:03:27,850
Else we will be mentioning that device initialization feature.

53
00:03:27,910 --> 00:03:34,630
Right now, what we're going to do is we'll just be going through an x GPIO driver so that you understand

54
00:03:34,630 --> 00:03:35,720
an entire process in.