Latest kernel 4.1 supports MPLS datapath.
IpRoute2 is also adding commands to add mpls routes in kernel.
What are the iproutes command to create FTN(Fec to NHLFE), ILM(Incoming Label Map) and NHLFE(Next hop label forwarding entry) ?
What are the commands to see above tables ?
Thanks in advance.
Related
I have installed LB for IPV4 on centos 6.9, dsserver starts successfully but when I start executor it gives me below error.
Error : kernel was not loaded (Error_Loading)
I know that it is deprecated and support will end in September, but for now I have to make this working. Any suggestions will be helpfull.
Below is the snap of the server.log file.
First of all you are using unsupported OS. Second LB for IPV4 has strong dependency on the kernel level.
You didn't specify the version you are using. From the log it looks like you are using 8.0.0.0. You should never use initial version. Please update to the latest fixpack.
I'd strongly suggest to use LB for IPv4 and IPv6 version, if possible, it is much less kernel dependent.
I have pcspkr in blacklisted in /etc/modprobe.d/pcspkr.conf. However, I can manually load the module using modprobe.
I'm guessing, some other component will be able to do the same via module alias mechanism. Is there a way to permanently block automatic loading of a specific kernel module?
My use case is that I want to experiment with an alternative driver than the one provided in-tree. For this, I do not want the system's default driver showing up. I do not want to delete the golden driver provided by the kernel and screw up either.
What options do I have ?
I'd like to generate a fixed device table in my embedded Linux image and skip using udev.
Following the Yocto Dev Manual, chapter* 5.18.1*, I've set the 2 variables USE_DEVFS="0" and IMAGE_DEVICE_TABLES = "device_table-mymachine.txt" and removed udev from the variable VIRTUAL-RUNTIME_dev_manager.
But the table was not created and I still need udev to populate devices.
Does anyone have an idea?
I am not sure how you have defined device_table-mymachine.txt but this is device_table-minimal.txt for example.
Secondly, without udev, you need to add another device manager such as BusyBox's mdev by specifying it in your conf/local.conf file as follow:
VIRTUAL_RUNTIME_dev_manager = "mdev"
Note that this will work only with core images that include packagegroup-core-boot
I want to write a test driver for mcspi and want to give all configuration in my driver file (instead of using user space application I want to use driver as a test driver and want to create .ko) and want to pass all configuration to the mcspi controller.
The configurations like chip_select, mode, speed, bits etc., Basically all these configurations I want to use for my test driver to check functionality of FIFO mode in the mcspi. I have already enabled FIFO in the mcspi but I want to check its functionality.
Can anyone please give me some suggestions?
I don't really know why cant you do something you want. I think you can pass the configuration by set up parameters using module_param
Adding on what #sunnyleevip suggested: another "standard" way to configure your driver would be to expose the params of interest via the /proc or the /sys filesystems.
You can find all the details in Linux Device Driver
Expanding on #sergico and #sunnyleevip, you could also use device tree to pass configuration data to the driver. The SPI bus master driver (since the 2.6.30s and all of the 3.x kernels) already are pretty devicetree supportive, so there might not be much more to do to get it to work.
Is there any uboot config option to print boot sequence with time prefixes similar to kernel option CONFIG_PRINTK?
I am expecting output like below,
[ 0.000000] U-Boot 1.1.4-gedeced79 (Feb 6 2012 - 09:27:11)
[ 0.011300] Starting kernel ...
[ 0.015686] Uncompressing Linux... done, booting the kernel
define DEBUG config option is best for your purpose, it is picked up by all u-boot code after you put it in your include/configs/myboard.h. (each config option is '#define', but that is doing strange things in my page preview)
Also
define CONFIG_BOOTSTAGE.
You can look at README for this, code is in common/bootstage.c, its functions do some of what you want. You may have to add a function show_boot_progress() in your BSP, for these functions to be used. With those in place, I believe there are already hooks in infrastructure code for them to get called, but I haven't used this option.
I am not aware of U-Boot config option that does such thing, but there are some other techniques which enables you to do it. I.e. config option inside the Linux kernel.
Take a look at: Measuring Boot-up time