Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Because u-boot can't actually interact with the flash once it's booted you need to write u-boot to it from linux. With a mainline kernel you need to enable the SPI NOR drivers in the kernel config and add a DT node something like this:
so we could have u-boot run from the inbuilt flash and boot freely from other media than the mmc card - and have said slot free for hot-plug and all things nice?
so we could have u-boot run from the inbuilt flash and boot freely from other media than the mmc card - and have said slot free for hot-plug and all things nice?
These options don't exist in 4.19.20 (or if they do, they aren't showing up). I wouldn't object to adding them for anybody else who wants to do it, although I have one "Pi"s that doesn't have onboard flash so it'd never be what I document as a suggested option.
Also, you still have to boot the thing in the first place - which presents a chicken-egg problem. I can't document what I don't know about - I don't know about any arbitrary version of u-boot that happens to be on any device. However, I do know that you can write a known version u-boot to an SD Card and have an environment in which you can follow a set of instructions and get Slackware going.
These options don't exist in 4.19.20 (or if they do, they aren't showing up). I wouldn't object to adding them for anybody else who wants to do it, although I have one "Pi"s that doesn't have onboard flash so it'd never be what I document as a suggested option.
Also, you still have to boot the thing in the first place - which presents a chicken-egg problem. I can't document what I don't know about - I don't know about any arbitrary version of u-boot that happens to be on any device. However, I do know that you can write a known version u-boot to an SD Card and have an environment in which you can follow a set of instructions and get Slackware going.
1. the kernel configuration has grown to a mess - i used grep on the .config to confirm and used search on the nconfig to get around:
- one of the three is set already, the other two are "all over the place", so one would to resort to search in order to find them
2. good point - self brewing a custom u-boot is less of a nuisance to a casual hacker than maintaining too many options - let's disregard onboard u-boot then.
on another note;
3. could you please include (hard-coded please) the tiny 4x6 font in the lib section, so i would not need to run off an custom kernel when using ridiculously tiny screens, and i will pay off with cute photos of them (1.8" SPI TFT @128x160)?
1. the kernel configuration has grown to a mess - i used grep on the .config to confirm and used search on the nconfig to get around:
- one of the three is set already, the other two are "all over the place", so one would to resort to search in order to find them
Which config file are you using? It doesn't look like it's the one in -current.
on another note;
3. could you please include (hard-coded please) the tiny 4x6 font in the lib section, so i would not need to run off an custom kernel when using ridiculously tiny screens, and i will pay off with cute photos of them (1.8" SPI TFT @128x160)?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.