...are available here: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-09-20
Standup meeting minutes are here: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-09-17
A recording of the call is here: http://tc.seabright.co.nz/toolchainwg/
The interesting events this week include Ira Rosen and Zach Welch joining us, a bunch of new issues found via the Ubuntu builds, preperations for releasing GDB with the next milestone, discussing how to knock a few low priority items off the list, and arranging hardware for trying string routines on the A9.
-- Michael
On Tue, Sep 21, 2010 at 03:53:48PM +1200, Michael Hope wrote:
...are available here: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-09-20
Heya Michael,
What's the issue with the OMAP3 memory map you bring up? I bet somebody here can help with that.
Are you sufficiently unblocked on cortex-strings?
On the A15, you'll want to talk to Roger, but I think we will only have early access if a Landing Team is in place to buffer it.
The hardware index tells me that all our versatile expresses are in the KWG or platform, but I know there are additional ones meant to be sent our way, so if you could check with Stephen D. he should be able to help you out. If there isn't one, I would suggest having Peter P. allocate his board to somebody on your team, since it's so critical this work gets done. Be sure to follow up with me if you are blocked on this.
On 21 September 2010 21:11, Christian Robottom Reis kiko@linaro.org wrote:
On Tue, Sep 21, 2010 at 03:53:48PM +1200, Michael Hope wrote:
...are available here: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-09-20
What's the issue with the OMAP3 memory map you bring up? I bet somebody here can help with that.
This is the question I raised on this list a week or two back ("omap3 startup memory map", 6 Sep). I had a very helpful conversation with Richard Woodruff this afternoon. So the good news is that I have a much better idea of what the hardware does; the bad news is that qemu isn't really in a position to model it :-) [the omap3 apparently hides its boot ROM for most purposes using a combination of trustzone and some special hardware so that the effect is that code can't see it but it still gets to control what happens on exceptions. I'll have a think and look at the code to see if there's anything we can sensibly do but it might well be that the "don't let the GPMC map anything at address zero" bodge is the most pragmatic thing for now.]
-- PMM
-
Christian Robottom Reis -
Michael Hope -
Peter Maydell