RE: [Ltib] Request to explain how the platform specific drivers can be loaded into the rootfs

[Zahidul Haque]

Hi Malay,

If everything is set up properly, then run the command :./ltib -m config". This 
command will let you configure for the platform you want to chose(Only for the 
first time). It will also prompt you options such as Toolchain selection, 
Choose your bootloader , Choose your Kernel.

Select the option"[ ] Configure the kernel" as Y. Save the configuration.
Run ./ltib

This command will extract the kernel in ltib/rpm/BUILD/linux-2.6-x.x and prompt 
to configure the kernel. Here you can chose yours  platform specific drivers 
and save the configuration. The built in driver will be part of kernel image 
such( zImage/uImage)

Thanks & Regards
Zahidul Haque,
____________________
From: address@hidden address@hidden On Behalf Of malay jajodia address@hidden
Sent: Thursday, August 12, 2010 10:10 PM
To: address@hidden
Subject: [Ltib] Request to explain how the platform specific drivers can be 
loaded into the rootfs

Hi,

I have started using LTIB for my PHY3250 board and have a question that has 
probably been answered many times but still gives me some doubts. If possible 
please let me know the steps required to load a platform specific driver into 
rootfs. Also i need to make an application program to test with my driver. I 
have read many related documents but still i am confused on how i can achieve 
both tasks, so please elaborate it with your reply.

Thanks a lot in advance.

--
Malay Jajodia
Email: address@hidden<mailto:address@hidden>

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."