----- On Aug 3, 2019, at 10:47 AM, Pavel Machek pavel@xxxxxx wrote: > Hi! > >> > What is status of OLPC-1.75 in v5.3? IIRC most of the patches went in, >> > but I don't see suitable dts file in the tree. I tried porting one >> > from working (4.19 or so) kernel, but it was not quite trivial. >> > >> > Is there time for dts to be merged? >> >> Short answer is that it's not absolutely necessary. With a new enough >> OpenFirmware, the firmware will just construct a correct FDT. > >> To upgrade your machine to the new firmware, just copy >> http://dev.laptop.org/~quozl/q4e00ja.rom to a FAT partition on a USB >> flash stick and run "flash u:\q4e00ja.rom" from the "ok" prompt. >> Then you'll be able to run stock mainline kernels happily. > > Aha, good, thanks. That went smoothly. > >> That said, it might still be useful to have a DTS file in tree (for >> reference, testing, machines with older firmware, etc.). I've now re- >> sent the MMP2 devicetree update patch set with the DTS file included >> and copied you on that one. > > Yes: sometimes it is neccessary to modify the dts. I was changing the > kernel command line, for example. Well, you can do that from OFW too. E.g.: " console=ttyS2,115200" to boot-file >> As usual, I'm thankful for testing, reviews and acks. > > I'll take a look. I tried 5.2 with defconfig from one of the branches > (olpc_xo175_defconfig), and that does not boot. I'm using [1]. [1] https://raw.githubusercontent.com/hackerspace/olpc-xo175-linux/lr/olpc-xo175/arch/arm/configs/olpc_xo175_defconfig I'm wondering if it would make sense to include this upstream? My guess was that nowadays multi_v7_defconfig that just works on any DT-based platform is preferred to machine specific ones. However, this one would enable OLPC-specific drivers the multi_v7_defconfig defconfig wouldn't. I've sent out an update to multi_v7_defconfig [2]. Once it is applied, it should work on the XO-1.75 (without fancy things like camera or power button). [2] https://lore.kernel.org/lkml/20190620114816.1387881-1-lkundrak@xxxxx/ > What config should I use? Is it enough to produce zImage and put it on > the flashdisk with olpc.fth file? Yes. OFW loads olpc.fth from the first active FAT or ext3 partition on SD card or a USB flash drive. If you put the zImage in the same place, the following script would work: \ OLPC boot script " last:\zImage" to boot-device visible unfreeze boot Note that it has to start with a backslash. The "visible" and "unfreeze" words enable the DCON pass-through mode. You would see the XO logo instead of the actual screen output without it. > Is there some kind of documentation somewhere? :-). This is always a tough question. Short answer would be no. I'm happy to answer questions though, if the above wouldn't be sufficient to make the thing boot for you. I'd prefer if things just worked to documenting how to hack things to make them work. If you got a Fedora machine, you can already just pick a nightly [1] armhfp image and install it with fedora-arm-installer the same way as any other ARM machine. I hope to make Debian work too. An image that already boots would then hopefully be a good start for whoever wishes to run their own kernels. That's my excuse for not documenting things... [1] https://www.happyassassin.net/nightlies.html > Thanks and best regards, > Pavel Take care Lubo > -- > (english) http://www.livejournal.com/~pavelmachek > (cesky, pictures) > http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
