Hi Ulrich,
> OK. So I guess the only remaining questions is: if this hardware needs the
> errata fix to work properly, shouldn't it be automatically selected by the
> kernel configure logic? Note that this appears to happen for certain OMAP
> boards, see arch/arm/mach-omap2/Kconfig:
>
> config
"Will Deacon" wrote on 02/16/2011 01:07:09 PM:
> > I've now built a kernel with CONFIG_ARM_ERRATA_720789 enabled, and the
> > symptoms indeed seem to have disappeared completely ...
>
> Yup - that's because without it, invalidating a TLB entry for a
particular
> process isn't broadcast correctly,
Hi Ulrich,
> I've now built a kernel with CONFIG_ARM_ERRATA_720789 enabled, and the
> symptoms indeed seem to have disappeared completely ...
Yup - that's because without it, invalidating a TLB entry for a particular
process isn't broadcast correctly, so you can end up using the old (pre-COW)
map
> "Will Deacon" wrote on 02/14/2011 11:30:45 AM:
>
> > > - In testing on Versatile Express, I noticed what appears to be SMP
> > > related bugs in handling regular software breakpoints:
occasionally,
> > > software breakpoints simply are not hit and execution continues as
if
> > > the underl
"Will Deacon" wrote on 02/14/2011 11:30:45 AM:
> > - In testing on Versatile Express, I noticed what appears to be SMP
> > related bugs in handling regular software breakpoints: occasionally,
> > software breakpoints simply are not hit and execution continues as if
> > the underlying code h
Hi Ulrich,
> I've now got it working reliably on on Versatile Express, after fixing
> a couple of bugs on the GDB side (both in the HW-watchpoint patch, and
> in common GDB code). The testsuite now passes with no regressions when
> enabling HW watchpoints, except for two tests that require more t
"Will Deacon" wrote on 02/11/2011 10:13:01 AM:
> I don't have a pandaboard, so I'd be interested to see if the code
> works there. I developed it using ARM boards, so the versatile express
> is a known good target.
I've now got it working reliably on on Versatile Express, after fixing
a couple o
> On Fri, Feb 11, 2011 at 4:23 AM, Ulrich Weigand
> wrote:
> >> The simple rule is Cortex-A8 is unsupported and Cortex-A9 is supported.
> >> The A5 should work (untested) and the A15 will need a bit of hacking to
> >> get it supported.
> >
> > OK. I guess I can try on our Versatile Express.
>
>
On Fri, Feb 11, 2011 at 4:23 AM, Ulrich Weigand
wrote:
>> The simple rule is Cortex-A8 is unsupported and Cortex-A9 is supported.
>> The A5 should work (untested) and the A15 will need a bit of hacking to
>> get it supported.
>
> OK. I guess I can try on our Versatile Express.
The PandaBoards ur
Hi Will,
> > - It seems odd that the kernel says it doesn't support the debug
> > architecture, but then reports to user space that 1 watchpoint and 6
> > breakpoints are supported ... GDB will never use the watchpoint,
because
> > the maximum watchpoint size is reported as zero, but GDB will at
Hi Arnd,
> > The memory-mapped interface is hugely unreliable in real hardware because
> > you have to calculate the address of the memory-mapped debug registers by
> > using a base and offset, which are hardcoded in some information registers.
> > Unfortunately, I've never found a board where the
On Wednesday 09 February 2011 20:25:32 Will Deacon wrote:
> > - Why is architecture 0x4 not supported? This seems to be the variant of
> > the v7 debug architecture with memory-mapped registers. Apparently the
> > IGEP only supports this version ... Do you know what the
> > Beagle-/Pandaboard an
> Hello Will,
Hi Ulrich,
> I've been trying to get GDB support for hardware watchpoints/breakpoints
> going. I've ported Matthew's GDB patch to current mainline, and am running
> this under a 2.6.37-1002-linaro-omap kernel on an IGEPv2 board.
Great - it's nice to see somebody using this stuff!
13 matches
Mail list logo
