On Thu, Jan 6, 2011 at 21:04, Edgar E. Iglesias wrote:
> You'll have to check the details in the code but I hope this gets
> you going.
thanks, that info was perfect. it allowed me to understand better
what qemu actually was doing and track down the problem. i thought
the infinite loop/hang was
On Thu, Jan 06, 2011 at 01:47:56PM -0500, Mike Frysinger wrote:
> On Wed, Jan 5, 2011 at 05:59, Edgar E. Iglesias wrote:
> > On Tue, Jan 04, 2011 at 02:43:11PM -0500, Mike Frysinger wrote:
> >> i've been working on a new architecture port, but i cant quite figure
> >> out some of the intricacies fr
On Wed, Jan 5, 2011 at 05:59, Edgar E. Iglesias wrote:
> On Tue, Jan 04, 2011 at 02:43:11PM -0500, Mike Frysinger wrote:
>> i've been working on a new architecture port, but i cant quite figure
>> out some of the intricacies from reading the code. i have all the
>> simple stuff working for linux-u
On Tue, Jan 04, 2011 at 02:43:11PM -0500, Mike Frysinger wrote:
> i've been working on a new architecture port, but i cant quite figure
> out some of the intricacies from reading the code. i have all the
> simple stuff working for linux-user (register moves, immediate moves,
> loads, stores, sysca
i've been working on a new architecture port, but i cant quite figure
out some of the intricacies from reading the code. i have all the
simple stuff working for linux-user (register moves, immediate moves,
loads, stores, syscall emulation) and want to move on to the next big
piece -- code flow cha
