• kboy101222@sh.itjust.worksEnglish
        0·
        3 months ago

        True, true. I have a vague idea how embedded systems work. I have no idea how you even get started with driver development.

        OS development isn’t terrible though. There are numerous books to help you make your own kernel and OS

        • cmder@lemmy.world
          0·
          3 months ago

          For linux driver development you can start by reading “Linux Device Drivers, Third Edition” pdf.
          It is free and give you an idea about how everything works.
          The real learning is by reading and using the linux kernel api doc or directly the source code of the api you want to call.
          Source : i did this for a school project where i had to implement multiple kernel modules.

          • merc@sh.itjust.works
            0·
            3 months ago

            I think the real issue with driver development is that almost nobody ever has a reason to do it. It’s a much more constrained way of programming compared to normal programs, and isn’t necessary unless you need to talk to hardware or something. So, nobody has an excuse to learn it.

              • merc@sh.itjust.works
                1·
                3 months ago

                Yes… as I said. But, most people use hardware provided by other people, which means other people write the drivers.

                • SpaceNoodle@lemmy.world
                  1·
                  3 months ago

                  Yes, and those people are people.

                  Also, sometimes the drivers are total garbage, and other people have to rewrite the garbage from the first people.

                  Also also, sometimes there is no driver.