Can't find device node in /dev/ directory!
Hi, I added some drivers in l4linux, of course, I assigned the corresponding peripheral resources (iomem, irq) to these drivers. From the driver's output log, it seems that they all work well, but when entering the command line, I could not find any relevant device node in /dev/ directory. To my confusion, I can see these devices info in /sys/ directory. The command line args is showing below: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd ramdisk_size=4000 Any idea?
On 10/27/2016 04:29 PM, li94575 wrote:
Hi, I added some drivers in l4linux, of course, I assigned the corresponding peripheral resources (iomem, irq) to these drivers. From the driver's output log, it seems that they all work well, but when entering the command line, I could not find any relevant device node in /dev/ directory. To my confusion, I can see these devices info in /sys/ directory. The command line args is showing below: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd ramdisk_size=4000 Any idea?
Do you have devtmpfs configured in your L4Linux kernel? Did you ran udev or mdev to populate /dev? Best, Matthias.
At 2016-10-27 22:33:01, "Matthias Lange" <matthias.lange@kernkonzept.com> wrote:
On 10/27/2016 04:29 PM, li94575 wrote:
Hi, I added some drivers in l4linux, of course, I assigned the corresponding peripheral resources (iomem, irq) to these drivers. From the driver's output log, it seems that they all work well, but when entering the command line, I could not find any relevant device node in /dev/ directory. To my confusion, I can see these devices info in /sys/ directory. The command line args is showing below: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd ramdisk_size=4000 Any idea?
Do you have devtmpfs configured in your L4Linux kernel? Did you ran udev or mdev to populate /dev? Thank you very much for your reply!It seems not to help, after configuring devtmpfs in l4linux kernel. I have selected the following two options.make menuconfig-->Device Drivers-->Generic Driver Options -->Maintain a devtmpfs filesystem to mount at /dev -->Automount devtmpfs at /dev, after the kernel mounted the rootfsNow I can only see these device nodes in dev/ directory:And could you tell me how to run udev or mdev?
Hello
And could you tell me how to run udev or mdev?
This is quite useful: http://free-electrons.com/doc/mdev-lab.pdf Good luck.
At 2016-10-29 00:28:30, g4@novadsp.com wrote:
Hello
And could you tell me how to run udev or mdev?
This is quite useful: http://free-electrons.com/doc/mdev-lab.pdf
Thank you! After adding "mdev -s" in file /etc/init.d/rcS, I can find device nodes in /dev/ directory
Hi L4-Hackers, is it possible to link a single task to a specific memory region? Because, I have a platform with a secure DRAM. But the secure DRAM is small, and the complete design with all the tasks won't fit. So, I'd like to link only one task to the secure DRAM, and all the others to the ordinary DRAM. Is this possible, or is there to much dynamic allocation? Have a nice day, ba_f
Hi, On Mon Mar 20, 2017 at 14:33:17 +0100, ba_f wrote:
is it possible to link a single task to a specific memory region?
Because, I have a platform with a secure DRAM. But the secure DRAM is small, and the complete design with all the tasks won't fit. So, I'd like to link only one task to the secure DRAM, and all the others to the ordinary DRAM.
Is this possible, or is there to much dynamic allocation?
Linking a program to a specific location is well possible. However, the extra memory region is not part of the normal RAM but an extra piece of memory? How is it accessed? And how big is it? Adam
participants (5)
-
Adam Lackorzynski -
ba_f -
g4＠novadsp.com -
li94575 -
Matthias Lange