[Meego-porting] Porting MeeGo on ARM11
vijay singh
testmrs.evo at gmail.com
Mon Oct 18 01:09:45 PDT 2010
Hi,
If the list is alive or active then can i get step proceeding answer for
below mail.
Thanks...
On Mon, 2010-09-27 at 09:35 +0200, Jari.Palojarvi at nokia.com wrote:
> Hi again,
>
>
>
> Alexander, some questions to you:
>
> - Any idea if the ARMv5 builds will start again at some point?
>
> - If not, what are the latest ARMv5 builds that one could try?
>
> - If someone would want to build the whole MeeGo OS to
> ARMv5/ARMv6 with his own tool chain, what would be the best way (I’m
> saying something about that below but don’t know if that is accurate)?
>
> - Off topic: is there some defined process through which you
> could introduce a new reference HW to MeeGo.com?
>
>
>
> Some comments also below in red…
>
>
>
> Regards, Jari
>
>
>
>
>
> From: ext evolution test [mailto:testmrs.evo at gmail.com]
> Sent: 25. syyskuuta 2010 15:44
> To: Palojarvi Jari (Nokia-MS/Tampere)
> Cc: meego-porting at lists.meego.com
> Subject: Re: [Meego-porting] Porting MeeGo on ARM11
>
>
>
>
>
>
> On Sat, Sep 25, 2010 at 1:03 AM, <Jari.Palojarvi at nokia.com> wrote:
>
> Hi,
>
>
>
> My understanding below (I hope its correct).
>
>
>
> I’d say that the best approach would be to start by following – at
> least roughly - the Trials section in the MPG.
>
>
> What will be the base image for me to try ??
>
>
>
>
>
>
> However, as the ARMv5 builds in MeeGo.com are currently
> suspended, there are no up to date MeeGo images available that
> would be suitable for your HW. Thus, you would need to build
> both the kernel (either your own one or the “official” MeeGo
> kernel) and the rest of the MeeGo OS for your device with your
> own tool chain. In this sense, http://wiki.meego.com/ARM/N8x0
> is a pretty similar case but I don’t know how actively that
> work is proceeding.
>
>
> Can i know when the ARMv5 build will start. ??
>
>
> Can anyone let me know if he/she is working for similar HW platform.
>
>
>
>
>
>
>
> Pretty good instructions for building the MeeGo kernel are
> these:
> http://wiki.meego.com/How-to:_getting_new_chipset_support_to_the_MeeGo_kernel .
>
>
>
>
>
> So here you mean that build your own kernel by own toolchain.
>
>
> In this case how the kernel will be compatible with the kernel used by
> MeeGo.
>
>
>
> The instructions behind the above link are about building the MeeGo
> kernel. But if you use your own kernel, there’s no guarantee that it
> will be fully compatible with the rest of the MeeGo OS stack.
>
>
>
>
> Regarding building the rest of the MeeGo OS (rootfs), I’d
> think that the best approach would be to try to imitate how
> things are done at MeeGo.com. Meaning setting up your own OBS,
> linking it to the MeeGo.com, creating the binary packages (and
> using your own compiler toolchain in this process) and finally
> using MIC to create the image. Unfortunately I cannot yet
> point you to any good instructions about how all this would go
> in detail.
>
> I also don’t know if you could avoid the need for your own OBS
> somehow, e.g. by using the osc tool.
>
>
>
>
> if i will build all the binary package,then how it will be work like
> MeeGo.
>
>
>
> Yes, the “imitate” verb above basically tries to suggest that the only
> thing specific to you would be your tool chain (compiler). Otherwise
> you would just be referring to the way how things are done at
> MeeGo.com. But like said, I don’t know how all this really would go in
> practice (Alexander might know).
>
>
>
>
> I am expecting some MeeGo base so that on top of that i can build my
> application package & run on MeeGo.
>
>
>
> Yes, this is the understandable expectation. But unfortunately now
> ruined by the lack of suitable MeeGo builds.
>
>
>
>
>
> If i will get more detail about how to proceed than i can start work
>
>
>
> I hope that Alexander can give you some pointers to better
> information.
>
>
>
> Regards, Jari
>
>
>
>
>
> More advice or comment will be help me to start.
>
>
> Regards, Jari
>
>
>
>
>
> From: meego-porting-bounces at lists.meego.com
> [mailto:meego-porting-bounces at lists.meego.com] On Behalf Of
> ext evolution test
> Sent: 23. syyskuuta 2010 13:59
> To: meego-porting at lists.meego.com
> Subject: [Meego-porting] Porting MeeGo on ARM11
>
>
>
>
> Hello,
> I would like to know the approaches to port MeeGo on below HW
> configuration.
>
> Family : ARM11
> Architecture Version : ARMv6K
> Core :ARM11 MPCore
>
> I would have below SW ready for my board.
>
> - Toolchain to build src.
> - u-boot for one core to boot for MeeGo.
> - Kernel & Module.
>
> I already gone through MPG document,with that i came to know
> many approaches to start MeeGO porting on new HW.
>
> I am writing below approaches with question coming to my mind.
> Please advice/suggest me which is best approaches to start.
>
>
> 1. Vendor's own OBS :
> · With this approaches i understand that i need to create
> my own OBS build system.
> * How can i set my own toolchain.Referring to cross
> compile section under below link will not talk about
> how to setup our own toolchain.
> http://wiki.meego.com/Build_Infrastructure/Sysadmin_Distro/OBS_setup_openSUSE112
> * How can i get the MeeGo components buiild for my HW
> architecture.
> * What all other points i need to take care.
>
> 2.Working under MeeGo.com
>
> * How can i get accepted above HW. ??
> * How it will be differ from above approaches. ??
>
> 3.Trials
> In this case i thought to use base from below link.
> //http://wiki.meego.com/ARM/N8x0
>
> * Is this will work for my HW ??
> * What all modification i need to do to get it work ??
> (Need suggestion)
> * I am sure that some or more package i need to build
> for my HW, in this case do i need to creat new project
> under OBS or i can do cross build package locally
> using my toolchain & add local repo into KS file &
> creat MeeGo image.
>
> I would like to know more comment & support so that i can
> start porting.
>
> Cheers--
> Vij
>
>
>
>
>
>
>
More information about the Meego-porting
mailing list