Florian Boelstler schrieb:
> I'm not sure at the moment whether too many ppc_md.progress()-messages
> may keep the PowerBook from proceeding fast enough.
Well it turned out, that depending on if btext debug output makes use of
scrolling (see #undef NO_SCROLL in arch/ppc/syslib/btext.c) a function
scrollscreen() calls pmu_suspend() / pmu_resume().
Since the amount of debug output reaches the lower screen at around
init_pmu() the screen is scrolled, which leads to a call of
pmu_suspend(), which may interfere with the corresponding functionality
in init_pmu(). At least is prevents further messages printed to the
screen. *OUCH*
An intermediate solution is to #define NO_SCROLL, which shows that the
kernel proceeds beyond init_pmu().
Later on it panics at pmac_m2_init() since find_devices("m2") fails --
but this is something completely different.
Cheers,
Florian
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
Nubus-pmac-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users
