Skip to contentSkip to conversation

oe-core layer including support for i.MX28

DISCUSSION Alex J Lennon 5 participants 14 messages Mar 14, 2012 – Mar 15, 2012

lore
Share & tools
lore
#0 lore raw

Hi,

I'm trying to begin the migration from oe-classic to oe-core, focussing on Freescale's i.MX28 and i.MX51. I recall there was i.MX28 kit being demo'd at FOSDEM but I can't seem to find support anywhere for the i.MX28, which I thought might be in meta-fsl-arm?

Can anybody point me in the right direction? (I've half a mind to try adding the support into meta-fsl-arm myself but that would seem somewhat wasteful if it's already been done)

Thanks,

Alex/

#1 lore raw

2012/3/14 Alex J Lennon <[email protected]>:

Quoted 1 line

Hi,

Hi,

Quoted 7 lines

I'm trying to begin the migration from oe-classic to oe-core, focussing on Freescale's
i.MX28 and i.MX51. I recall there was i.MX28 kit being demo'd at FOSDEM but I can't
seem to find support anywhere for the i.MX28, which I thought might be in meta-fsl-arm?

did the meta-fsl-arm developers merge the meta-freescale repository? AFAICT there was support for i.MX28 in Andreas git repository:
http://gitorious.org/schnitzeltony-oe-meta/meta-freescale

Quoted 6 lines

Can anybody point me in the right direction? (I've half a mind to try adding the support
into meta-fsl-arm myself but that would seem somewhat wasteful if it's already been
done)

The meta-freescale repository might need some work, but it is a starting point.

Signature · 2 lines
Regards
Samuel
#2 lore raw
Quoted 17 lines · Samuel Stirtzel

2012/3/14 Alex J Lennon <[email protected]>:

Quoted 1 line

Hi,

Hi,

Quoted 7 lines

I'm trying to begin the migration from oe-classic to oe-core, focussing on Freescale's
i.MX28 and i.MX51. I recall there was i.MX28 kit being demo'd at FOSDEM but I can't
seem to find support anywhere for the i.MX28, which I thought might be in meta-fsl-arm?

did the meta-fsl-arm developers merge the meta-freescale repository? AFAICT there was support for i.MX28 in Andreas git repository:
http://gitorious.org/schnitzeltony-oe-meta/meta-freescale

Quoted 1 line
Quoted 8 lines
Quoted 5 lines

Can anybody point me in the right direction? (I've half a mind to try adding the support
into meta-fsl-arm myself but that would seem somewhat wasteful if it's already been
done)

The meta-freescale repository might need some work, but it is a starting point.

meta-freescale merge to meta-arm-fsl is in progress - thanks Otavio:)

Andreas

#3 lore raw
Quoted 2 lines

did the meta-fsl-arm developers merge the meta-freescale repository?

Thanks Andreas, Samuel. I shall take a look.

Best Regards,

Alex

Quoted 30 lines · Andreas Müller
Quoted 13 lines · Samuel Stirtzel

2012/3/14 Alex J Lennon<[email protected]>:

Quoted 1 line

Hi,

Hi,

Quoted 6 lines

I'm trying to begin the migration from oe-classic to oe-core, focussing on Freescale's
i.MX28 and i.MX51. I recall there was i.MX28 kit being demo'd at FOSDEM but I can't
seem to find support anywhere for the i.MX28, which I thought might be in meta-fsl-arm?

did the meta-fsl-arm developers merge the meta-freescale repository? AFAICT there was support for i.MX28 in Andreas git repository:
http://gitorious.org/schnitzeltony-oe-meta/meta-freescale

Quoted 7 lines
Quoted 5 lines

Can anybody point me in the right direction? (I've half a mind to try adding the support
into meta-fsl-arm myself but that would seem somewhat wasteful if it's already been
done)

The meta-freescale repository might need some work, but it is a starting point.

meta-freescale merge to meta-arm-fsl is in progress - thanks Otavio:)

Andreas

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#4 lore raw
In reply to Alex J Lennon

[ added meta-fsl-arm on CC ]

Quoted 7 lines · Alex J Lennon

I'm trying to begin the migration from oe-classic to oe-core, focussing on Freescale's
i.MX28 and i.MX51. I recall there was i.MX28 kit being demo'd at FOSDEM but I can't
seem to find support anywhere for the i.MX28, which I thought might be in meta-fsl-arm?

Quoted 5 lines

Can anybody point me in the right direction? (I've half a mind to try adding the support
into meta-fsl-arm myself but that would seem somewhat wasteful if it's already been
done)

I am working on that; my current work in progress can be seen at
https://github.com/OSSystems/meta-fsl-arm/tree/wip-imx28 and it shouldn't be assumed to be working yet but once I get it more or less finished I ask you guys to test it as well.

Signature · 3 lines
Otavio Salvador                             O.S. Systems
E-mail: [email protected]  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
#5 lore raw

Hi Otavio,

Quoted 1 line

I am working on that; my current work in progress can be seen at https://github.com/OSSystems/meta-fsl-arm

Thanks for that. I had a quick go ad building and as you say I saw bitbake fails as it's trying to build up a patched linux-imx kernel.

"include/linux/pagemap.h: In function 'fault_in_pages_readable':"

Maybe the best way for me to proceed would be to put in a pull request on your wip-imx28 branch and see if I can add my oe-classic imx28 specifics into the copy?

Best Regards,

Alex

#6 lore raw
Quoted 7 lines · Alex J Lennon
Quoted 2 lines

I am working on that; my current work in progress can be seen at
https://github.com/OSSystems/meta-fsl-arm

Thanks for that. I had a quick go ad building and as you say I saw bitbake fails as it's trying to build up a patched linux-imx kernel.

"include/linux/pagemap.h: In function 'fault_in_pages_readable':"

I fixed the branch right now and you ought to be able to build using it.

Quoted 3 lines

Maybe the best way for me to proceed would be to put in a pull request on your wip-imx28 branch and see if I can add my oe-classic imx28 specifics into the copy?

I'll do the pull request but only after I get it properly done. There're some missing things on it and some work to be done. However, you should be able to base your work on that and keep doing rebases against this branch (be prepared to fix some conflicts on the way).

Signature · 3 lines
Otavio Salvador                             O.S. Systems
E-mail: [email protected]  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
#7 lore raw
Quoted 1 line

However, you should be able to base your work on that and keep doing rebases against this branch

Will do.

What's the view/policy on adding custom board implementations into these layers?

e.g. I'm about to start taking a look at an i.MX51 based screen unit. Various machine parameters are different including SDRAM settings, so I'll probably end up with a new machine, imx51gem or some such, much as I did with my imx28evk based "gem" in oe-classic.

Is the the new machine target and associated recipes, kernel+patches something that I should expect to be able to merge back into meta-fsl-arm at some point?

Thanks / Best Regards,

Alex

Quoted 18 lines · Otavio Salvador
Quoted 6 lines · Alex J Lennon
Quoted 2 lines

I am working on that; my current work in progress can be seen at
https://github.com/OSSystems/meta-fsl-arm

Thanks for that. I had a quick go ad building and as you say I saw bitbake fails as it's trying to build up a patched linux-imx kernel.

"include/linux/pagemap.h: In function 'fault_in_pages_readable':"

I fixed the branch right now and you ought to be able to build using it.

Quoted 3 lines

Maybe the best way for me to proceed would be to put in a pull request on your wip-imx28 branch and see if I can add my oe-classic imx28 specifics into the copy?

I'll do the pull request but only after I get it properly done. There're some missing things on it and some work to be done. However, you should be able to base your work on that and keep doing rebases against this branch (be prepared to fix some conflicts on the way).

#8 lore raw

Hi,

Quoted 4 lines · Alex J Lennon

Is the the new machine target and associated recipes, kernel+patches something that I should expect to be able to merge back into meta-fsl-arm at some point?

that depends if meta-fsl-arm is considered as the layer for supporting evaluation boards from Freescale of the layer which can host any board using a Freescale i.MX.
I think the first solution is better and that custom boards should be added to custom layers (maybe on top of meta-fsl-arm if these custom boards need recipes included in the reference layer).

Eric

Signature · 1 line
http://eukrea.com/en/news/104-2012
#9 lore raw
Quoted 2 lines

I think the first solution is better and that custom boards should be added to custom layers

Hmmm ok, thanks That being the case it may be better for me to migrate my recipes from the oe-classic codebase into a new layer created from scratch. It'll be quicker and easier for me that way but perhaps less generic.

(Although my understanding was that Freescale have no intention of providing Linux support related
to OpenEmbedded at this time? Or at least that's what they are telling
me :)

Alex/

Quoted 16 lines · Eric Bénard

Hi,

Quoted 4 lines · Alex J Lennon

Is the the new machine target and associated recipes, kernel+patches something that I should expect to be able to merge back into meta-fsl-arm at some point?

that depends if meta-fsl-arm is considered as the layer for supporting evaluation boards from Freescale of the layer which can host any board using a Freescale i.MX.
I think the first solution is better and that custom boards should be added to custom layers (maybe on top of meta-fsl-arm if these custom boards need recipes included in the reference layer).

Eric

#10 lore raw
Quoted 8 lines · Alex J Lennon
Quoted 2 lines

I think the first solution is better and that custom boards should be added to custom layers

Hmmm ok, thanks That being the case it may be better for me to migrate my recipes from
the oe-classic codebase into a new layer created from scratch. It'll be quicker and easier for
me that way but perhaps less generic.

I think many things can be merged back but it is better to have custom boards in specific layers that inherit meta-fsl-arm. That said, I do believe you ought to check if your changes cannot be made generic (ofthenly it can be done) and this could allow it to be merged here.

Quoted 4 lines

(Although my understanding was that Freescale have no intention of providing Linux support related
 to OpenEmbedded at this time? Or at least that's what they are telling me :)

Please complain at them ... this is the only way to revert it. Some individuals are working with OpenEmbedded/Yocto and it might end changing the Freescale's position if we can enough community support and complains at them :-)

Signature · 3 lines
Otavio Salvador                             O.S. Systems
E-mail: [email protected]  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
#11 lore raw
Quoted 2 lines

That said, I do believe you ought to check if your changes cannot be made generic

Will try to keep in mind.

Quoted 1 line

Please complain at them ... this is the only way to revert it.

I'll keep on at them :) Anything not to have to go back to LTIB... ;)

Alex

Quoted 23 lines · Otavio Salvador
Quoted 7 lines · Alex J Lennon
Quoted 2 lines

I think the first solution is better and that custom boards should be added to custom layers

Hmmm ok, thanks That being the case it may be better for me to migrate my recipes from
the oe-classic codebase into a new layer created from scratch. It'll be quicker and easier for
me that way but perhaps less generic.

I think many things can be merged back but it is better to have custom boards in specific layers that inherit meta-fsl-arm. That said, I do believe you ought to check if your changes cannot be made generic (ofthenly it can be done) and this could allow it to be merged here.

Quoted 4 lines

(Although my understanding was that Freescale have no intention of providing Linux support related
to OpenEmbedded at this time? Or at least that's what they are telling me
:)

Please complain at them ... this is the only way to revert it. Some individuals are working with OpenEmbedded/Yocto and it might end changing the Freescale's position if we can enough community support and complains at them :-)

#12 lore raw
Quoted 3 lines · Alex J Lennon
Quoted 1 line

Please complain at them ... this is the only way to revert it.

I'll keep on at them :) Anything not to have to go back to LTIB... ;)

I'll pray for you ;-)

Signature · 3 lines
Otavio Salvador                             O.S. Systems
E-mail: [email protected]  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
#13 lore raw
In reply to Alex J Lennon
Quoted 10 lines · Alex J Lennon
Quoted 2 lines

I think the first solution is better and that custom boards should be

added to custom layers

Hmmm ok, thanks That being the case it may be better for me to migrate my recipes from
the oe-classic codebase into a new layer created from scratch. It'll be quicker and easier for
me that way but perhaps less generic.

that was just a suggestion. meta-fsl-arm maintainers can have differents opinions ;-)

Quoted 5 lines

(Although my understanding was that Freescale have no intention of providing Linux support related
to OpenEmbedded at this time? Or at least that's what they are telling
me :)

that's not surprising.

Eric

Signature · 1 line
http://eukrea.com/en/news/104-2012