Heecheol, Here is a thorough porting guide for Tizen: https://wiki.tizen.org/wiki/Porting_Guide
thanks - jf.ding On Friday, October 10, 2014 at 8:45 AM, heecheol.yang wrote: > > Hello, > > This mail is about general approach to port a certain os stack(e.g. tizen) on > certain platform and I am wondering wherther it is appropriate to > characteristics of this mailing list and if not, I apologize to all of you ( > and you don't have to read this mail :) ) > > Anyway, In summary, my question is that do you usually start porting work > from already-built image like tizen-common.img on tizen snapshots web page or > by writing kick starter file and building the image? > > To be specifice, I hope some of you might remember my previous mail that I > stopped to port tizen on odroid xu board due to old version of SMACM issue. > Yes, I am almost doing nothing on this work these days but there was a little > bit of progress thanks to so much advices; I succeeded in back porting recent > version of SMACK on kernel 3.4 which my board is currently supporting. > > And the problem which I am struggling is hanging problem on boot sequence and > it seems that it is related to device driver and udev. BUT this mail is NOT > about asking the solution. > > As having been solving some problems that I've faced during porting work, now > I can't certain whether I am approaching correctly. > > Currently, I downloaded tizen-common image file and overwrote it to sd card > and booted it on my board. Surely,there are a lot of errors, and I am solving > them one by one. > > But when I faced the device driver issues, I thought that something goes > wrong. As you know, the image might be for the certain target board, and it > also might be very different from my board. Some parameters may be controlled > and arranged but other parts, especially device drivers, should be touched > from the clear and new state; If I do porting by modifying a built image, it > would be more difficult to dealing with these issues. > > Therefore, I am considering getting rootfs repository and the kick starter > file, analyzing and modifying them for my board instead of using > already-built image. > > So I want to ask you what is your preferred approach to port a os stack on a > new platform. Do you like to do like whar I've been doing or another way I > am considering? > > Thanks for reading my long and boring mail. > > Regards > > Heecheol, Yang > > _______________________________________________ > Dev mailing list > [email protected] (mailto:[email protected]) > https://lists.tizen.org/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
