WEBVTT 00:00.000 --> 00:08.000 I think then we are ready, is it? 00:08.000 --> 00:11.000 Yes, yes. 00:11.000 --> 00:14.000 Okay, so welcome. 00:14.000 --> 00:16.000 My name is Mitre and this is Chris. 00:16.000 --> 00:23.000 We work for Linaur and we work on the in the Qualcomm ecosystem team. 00:23.000 --> 00:27.000 And today we want to talk about the strange thing. 00:27.000 --> 00:29.000 And also an arm laptops. 00:29.000 --> 00:33.000 And a continuation of the previous talk. 00:33.000 --> 00:37.000 The previous talk was about a switching from device 3 to a CPI. 00:37.000 --> 00:39.000 We want to do it another way around. 00:39.000 --> 00:43.000 We want to switch from a CPI to the device 3. 00:43.000 --> 00:47.000 So first of all, why is it all about windows on arm? 00:47.000 --> 00:52.000 Yeah, up to now, all arm 64 laptops will snap dragons, but welcome. 00:52.000 --> 00:56.000 And all of them will, of course, have booting windows. 00:56.000 --> 00:59.000 All of them are using a CPI to boot windows. 00:59.000 --> 01:08.000 But sadly enough, Qualcomm and Microsoft decided that they don't want to have everything in the CPI tables. 01:08.000 --> 01:13.000 They created a thing called P.P. Package, whatever. 01:13.000 --> 01:15.000 Platform accession plugins. 01:15.000 --> 01:17.000 Yeah, platform. 01:17.000 --> 01:22.000 Which basically moves a ML2 bind to windows drivers. 01:22.000 --> 01:25.000 So thank you. That's very helpful. 01:26.000 --> 01:29.000 But that does not help in our case. 01:29.000 --> 01:32.000 So CPI tables are basically non-complete. 01:32.000 --> 01:37.000 Non-working, sad, a disaster. 01:37.000 --> 01:42.000 So from the day zero or from the day one of arm 64 laptops. 01:42.000 --> 01:45.000 Or Qualcomm arm 64 laptops. 01:45.000 --> 01:49.000 Platform containers decided that all laptops should use device 3s. 01:49.000 --> 01:56.000 And if you follow or if you have heard anything about the laptops, 01:56.000 --> 01:58.000 yeah, there was a user controversy. 01:58.000 --> 02:03.000 Yeah, there was a laptop, let's wait for a few months until the device becomes up. 02:03.000 --> 02:06.000 Yeah, but that's about the development. 02:06.000 --> 02:10.000 That's how we start. That's how we make laptops work. 02:10.000 --> 02:13.000 But then it comes to the actual users. 02:13.000 --> 02:18.000 When the user, or maybe not the powerful user by the laptop from the store, 02:18.000 --> 02:21.000 and they want to install Libyan, Fedora, 02:21.000 --> 02:25.000 right-hat enterprise or some other Ubuntu, 02:25.000 --> 02:30.000 they want to take the existent image. 02:30.000 --> 02:35.000 They want to adjust the flash it to the thumb drive and install it. 02:35.000 --> 02:39.000 And then the next after the installation reboot, 02:39.000 --> 02:46.000 they laptop and also be happy with having the proper work in Linux, et cetera. 02:47.000 --> 02:52.000 So far so good, but how do we actually get from a CPI to the device 3? 02:52.000 --> 02:57.000 How do we get to the device 3 to the working Linux? 02:57.000 --> 03:01.000 So three major use cases, so turn the half. 03:01.000 --> 03:07.000 Normal, well, I'm sorry, something might be obvious to some of you. 03:07.000 --> 03:10.000 Please shout if, yeah, go on. 03:11.000 --> 03:14.000 Oh, this normal boot, when you have already everything installed, 03:14.000 --> 03:16.000 just copy it from your thumb drive. 03:16.000 --> 03:19.000 You need to specify the device 3 in the boot load appearance. 03:19.000 --> 03:21.000 Somehow. 03:21.000 --> 03:25.000 If it's a curable case, in some of these tools, 03:25.000 --> 03:29.000 grab decides, yeah, if it's a curable, if the machine is secured, 03:29.000 --> 03:31.000 let's skip all the device 3, we just ignore that command, 03:31.000 --> 03:32.000 it doesn't exist. 03:32.000 --> 03:34.000 And you cannot load anything. 03:34.000 --> 03:37.000 And the same applies to other boot loaders too. 03:37.000 --> 03:40.000 And obviously, the last case is installation. 03:40.000 --> 03:42.000 Well, you have a generic image. 03:42.000 --> 03:47.000 How do we check, how do we select the device 3 for it? 03:47.000 --> 03:51.000 So this needs to be somehow solved. 03:51.000 --> 03:54.000 And we try several attempts. 03:54.000 --> 03:57.000 Our colleagues also tried several approaches, 03:57.000 --> 03:59.000 and we would like to discuss them with you. 03:59.000 --> 04:03.000 And we would really like to bump start the, 04:03.000 --> 04:10.000 some kind of a process, and some kind of understanding how to proceed. 04:10.000 --> 04:15.000 So possible solutions that we followed through in our history. 04:15.000 --> 04:22.000 Use a CPI for the first boot of boot and delete a load. 04:22.000 --> 04:26.000 There was an original implementation by Rob Clark. 04:26.000 --> 04:30.000 An extra pre boot loader that's bumps in. 04:30.000 --> 04:33.000 Check the assemblies, check the DMI information, 04:33.000 --> 04:37.000 and loss the GTP from the, from the ESP. 04:37.000 --> 04:39.000 Yeah, nice, great. 04:39.000 --> 04:45.000 But major drawback is that it adds another step in the boot process. 04:45.000 --> 04:48.000 It doesn't work with the machine, because human codes, 04:48.000 --> 04:50.000 the name of the next boot loader, 04:50.000 --> 04:56.000 and Rob's implementation required very cryptic names of the device 3s. 04:56.000 --> 04:59.000 So, yeah, that works, but that's not so good. 04:59.000 --> 05:03.000 And as I said, it, because the boot loader name, 05:03.000 --> 05:06.000 you kind of really use that in a generic boot loader. 05:06.000 --> 05:08.000 Because, yeah, the boot loader name, 05:08.000 --> 05:10.000 you kind of really use that in a generic boot loader. 05:10.000 --> 05:11.000 Because, yeah, the boot loader. 05:11.000 --> 05:12.000 Yeah, the boot loader. 05:12.000 --> 05:13.000 Yeah, the boot loader. 05:13.000 --> 05:14.000 The boot loader. 05:14.000 --> 05:16.000 There was another implementation, 05:16.000 --> 05:19.000 or re-implementation of the same idea by Nikita Trafkin, 05:19.000 --> 05:23.000 another community called Komia developer. 05:23.000 --> 05:27.000 He rewrote that to be a UFA app. 05:27.000 --> 05:30.000 And, but to the major drawback of his approach, 05:30.000 --> 05:35.000 is that he encodes all the SMBIs information, 05:35.000 --> 05:40.000 all the hardware IDs into the binary. 05:40.000 --> 05:42.000 So, whenever we add a new laptop, 05:42.000 --> 05:44.000 we have to change the binary to, 05:44.000 --> 05:47.000 and you have to then assign it, or to do something else. 05:47.000 --> 05:49.000 So, the great thing, yeah, it works. 05:49.000 --> 05:52.000 These advantages, yeah, as I said, 05:52.000 --> 05:54.000 extra boot loader. 05:54.000 --> 05:56.000 It does not work with all the boot loaders. 05:56.000 --> 05:58.000 And it complicates it up. 05:58.000 --> 06:01.000 And it's unlikely to be included in any distributions as well. 06:01.000 --> 06:02.000 So, yeah. 06:02.000 --> 06:05.000 So, there is only one distribution, a postmarketer, 06:05.000 --> 06:07.000 which uses the DTB loader. 06:07.000 --> 06:09.000 So, thank you postmarketer. 06:09.000 --> 06:10.000 That's great. 06:10.000 --> 06:11.000 Thank you for your support. 06:11.000 --> 06:16.000 But, I don't think we can get that into one of major installs. 06:19.000 --> 06:21.000 So, there's some recent work in system D, 06:21.000 --> 06:24.000 system D boot with the UKI loading. 06:24.000 --> 06:27.000 So, basically, in there, you can have a UKI, 06:27.000 --> 06:29.000 that you load that contains all the DTBs, 06:29.000 --> 06:31.000 and there's a function in there, 06:31.000 --> 06:35.000 which allows you to actually put in the CHIDDTB mapping, 06:35.000 --> 06:38.000 and use the same module as DTB loader, 06:38.000 --> 06:43.000 but it allows you to kind of boot using system D. 06:43.000 --> 06:45.000 So, it's quite a nice way of doing it, 06:45.000 --> 06:47.000 because you can sign the UKI. 06:47.000 --> 06:50.000 You can update the DTB mapping later, 06:50.000 --> 06:53.000 so you don't have to, you can support new devices later on, 06:53.000 --> 06:54.000 if you like. 06:54.000 --> 06:59.000 But, this allows you to boot with UKI. 06:59.000 --> 07:03.000 There's no central repository yet for the CHIDM 07:03.000 --> 07:06.000 mappings, and also the UKI can become quite large, 07:06.000 --> 07:09.000 because each DTB is a separate section in the UKI. 07:09.000 --> 07:12.000 And also, this means that you need to use system D boot. 07:12.000 --> 07:14.000 Some distros, Debbie, and et cetera, 07:14.000 --> 07:15.000 she's grabbed. 07:15.000 --> 07:17.000 So, we're not quite there yet. 07:18.000 --> 07:20.000 And the only reason is that these are a bunch, 07:20.000 --> 07:22.000 which means these are really salty, 07:22.000 --> 07:25.000 because we support Christ and the others. 07:25.000 --> 07:26.000 Oh, really? 07:26.000 --> 07:27.000 Oh, really? 07:27.000 --> 07:28.000 Oh, nice. 07:28.000 --> 07:30.000 Currently, the implementation is under the work 07:30.000 --> 07:33.000 and tomorrow, it will be available in a few weeks 07:33.000 --> 07:34.000 in the last two weeks. 07:34.000 --> 07:35.000 Excellent. 07:35.000 --> 07:36.000 Yeah. 07:36.000 --> 07:37.000 Sure. 07:37.000 --> 07:40.000 So, there was a comment from... 07:40.000 --> 07:41.000 From Daniel. 07:41.000 --> 07:42.000 Oh, my name. 07:42.000 --> 07:43.000 From Grapp Martinez, 07:43.000 --> 07:46.000 that Grapp will support UKI soon. 07:46.000 --> 07:47.000 Thank you. 07:47.000 --> 07:48.000 And there was another hand here. 07:48.000 --> 07:49.000 Yeah. 07:49.000 --> 07:51.000 I just want to say, like, the UKI, 07:51.000 --> 07:53.000 when you can play large things, 07:53.000 --> 07:54.000 I don't know. 07:54.000 --> 07:56.000 This is my earlier talk. 07:56.000 --> 07:59.000 We have the same call, the EFI adults, 07:59.000 --> 08:00.000 with those things. 08:00.000 --> 08:02.000 Like, the EFI environments that look up in there, 08:02.000 --> 08:03.000 not as you go. 08:03.000 --> 08:05.000 And while it's not true, 08:05.000 --> 08:06.000 it's not true. 08:06.000 --> 08:07.000 I feel as far as, you know, 08:07.000 --> 08:10.000 because these people can have these adults 08:10.000 --> 08:11.000 who can have these adults who can have these adults, 08:11.000 --> 08:13.000 who can have these adults who can have these adults, 08:13.000 --> 08:15.000 who can have these adults who can have these adults. 08:16.000 --> 08:17.000 That makes a lot of sense. 08:17.000 --> 08:18.000 Yeah. 08:18.000 --> 08:19.000 Yeah. 08:19.000 --> 08:20.000 Yeah. 08:20.000 --> 08:21.000 Yeah. 08:21.000 --> 08:22.000 Yeah. 08:22.000 --> 08:23.000 And the worst thing, 08:23.000 --> 08:25.000 because we're in America, 08:25.000 --> 08:26.000 which means, yeah. 08:26.000 --> 08:27.000 Okay. 08:27.000 --> 08:28.000 So, there was a comment as well about, 08:28.000 --> 08:29.000 kind of UKI's, 08:29.000 --> 08:31.000 the adults you can have separate 08:31.000 --> 08:32.000 adults per manufacturer. 08:32.000 --> 08:33.000 That's a really good. 08:33.000 --> 08:34.000 Thanks. 08:34.000 --> 08:35.000 Yeah. 08:35.000 --> 08:36.000 But then it also doesn't help 08:36.000 --> 08:37.000 in the generic case. 08:37.000 --> 08:38.000 Well, if I know that, 08:38.000 --> 08:39.000 it's a welcome. 08:39.000 --> 08:40.000 Then it's a welcome. 08:40.000 --> 08:41.000 If I just want to, 08:41.000 --> 08:42.000 Libyan thumb drive, 08:42.000 --> 08:43.000 to vote on, 08:43.000 --> 08:44.000 to sign a media tech, 08:44.000 --> 08:46.000 and something else in Rochib, 08:46.000 --> 08:48.000 then that wouldn't really help. 08:48.000 --> 08:49.000 Yeah. 08:49.000 --> 08:50.000 Yeah. 08:50.000 --> 08:51.000 Yeah. 08:51.000 --> 08:52.000 Yeah. 08:52.000 --> 08:53.000 Sure. 08:57.000 --> 08:58.000 Yeah. 08:58.000 --> 09:00.000 So, the other option is obviously, 09:00.000 --> 09:03.000 so, the other option is UBoot. 09:03.000 --> 09:05.000 So, obviously, you can use UBoot to do this kind of thing. 09:05.000 --> 09:07.000 But we don't really need to explain 09:07.000 --> 09:08.000 that's possibly a bad idea. 09:08.000 --> 09:11.000 We can introduce loads of security bugs. 09:12.000 --> 09:14.000 So, we'd like to keep that out, 09:14.000 --> 09:15.000 ideally, if we can. 09:15.000 --> 09:17.000 And it will probably not end up going into any 09:17.000 --> 09:18.000 distros. 09:18.000 --> 09:19.000 So. 09:19.000 --> 09:20.000 Yeah. 09:20.000 --> 09:25.000 This is my second, 09:25.000 --> 09:28.000 if you use it a feedback from the mentors, 09:28.000 --> 09:30.000 I'm almost certain that you, 09:30.000 --> 09:32.000 if you use it a feedback from the mentors, 09:32.000 --> 09:33.000 I'm almost certain. 09:33.000 --> 09:34.000 Yeah. 09:34.000 --> 09:35.000 Yeah. 09:35.000 --> 09:36.000 Yeah. 09:36.000 --> 09:37.000 Well, thank you for, 09:37.000 --> 09:38.000 there was a comment that here. 09:38.000 --> 09:39.000 Please don't do that. 09:39.000 --> 09:41.000 I would like to spend really two words. 09:41.000 --> 09:45.000 So, why we thought that it might be a good idea. 09:45.000 --> 09:47.000 Well, first of all, because, yeah, 09:47.000 --> 09:48.000 it's loaded everywhere. 09:48.000 --> 09:50.000 It has loaded as a part of the boot process. 09:50.000 --> 09:52.000 It has loaded before all other boot loaders, 09:52.000 --> 09:53.000 like before system table, 09:53.000 --> 09:54.000 before grab, etc. 09:54.000 --> 09:57.000 So, that solves one of the problems with DTV loader. 09:57.000 --> 09:58.000 And then, 09:58.000 --> 09:59.000 just a second then. 09:59.000 --> 10:00.000 And then, 10:00.000 --> 10:02.000 it also has the code. 10:02.000 --> 10:04.000 So, that's the only place in the system, 10:04.000 --> 10:06.000 which actually has the code to verify 10:06.000 --> 10:09.000 PKCS7 without it to be defined. 10:09.000 --> 10:12.000 L-P files without any kind of problems. 10:12.000 --> 10:15.000 So, we really can't just sign the, 10:15.000 --> 10:23.000 just sign the DTV's on the ESP with PKCS7 as signatures. 10:23.000 --> 10:25.000 With the touch. 10:25.000 --> 10:27.000 Not trapped in anything, 10:27.000 --> 10:30.000 just put the touch signatures, 10:30.000 --> 10:31.000 the touch signatures, 10:31.000 --> 10:34.000 and then use a native code in Scheme, 10:34.000 --> 10:36.000 which will go through the system case, 10:36.000 --> 10:37.000 which will go through map, 10:37.000 --> 10:38.000 mock, k, etc. 10:38.000 --> 10:40.000 So, from the secure boot, 10:40.000 --> 10:42.000 from secure boot. 10:42.000 --> 10:44.000 Yeah, okay. 10:44.000 --> 10:46.000 So, that was, 10:46.000 --> 10:47.000 why, and yeah, 10:47.000 --> 10:49.000 it would just allow an easy integration 10:49.000 --> 10:51.000 into all the distros. 10:51.000 --> 10:52.000 Yeah. 10:52.000 --> 10:54.000 But yeah, there would be a problem 10:54.000 --> 10:55.000 getting that signed. 10:55.000 --> 10:56.000 Yes. 10:56.000 --> 11:01.000 Sorry. 11:01.000 --> 11:02.000 Yeah, by now. 11:02.000 --> 11:03.000 So, I mentioned that also, 11:03.000 --> 11:05.000 that's taken with those technical issues. 11:05.000 --> 11:06.000 Right? 11:06.000 --> 11:07.000 Yeah. 11:07.000 --> 11:09.000 You got your share in integration, but that's it. 11:09.000 --> 11:10.000 Oh. 11:10.000 --> 11:12.000 Well, I, who integrate? 11:12.000 --> 11:14.000 Like we see side profiles that I mentioned earlier, 11:14.000 --> 11:15.000 right? 11:15.000 --> 11:16.000 Yeah. 11:16.000 --> 11:17.000 Yeah. 11:17.000 --> 11:18.000 Yeah. 11:18.000 --> 11:19.000 Yeah. 11:19.000 --> 11:24.000 But the thing is that, 11:24.000 --> 11:26.000 it would be really nice to get, 11:26.000 --> 11:28.000 just get the touch signatures, 11:28.000 --> 11:30.000 because yeah, then you don't need any kind of weapon. 11:30.000 --> 11:31.000 Yeah. 11:31.000 --> 11:32.000 Yeah. 11:32.000 --> 11:33.000 Yeah. 11:33.000 --> 11:34.000 So, let's have the Linux binary, 11:34.000 --> 11:35.000 like VMZ, a VMLinals, or a image of dizzy, 11:35.000 --> 11:38.000 and I have DTVs, and I have signatures. 11:38.000 --> 11:41.000 So, that's, well, we can discover that later, really. 11:41.000 --> 11:44.000 So, now a small talk about distros. 11:44.000 --> 11:45.000 Yeah. 11:45.000 --> 11:46.000 So, in terms of the distros, 11:46.000 --> 11:48.000 so, Debbie uses a grab-based boot flow. 11:48.000 --> 11:50.000 I mean, I argue that we should move to system D boot. 11:50.000 --> 11:51.000 Others disagree. 11:51.000 --> 11:52.000 Yeah. 11:52.000 --> 11:53.000 Let's do it. 11:53.000 --> 11:54.000 Why not? 11:54.000 --> 11:55.000 Why not? 11:55.000 --> 11:57.000 Uh, guilty of the TLC. 11:57.000 --> 11:59.000 Well, let's talk about that later. 11:59.000 --> 12:01.000 We've got some custom images with system D boot, 12:01.000 --> 12:05.000 UKIs, kind of we ship all of the DTVs, 12:05.000 --> 12:07.000 and all of the CHID mapping in there, 12:07.000 --> 12:09.000 and it seems to work really well. 12:09.000 --> 12:14.000 For Dora, they don't really build an images for ARM64. 12:14.000 --> 12:17.000 These call come-lapsops because this exact issue. 12:17.000 --> 12:20.000 There's some arch images with system D boot, 12:20.000 --> 12:21.000 UKIs as well. 12:21.000 --> 12:23.000 They're the ones who've been adding all the actual 12:23.000 --> 12:27.000 implementation system D boot for the CHID mapping and everything. 12:27.000 --> 12:30.000 There's some concept images for a bunch too, 12:30.000 --> 12:33.000 but they use a grab-script system in which DTVs are load. 12:33.000 --> 12:36.000 So, I mean, it's kind of not very generic. 12:36.000 --> 12:39.000 And as we mentioned before, post-market OS. 12:39.000 --> 12:43.000 The trailblazer images use DTV loader to load the DTV. 12:43.000 --> 12:44.000 I'm not sure of any others. 12:44.000 --> 12:49.000 If anyone has any other images or distributions that 12:49.000 --> 12:51.000 I'd be interested to hear more. 12:51.000 --> 12:52.000 See if anyone else. 12:52.000 --> 12:52.820 Yeah? 12:52.820 --> 12:54.820 Yeah? 12:54.820 --> 12:56.820 It's ARM code, ARM code, ARM code? 12:56.820 --> 12:57.420 Yeah? 12:57.440 --> 12:58.440 ARM code! 12:58.440 --> 12:59.720 ARM code is ARM code. 12:59.720 --> 13:01.720 ARM code, ARM code. 13:02.920 --> 13:03.440 ARM code. 13:03.440 --> 13:05.440 ARM code. 13:06.740 --> 13:07.280 ARM code. 13:08.400 --> 13:08.900 ARM code. 13:10.100 --> 13:10.680 ARM code. 13:11.040 --> 13:12.120 ARM code. 13:14.140 --> 13:15.140 ARM code. 13:15.140 --> 13:16.140 ARM code. 13:16.200 --> 13:17.140 ARM code. 13:17.140 --> 13:21.140 It's the only laptop, how do you work on any other laptops? 13:21.140 --> 13:24.140 Okay, yeah, nice. 13:29.140 --> 13:32.140 Any other these tools, any comments? 13:32.140 --> 13:37.140 Again, thank you for the post-market rest, because they do a really great job on enabling stuff 13:37.140 --> 13:42.140 and thank you for all these tools, because all of you do a really great job on helping us 13:42.140 --> 13:49.140 or making our life easier and harder to enable the, to enable laptops. 13:51.140 --> 13:57.140 So yeah, the next steps really, we want to help the fedora and the Debbie and Images to kind of become 13:57.140 --> 13:59.140 mainline really for these laptops. 13:59.140 --> 14:04.140 We want to make sure that we do it in the right way, so we want to include vendors, 14:04.140 --> 14:10.140 laptops, vendors, distro, people, mainstayners, anyone interested, we'd like to form some sort of working group. 14:10.140 --> 14:14.140 I don't know how really that works, if anyone's got any ideas, I'd love to hear it. 14:14.140 --> 14:18.140 And we want to decide on a common solution. 14:18.140 --> 14:22.140 I mean, my favourite solution is UK-I's, Dimitri's favourite solution is the 14:22.140 --> 14:24.140 Shim idea. 14:24.140 --> 14:25.140 Yeah, sure. 14:25.140 --> 14:27.140 So, I'd need to be a larger one. 14:27.140 --> 14:28.140 Yeah. 14:28.140 --> 14:35.140 And it's a shame, because I mean, we're hoping to use this as a step-in-stone to get systemD boot into Debbie and so. 14:36.140 --> 14:40.140 I think Debbie and support systemD boot, so you can do it by default, by default. 14:40.140 --> 14:41.140 Oh, that one. 14:41.140 --> 14:43.140 What if I give it five years? 14:43.140 --> 14:45.140 I'm going to take it to my deck. 14:45.140 --> 14:48.140 Yeah, I mean, I have Debbie and on this laptop, but I like it about it. 14:48.140 --> 14:50.140 Yeah, sometimes it takes a lot of time. 14:50.140 --> 14:52.140 So, any other opinions, any other comments? 14:52.140 --> 14:53.140 Please, we're really. 14:53.140 --> 14:54.140 Yeah. 14:54.140 --> 14:56.140 I think there is, like, about the big size of this, 14:56.140 --> 15:02.140 like, let's say, we're in the world where, like, we're, like, 15:02.140 --> 15:06.140 how am I going to get it by the way I can talking, like, if you have a generic image, 15:06.140 --> 15:10.140 like, how am I going to migrate, like, blocks, and how large is it going to be. 15:10.140 --> 15:12.140 So, I'm going to do support systemD boot. 15:12.140 --> 15:14.140 Because this doesn't look interesting. 15:14.140 --> 15:15.140 Yeah. 15:15.140 --> 15:16.140 Yeah. 15:16.140 --> 15:18.140 I think I just have to move to those who are secondary booting, 15:18.140 --> 15:19.140 and say, like, I can shift. 15:19.140 --> 15:20.140 Right. 15:20.140 --> 15:22.140 But eventually, each other's secondary boot gets slow. 15:22.140 --> 15:24.140 If you pause, because I said, you know, actually going to use, 15:24.140 --> 15:25.140 as we would, right? 15:25.140 --> 15:27.140 And this is the implications that we can use. 15:27.140 --> 15:29.140 If you need to, we have this in separate files, 15:29.140 --> 15:32.140 and you can load them, and this gets separately. 15:32.140 --> 15:35.140 Or if it's fine to actually just have it in one UKI, 15:35.140 --> 15:37.140 but that would, of course, go. 15:37.140 --> 15:39.140 So, yeah, my question is, what's with it? 15:39.140 --> 15:41.140 And you saw about, like, because we've, 15:41.140 --> 15:43.140 we've had it on one structure of data. 15:43.140 --> 15:44.140 Yeah. 15:44.140 --> 15:45.140 Yeah. 15:45.140 --> 15:46.140 There's so many information. 15:46.140 --> 15:47.140 How do you understand this? 15:47.140 --> 15:48.140 Yeah. 15:48.140 --> 15:49.140 Yeah. 15:49.140 --> 15:50.140 Not particularly. 15:50.140 --> 15:52.140 So, the question was, basically. 15:52.140 --> 15:54.140 Oh, sorry. 15:54.140 --> 15:56.140 The question was around the size of these things. 15:56.140 --> 15:59.140 How big is it going to make the UKIs? 15:59.140 --> 16:02.140 So, I don't know if you got any questions. 16:02.140 --> 16:07.140 So, I just checked the size of, oh, welcome. 16:07.140 --> 16:08.140 Detabies. 16:08.140 --> 16:12.140 At this point is 55, 56 megs. 16:12.140 --> 16:16.140 And I think, when I last checked the size of, 16:16.140 --> 16:17.140 I don't know. 16:17.140 --> 16:18.140 I don't know. 16:18.140 --> 16:19.140 I don't know. 16:19.140 --> 16:20.140 I don't know. 16:20.140 --> 16:21.140 I don't know. 16:21.140 --> 16:22.140 I don't know. 16:22.140 --> 16:24.140 I don't know. 16:24.140 --> 16:25.140 I don't know. 16:25.140 --> 16:26.140 I don't know. 16:26.140 --> 16:27.140 I don't know. 16:27.140 --> 16:28.140 I don't know. 16:28.140 --> 16:29.140 I don't know. 16:29.140 --> 16:30.140 I don't know. 16:30.140 --> 16:31.140 I don't know. 16:31.140 --> 16:32.140 I don't know. 16:32.140 --> 16:33.140 I don't know. 16:33.140 --> 16:34.140 I don't know. 16:34.140 --> 16:35.140 I don't know. 16:35.140 --> 16:36.140 I don't know. 16:36.140 --> 16:37.140 I don't know. 16:37.140 --> 16:38.140 I don't know. 16:38.140 --> 16:39.140 I don't know. 16:39.140 --> 16:40.140 I don't know. 16:40.140 --> 16:41.140 I don't know. 16:41.140 --> 16:42.140 I don't know. 16:42.140 --> 16:43.140 I don't know. 16:43.140 --> 16:45.140 I don't know.