[meta-ti] [PATCH 0/3] beagleboard.org board updates

[Koen Kooi]

Op 1 mrt. 2012, om 14:41 heeft Maupin, Chase het volgende geschreven:

> 
>> -----Original Message-----
>> From: Koen Kooi [mailto:koen at dominion.thruhere.net]
>> Sent: Thursday, March 01, 2012 7:37 AM
>> To: Maupin, Chase
>> Cc: meta-ti at lists.yoctoproject.org
>> Subject: Re: [meta-ti] [PATCH 0/3] beagleboard.org board updates
>> 
>> 
>> Op 1 mrt. 2012, om 14:29 heeft Maupin, Chase het volgende
>> geschreven:
>> 
>>> 
>>>> -----Original Message-----
>>>> From: Koen Kooi [mailto:koen at dominion.thruhere.net]
>>>> Sent: Thursday, March 01, 2012 7:01 AM
>>>> To: Maupin, Chase
>>>> Cc: meta-ti at lists.yoctoproject.org
>>>> Subject: Re: [meta-ti] [PATCH 0/3] beagleboard.org board updates
>>>> 
>>>> 
>>>> Op 1 mrt. 2012, om 13:44 heeft Maupin, Chase het volgende
>>>> geschreven:
>>>> 
>>>>> Koen,
>>>>> 
>>>>> Why "add" the two patches from the PSP tree for linux-ti33x-psp
>>>> recipe?  Shouldn't those be picked up by changing the base that
>> you
>>>> are pulling from.  i.e. bumping the SRCREV of the base PSP tree?
>>>> 
>>>> I can't, the hwmod fixes for the ADC drivers break our sysfs
>>>> interface hack.
>>> 
>>> Is there a plan to fix this going forward?
>> 
>> Devicetree...
>> 
>>> I doubt we can avoid updating the base kernel forever.
>> 
>> I know, I'm hoping we can fix it before an update is needed. The
>> current SRCREV corresponds with a psp release, so we should be
>> reasonably safe.
> 
> True, but there is a release coming at the end of the month.  Just FYI.

In the extreme case I can add 4 reverts for the TSC stuff, but I really don't want to go there. The new code is a big step forward.

> 
>>> 
>>> Plus, when we switch our SDKs to using oe-core we will be
>> updating the base kernel.
>> 
>> I hope that is a few weeks out :)
> 
> Until I get time to work on it then yes, it is several weeks out :).  But you may want some of the changes in the next PSP release for PM.

Do I get access to that super-secret M3 firmware needed for proper PM as well? And will I be able to rebuild that with the cgt/arm toolchain? Right now enabling CONFIG_SUSPEND will block the boot for 60 seconds timing out on the m3 firmware.

regards,

Koen