2011/2/28 Sławomir Cygan <[email protected]>: > 2011/2/28 Madhavi Manchala <[email protected]>: >> 2011/2/27 Sławomir Cygan <[email protected]>: >>> On Sun, Feb 27, 2011 at 2:04 PM, Florian Fainelli <[email protected]> >>> wrote: >>>> Hello, >>>> >>>> On Sunday 27 February 2011 13:12:03 Madhavi Manchala wrote: >>>>> Dear All, >>>>> >>>>> Where can I find the HAL (Hardware Abstraction Layer) code in the >>>>> OpenWRT sources? I checked out the trunk through svn. I need to change >>>>> the RAM, FLASH, UART and MCU details in the HAL code in order to >>>>> support our device. >>>> >>>> You have not mentionned which target you are talking about, which one are >>>> working on? >>>> -- >>>> Florian >>>> _______________________________________________ >>>> openwrt-devel mailing list >>>> [email protected] >>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel >>>> >>> >>> Usually code for "platform devices" initialization is placed in >>> patches and files in apropriate target directory. >>> >>> For example for devices with Ralink RT3050 target is "ramips" and >>> target directory is trunk/target/linux/ramips/. >>> Platform devices are configured by board-specific code in >>> trunk/target/linux/ramips/files/arch/mips/ralink/rt305x/mach-* files, >>> than initialised in >>> trunk/target/linux/ramips/files/arch/mips/ralink/rt305x/devices.c >>> Early serial and ram in >>> trunk/target/linux/ramips/files/arch/mips/ralink/rt305x/setup.c >>> >>> All files from trunk/target/linux/ramips/files are added to lnx >>> kernel, than patches from trunk/target/linux/ramips/patches-[kernel >>> version] are applied - theese the files you should concentrate on, >>> when booting new device. >>> >>> Lnx kernels does not offer HAL, but instead features like platform >>> devices are avaliable >> >> Dear Swalomir Cygan, >> >> Thanks for your useful important information. However, here are my findings. >> >> We are planning to build the OpenWRT to our custom board which is >> based on Samsung S3C2510A processor. This is not available under >> trunk/target/linux/ directory. However, there is a directory, named >> s3c24xx, which is based on Samsung S3C24xx processor. So, what is the >> procedure for porting the OpenWRT to my board which is based on the >> Samsung s3c2510A processor? >> >> Further information, I extracted the linux-2.6.30-10.tar.bz2 directory >> from dl (downloads) directory of the OpenWRT sources. After extracting >> also, I did not find any mach- directory which is based on S3C25XX. >> Even, I did not find anything about S3C25xx in the latest stable >> kernel 2.6.37 also. Then, how can I proceed further for porting the >> OpenWRT to my Samsung S3C2510A processor. >> >> Please suggest me. >> >> Thanks and Regards, >> Madhavi M. >> >>> >>> >>> -- >>> Pozdrawiam, >>> Sławomir Cygan >>> >> > > Do you have any working linux kernel for this board? If so, create new > OpenWrt target, make diffs for this kernel against vanilla kernel and > put them in the new target patches. Also You would have to create a > Makefile for image generation and at least one target profile. > > If You don't have any linux kernel, nor Samsung provided one, you must > start from the beginning and port vanilla kernel patched witch > target/generic/patches-[version] patches ;) You can use OpenWrt for > this as a tool for this (toolchain generation, image generation..), it > is still a lot of work in front of You.
Dear Slawomir Cygan, Thanks for the information. However, we do not have any working linux kernel for this board. So, the first option is not suitable for me. The samsung doesn't provide any linux kernel code. However, it provided us HAL initialization code for initializing the board. This is not for the Linux. Then, I need to do the following for porting OpenWRT on to my board. 1) I need to develop the architecture files which resides under arch/arm of the trunk/target/linux/board directory from beginning. Along with this, I need to add some configuration files and makefiles for this. 2) Then, I need to develop the drivers for my board for the peripherals, which are present on my board, as some patches. The patches are available at trunk/target/linux/generic directory of the OpenWRT sources. 3) Then building the OpenWRT images and loading them on to my board. Please let me know, whether my understanding is correct or not. I am new to this environment. So, please suggest. Thanks and Regards, Madhavi M. > > -- > Pozdrawiam, > Sławomir Cygan > _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-users
