*boggle* Where'd you manage to find all that info? Gods, I hope you're right.. might mean full 1400 usage, which I'd LOVE! (I'm sure the 5300 guys wouldn't mind, either.)
On Nov 13, 2007 4:16 AM, Alex Kenis <[EMAIL PROTECTED]> wrote: > About the powerbook troubles, I looked at the interrupt settings in > the nbpmac_m2.c, and they appear to be wrong. Of course... it could > be ME that is wrong, but this is what it looks like how it could be > changed to fix the problem. I looked into some older code, and it > looks like the M2 class powerbooks are similar to the PDM class x100 > Powermacs in terms of the interrupt handling. Of course... this > would mean a re-writing of all the powerbook-related code, but there > should not be all that much. > > Currently they are grouped as > ICR:0-7 > VIA1:0-6 > VIA2:0-6 > SLOT:0-7 > baboon:0-2 > possible irq sources:0 > > The 'slot', 'baboon', and 'sources' appear to be the wrong > structure. Here is what i *THINK* it should look like with ** > marking the corrections. > > ICR 0-7 > 00-correct (via1 interrupt) cascade > 01-correct (via2 interrupt) > <<<<<INCORRECT STRUCTURE?... **should be as follows>>>>> > **02-DEV SCC > **03-DEV ETHERNET > **04-PDM DMA INTERRUPT > **05-DEV NMI > 06-correct (INT mode bit) > 07-correct (ack bit) > > VIA1 0-6 > 00-correct (cascade) > 01-correct (dev_hz) > <<<<<INCORRECT STRUCTURE? ... **should be as follows>>>>> > **02- > **03-VIA DATA > **04-VIA CLK SOURCE for DEV_PMU > **05-DEV_TIMER2 > **06-DEV_TIMER1 > <<<For some reason, the author added an interrupt # "15 any interrupt > pending" here???>>>>> > > VIA2 0-6 > 00-correct (unused SCSI a DMA) > 01-correct (slot interrupt) > **02-INCORRECT but it does not matter because it is an unused SCSI B DMA > 03-correct (DEV_SCSI0) > 04- /*reserved*/ > 05-correct (DEV_FD floppy) > ***06-INCORRECT, SHOULD BE DEV_SCSI1 > <<<<<For some reason, the author added interrupt # "23 any interrupt > pending" here???>>>>> > > SLOT 0-6 > <<<<<This was incorrectly labeled "SLOT 0-7" and "BABOON 0-2" with > some strange N/A assignments>>>>> > <<<<<INCORRECT STRUCTURE?... **should be as follows>>>>> > 00-correct (TREX PCNCIA) > 01-correct ((E)CSC) > 02-correct (dev_nubus3 modem) > **03-INCORRECT SHOULD BE DEV_ATA0 > **04-INCORRECT SHOULD BE DEV_ATA1 > 05-correct (DEV_VBL internal expansion or keystone video) > <<<This is a BIG oops?... here is an interesting bit of information > from the MkLinux project... I assume commands to let the Whitney I/O > chip buffer into main memory>>> > 06-INCORRECT (see below:) > #if 0 > struct powermac_interrupt m2_dma_interrupts > 00 PMAC_DMA_SCC_B_RX > 01 PMAC_DMA_SCC_B_TX > 02 PMAC_DMA_SCC_A_RX > 03 PMAC_DMA_SCC_A_TX > 04 PMAC_DMA_ETHERNET_RX > 05 PMAC_DMA_ETHERNET_TX > 06 PMAC_DMA_FLOPPY > 07 PMAC_DMA_AUDIO_IN > 08 PMAC_DMA_AUDIO_OUT > > So it looks like what was assumed to be the clock source for the PMU > was wrongly assigned to a different bus' clock source, and the audio > was completely missed, as well as the floppy. So if I am close... we > should be able to fix (or at least start to fix) the sound, random > PMU power-off troubles and give a little more insight into the > floppy. Should not be too hard to fix actually, but someone more > experienced might want to look at it. If anyone wants to compare > this IRQ arrangement to the original file and see if it makes sense, > that would be great. > > I also have the physical addresses from various bits of code from > other ports: > IO_BASE_ADDR 0x50f00000 > IO_SIZE 0x42000 > IDE0_BASE 0x50F1A000 > IRQ control register IO_BASE_ADDR+0x2a000 > PMU registers IO_BASE_ADDR > VIA1_IFR IO_BASE_ADDR+0x01a00 > VIA1_IER IO_BASE_ADDR+0x01c00 > VIA1_PCR IO_BASE_ADDR+0x01800 > VIA1_AUXCONTROL IO_BASE_ADDR+0x01600 > VIA1_T1COUNTERLOW IO_BASE_ADDR+0x00800 > VIA1_T1COUNTERHIGH IO_BASE_ADDR+0x00A00 > VIA1_T1LATCHLOW IO_BASE_ADDR+0x00C00 > VIA1_T1LATCHHIGH IO_BASE_ADDR+0x00E00 > VIA2_IFR IO_BASE_ADDR+0x3a00 > VIA2_IER IO_BASE_ADDR+0x3c00 > VIA2_SLOT_IFR IO_BASE_ADDR+0x3e00 > DMA_IFR IO_BASE_ADDR+0x2a008 > DMA_AUDIO IO_BASE_ADDR+0x2a00a > > > I have pulled together as much code as i could from 68k ports, > MkLinux and HURD, so if anyone needs it, lemme know. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Nubus-pmac-users mailing list > Nubus-pmac-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nubus-pmac-users mailing list Nubus-pmac-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users
