Hi,
I have a question about the ICU controller in the XO 1.75. I was
looking into porting over and extending the FIQ debugger onto the XO (which
allows debugging wedged/deadlocked kernels), and was wondering if it
was possible to force triggering a particular IRQ (not FIQ).
It's a feature common
On Fri, Sep 23, 2011 at 01:49:28PM +0100, Daniel Drake wrote:
Found them, please put future releases in f14-xo1.75 as f14-arm is no
longer used.
Moved Richard's directory, and changed the olpc-firmware builder.
--
James Cameron
http://quozl.linux.org.au/
On Fri, Sep 23, 2011 at 01:09:07PM +0100, Daniel Drake wrote:
Is this ready for build inclusion?
Yes.
--
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Hi Andrei,
On Mon, Sep 26 2011, Andrei E. Warkentin wrote:
I have a question about the ICU controller in the XO 1.75. I was
looking into porting over and extending the FIQ debugger onto the XO (which
allows debugging wedged/deadlocked kernels), and was wondering if it
was possible to force
Hi Chris, Mitch,
2011/9/26 Chris Ball c...@laptop.org:
Here's a transcription of an explanation Mitch just gave:
It's certainly possible to route any given interrupt to either FIQ or
IRQ on either core. It is possible for an instruction to cause an
interrupt/exception; that's how OFW does
2011/9/26 Mitch Bradley w...@firmworks.com:
If you write 0x400 to APB_VIRT_BASE + 0x1d008, it will assert interrupt 56 .
You can then clear it by writing 0x400 to APB_VIRT_BASE + 0x1d40c.
This uses an inter-processor communication unit. Presumably the FIG handler
would assert the interrupt
On Fri, Sep 23, 2011 at 6:03 AM, Simon Schampijer si...@schampijer.de wrote:
Hi,
we have been branching [1] off 'sucrose-0.94' with the Sucrose 0.93.5
release [2].
This is important to have the master branch available again for new
development. The 'sucrose-0.94' will be used to host
2011/9/26 Andrei E. Warkentin andrey.warken...@gmail.com:
2011/9/26 Mitch Bradley w...@firmworks.com:
If you write 0x400 to APB_VIRT_BASE + 0x1d008, it will assert interrupt 56 .
You can then clear it by writing 0x400 to APB_VIRT_BASE + 0x1d40c.
This uses an inter-processor communication
All,
At some point over the next few Sugar builds we will probably want to
freeze a last known good set of Fructose Activities as there is a
growing possibility that the ongoing changes (de-hippofication, gtk3,
PyGobject introspection) will cause problems with these important
activities.
The
2011/9/27 Mitch Bradley w...@firmworks.com:
On 9/26/2011 4:40 PM, Andrei E. Warkentin wrote:
2011/9/26 Andrei E. Warkentinandrey.warken...@gmail.com:
2011/9/26 Mitch Bradleyw...@firmworks.com:
If you write 0x400 to APB_VIRT_BASE + 0x1d008, it will assert interrupt
56 .
You can then clear
10 matches
Mail list logo