I will be porting a video decode driver and am trying to figure out if the driver that I am porting is compatible with the linux kernel I am porting it into. How do I figure this out?
I am trying to port a driver similar to this one:
https://github.com/Xilinx/vcu-ctrl-sw
Related
i have already compile the linux kernel with arm compiler for beaglebone black.comile the uboot. and also filesystem debian. Now i want to run my compiled linux kernel on beaglebone. how can i do it?which image file has to be port? and how? using sd card or using usb to serial ttl connector? please help me descriptively.thank you
This excellent page created by Robert C. Nelson, who also maintains the official images for Beagleboard, covers it in great descriptive detail, #exactsteps even.
I am trying to test a particular driver.
Would like to simulate KZALLOC() to fail and verify my driver is working fine.
Can anyone recommend a suitable Kernel Configraiton that helps me with this?
I am using 3.10 as well as 3.4 Linux Kernels please/
I could successfully implement POSIX Message Queue on Ubuntu 10.04 (Kernel version 2.6.38).
But the code fails when (built and) run on same version of Ubuntu 10.04 (Kernel version 2.6.37) on ARM Processor (Thin client devices like HP T410).
The failure happens to use any of the Message Queue functions (e.g. mq_open, unlink_message_queue()) :
OSError: [Errno 38] Function not implemented
Online information shows that. POSIX MQ is supported from Linux Kernel version 2.6.6.
This is very confusing to me (being new to linux world).
How come the functionality works on a x86 Linux Kernel 2.6.38 , but does not work on Kernel 2.6.37 running on ARM processor. And the document gives a different Version information 2.6.6 about the support.
Is there a better way to verify if the Current OS has the support or not ?
Is it possible the Kernel is trimmed off on Thin client devices.
Yesterday I faced with an interview. In interview he asked me for steps to porting Linux on new board.
My answer was,
cross-compile u-boot for board architecture.
cross-compile kernel, with selecting driver for peripherals connected to board.
cross-compile filesystem, and port all on board.
But Interviewer is not happy with this answer.
Can you please suggest me which point were I missed out?
Thanks in advance.
Porting steps -
Install a cross-development environment.
Setup the board and ensure that the serial port is working so we can print data through the serial port.
Download and install the Linux kernel, most of the porting work will be done at this level.
Add board specific code into the kernel tree.
Build a kernel image to run on the board
Test that early kernel printk is working
Get the real printk working with the serial console.
For a new board, a new board-specific directory should be added as well as support for interrupt handling, kernel timer services and mapping for memory areas.
Ethernet drivers are usually the next drivers to focus on as they enable setup of NFS root file system to get access to user utilities and applications.
Filesystem can be provided in different forms which are listed on LinuxFilesystem
Has anyone tried to compile Intel xf86_video_intel for another OS. This code is written for Linux. I am wondering if there is any experience with porting the code to another operating system? The code is located at:
http://intellinuxgraphics.org/documentation.html
Thanks,
FM
The latest Intel Linux graphics drivers are very dependent of features of the linux kernel (kernel mode setting being one of the most talked about recently). Porting the driver may not be a trivial, if possible, task.
Usually Linux graphic code is written for the X server. X is available for many different platforms / OS'es. For more information see (http://www.x.org/wiki/).