I figured out I can't iprint my way out of the problem, because iprint doesn't work until after trapinit is over.
I added a special case to intrs so that if ibits is 0x00000010 and the sort is Irqbridge, we just turn off that bit in the irq mask, and uncommented several debuggy iprints. I found the sheevamem structure and changed its 512*MB to 256*MB because my TS-212 only has 256 MB of RAM, according to the u-boot startup message. (I think TS-219s have 512 MB.) Now my message looks like so: Marvell>> go 0x800000 ## Starting application at 0x00800000 ... Plan 9 from Bell Labs l1 D: 16384 bytes, 4 ways 128 sets 32 bytes/line; write-through only l1 I: 16384 bytes, 4 ways 128 sets 32 bytes/line; write-back type `reg 7 ops, format C' (016) possible l2 cache: 256K or 512K: 4 ways, 32-byte lines, write-back, sdram only cpu0: 1200MHz ARM Marvell 88F6281 A1; arm926ej-s arch v5te rev 2.1 part 131 enabling intr 0 vec 11 for ether0 #l0: 88e1116: 100Mbps port 0xf1072000 irq 11: 00089bc1d539 enabling intr 1 vec 1 for eia0 duplicate irq: eia0 (0x60859aac) 248intrs: quashing bridge irq 00000010 enabling intr 0 vec 29 for twsi M memory: 27M kernel data, 221M user, 961M swap (The "intrs:" message is mine.) Then it just hangs there. It does not automatically reboot after 10 seconds. Has the kernel finished starting up? Do I now need to figure out the next step in the boot process? On 7/9/11, Jared Jennings <jjenn...@gmail.com> wrote: > On 7/9/11, erik quanstrom <quans...@quanstro.net> wrote: >> as a wag, i would start by tweaking ether1116.c (sic) to leave the >> second port alone. > > Wagged. It appears from the code in devether.c that the MaxEther enum > in devether.h is what controls how many ethernet cards are frobbed. I > changed MaxEther from 2 to 1. It said the same thing except without > the #l1 line. > > Because I saw the "#u/u" right before the message, I tried turning off > the USB entirely by commenting it out in the plug file. The "#u/u" at > the beginning of the line went away, but the "spurious irqbridge > interrupt: 00000010" messages continue. > > Still investigating. >
