[Bug 1205359] New: Modprobing spidev on a Raspberry Pi does not create "/dev/spidev*.*".
http://bugzilla.opensuse.org/show_bug.cgi?id=1205359 Bug ID: 1205359 Summary: Modprobing spidev on a Raspberry Pi does not create "/dev/spidev*.*". Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: expeehaa@outlook.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- On my Raspberry Pi with MicroOS I want to use a library that requires "/dev/spidev*.*" devices, but when following the guide at https://en.opensuse.org/openSUSE:SPI, none show up, even though the spidev Kernel module is successfully loaded. I���ve obtained the same result with a regular Tumbleweed image, as well as Leap 15.3 and 15.4. On Raspbian on the other hand, it works as expect, but apparently only due to a patch for the spidev source in its kernel: https://github.com/raspberrypi/linux/commit/ea85fb22e836d6457bf69665e65fe60c... Using the patch I compiled spidev out-of-tree and got the expected "/dev/spidev0.0" and "/dev/spidev0.1" devices upon modprobing. I have no clue if this is acceptable or if there is a better (easier?) solution, but it would be nice if the patch could be included in kernel-default (at least in Tumbleweed, maybe even in Leap). -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205359 http://bugzilla.opensuse.org/show_bug.cgi?id=1205359#c1 Michal Suchanek <msuchanek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek@suse.com --- Comment #1 from Michal Suchanek <msuchanek@suse.com> --- You should be able to bind the driver by hand even if there is no match. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Docu... -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205359 http://bugzilla.opensuse.org/show_bug.cgi?id=1205359#c2 --- Comment #2 from M�ller <expeehaa@outlook.com> --- Thanks for that link, that pretty much explains why the Raspbian kernel patch exists. I only found some other docs that weren't as helpful. Since the Raspbian kernel devs seem to think that the patch is the best solution (see https://github.com/raspberrypi/linux/issues/1054), I don't think asking them (or even just me trying) to find a better solution acceptable for the upstream kernel is feasible. For now, I think I'll keep using my patched spidev module package and maybe I'll document the issue on the openSUSE:SPI wiki page. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205359 http://bugzilla.opensuse.org/show_bug.cgi?id=1205359#c3 --- Comment #3 from Ivan Ivanov <ivan.ivanov@suse.com> --- (In reply to M�ller from comment #2)
For now, I think I'll keep using my patched spidev module package
Not sure why you need this, because instructions that you have added to the Wiki are working just fine without need to patch kernel module.
and maybe I'll document the issue on the openSUSE:SPI wiki page.
Thanks for this! -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com