Compiled reply.
William O Ferry
> > > From: Bill Studenmund <wrst...@nas.nasa.gov>
> > > Date: 02/07/2000 15:03:39
> > >
> > > One drawback is that OF puts the 646 pciide controller in a polling mode
> > > our firmware initialization doesn't reset, so while you can boot from an
> > > ide disk, you then can't use it.
> >
> > As I recall, that means you can either boot from it *or* use it as
> > your root, but not both.
>
> Exactly. However supposedly Manuel Bouyer recently fixed this problem. It
> was that the 646 had two interrupt modes, compat and native. We didn't
> support native, so if the firmware put the chip in it, we lost. But
> someone should try it, it now might be fixed. Unfortunatly I don't still
> have a G3. :-(
I had the same impression, and figured I'd try the latest code. SUP
currently only provides a pciide.c based on 1.78 (1.79 claimed to add
native-mode support). But the patches to 1.79 were really easy so I
applied them to my sources and rebuilt the kernel. Unfortunately
nothing changed on my Blue&White, if I run ofwboot.elf or load the
kernel off the internal HD I get the same old lost interrupt messages.
Oh, well. Back to zip booting.. =)
Will Ferry
Andreas Wrede
On 07/13/2000 12:09:58, Bill Studenmund <wrst...@zembu.com>
> On Thu, 13 Jul 2000, gabriel rosenkoetter wrote:
> [..]
>> As I recall, that means you can either boot from it *or* use it as
>> your root, but not both.
>
> Exactly. However supposedly Manuel Bouyer recently fixed this problem. It
> was that the 646 had two interrupt modes, compat and native. We didn't
> support native, so if the firmware put the chip in it, we lost. But
> someone should try it, it now might be fixed. Unfortunatly I don't still
> have a G3. :-(
I compiled a GENERIC kernel with Revision 1.79 of pciide.c, but the
problem persists: Netbooting the G4 allows the kernel to access the
IDE drive, but booting from the IDE drive via ofwboot.elf produces a
never ending stream of lost interrupts. In both cases the probe lines
from pciide are the same:
pciide0 at pci1 dev 1 function 0: CMD Technology PCI0646 (rev. 0x07)
pciide0: bus-master DMA support present
pciide0: primary channel configured to native-PCI mode
pciide0: using irq 26 for native-PCI interrupt
[...]
root on wd0a: dumps ins wd0b
pciide0:0:0: lost interrupt
type: ata tc_bcount: 512 tc_skip: 0
[many more]
pciide0:0:0: bus-master DMA error: missing interrupt, status 0x20
wd0: transfer error, downgrading to PIO mode 4
wd0(pciide0:0:0): using PIO mode 4
[...]
pciide0:0:0: lost interrupt
type: ata tc_bcount: 512 tc_skip: 0
[and so on...]
Does the driver somehow not recognize that the firmware initialized
the 646 in compat mode?
NetBSD 1.5B (GENERIC) #5: Sun Jul 16 00:06:52 EDT 2000
root@walker:/usr/src/sys/arch/macppc/compile/GENERIC
total memory = 65536 KB
avail memory = 54636 KB
using 844 buffers containing 3376 KB of memory
mainbus0 (root)
cpu0 at mainbus0: 7400 (Revision 206), ID 0 (primary)
cpu0: 1MB backside cache
grackle0 at mainbus0
pci0 at grackle0 bus 0
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 0 function 0
pchb0: Motorola MPC106 "Grackle" Host Bridge (rev. 0x40)
ppb0 at pci0 dev 13 function 0: Digital Equipment DECchip 21154 PCI-PCI Bridge (rev. 0x02)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
Texas Instruments TSB12LV21 IEEE 1394 Host Controller (Firewire serial bus, revision 0x04) at pci1 dev 0 function 0 not configured
pciide0 at pci1 dev 1 function 0: CMD Technology PCI0646 (rev. 0x07)
pciide0: bus-master DMA support present
pciide0: primary channel configured to native-PCI mode
pciide0: using irq 26 for native-PCI interrupt
wd0 at pciide0 channel 0 drive 0: <QUANTUM FIREBALL CX10.2A>
wd0: drive supports 16-sector pio transfers, lba addressing
wd0: 9787 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 20044080 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
pciide0: secondary channel configured to native-PCI mode
pciide0: secondary channel ignored (disabled)
cy0 at pci1 dev 2 function 0: interrupting at irq 23
cy0: 8 ports
ex0 at pci1 dev 3 function 0: 3Com 3c905C-TX 10/100 Ethernet with mngmt (rev. 0x74)
ex0: interrupting at irq 24
ex0: MAC address 00:50:da:c6:d3:ef
ukphy0 at ex0 phy 24: Generic IEEE 802.3u media interface
ukphy0: OUI 0x001018, model 0x0017, rev. 6
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
obio0 at pci1 dev 5 function 0: addr 0x80800000
scsi at obio0 offset 0x10000 not configured
zsc0 at obio0 offset 0x13000: irq 15,16
zstty0 at zsc0 channel 0
zstty1 at zsc0 channel 1
davbus at obio0 offset 0x14000 not configured
fdc at obio0 offset 0x15000 not configured
adb0 at obio0 offset 0x16000 irq 18: 0 targets
aed0 at adb0 addr 0: ADB Event device
wdc0 at obio0 offset 0x20000 irq 13: DMA transfer
atapibus0 at wdc0 channel 0
cd0 at atapibus0 drive 0: <MATSHITA CR-589, , GA0W> type 5 cdrom removable
cd0: drive supports PIO mode 4, DMA mode 2
bm0 at obio0 offset 0x11000 irq 42,33: address 00:50:e4:10:ac:55
lxtphy0 at bm0 phy 0: LXT970 10/100 media interface, rev. 3
lxtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
nvram0 at obio0 offset 0x60000
ohci0 at pci1 dev 6 function 0: Opti RM861HA (rev. 0x10)
ohci0: interrupting at irq 28
ohci0: OHCI version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: Opti OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ofb0 at pci0 dev 16 function 0: ATI Technologies product 0x5245
ofb0: 640 x 480, 8bpp
wsdisplay0 at ofb0: console (std, vt100 emulation)
uhub1 at uhub0 port 1
uhub1: Mitsumi Electric Hub in Apple USB Keyboard, class 9/0, rev 1.10/2.11, addr 2
uhub1: 3 ports with 2 removable, bus powered
ukbd0 at uhub1 port 1 configuration 1 interface 0
ukbd0: Mitsumi Electric Apple USB Keyboard, rev 1.00/1.03, addr 3, iclass 3/1
wskbd1 at ukbd0: console keyboard, using wsdisplay0
ums0 at uhub1 port 2 configuration 1 interface 0
ums0: Mitsumi Apple USB Mouse, rev 1.00/5.01, addr 4, iclass 3/1
ums0: 1 buttons
wsmouse1 at ums0
boot device: bm0
root on bm0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP server: 204.29.161.33
nfs_boot: my_name=test2.planix.com
nfs_boot: my_domain=planix.com
nfs_boot: my_addr=204.29.161.49
nfs_boot: my_mask=255.255.255.224
nfs_boot: gateway=204.29.161.51
root on 204.29.161.33:/u5/client/macppc/walker/root
--
- aew
Manuel Bouyer
>
> I compiled a GENERIC kernel with Revision 1.79 of pciide.c, but the
> problem persists: Netbooting the G4 allows the kernel to access the
> IDE drive, but booting from the IDE drive via ofwboot.elf produces a
> never ending stream of lost interrupts. In both cases the probe lines
> from pciide are the same:
>
> pciide0 at pci1 dev 1 function 0: CMD Technology PCI0646 (rev. 0x07)
> pciide0: bus-master DMA support present
> pciide0: primary channel configured to native-PCI mode
> pciide0: using irq 26 for native-PCI interrupt
> [...]
> root on wd0a: dumps ins wd0b
> pciide0:0:0: lost interrupt
> type: ata tc_bcount: 512 tc_skip: 0
> [many more]
> pciide0:0:0: bus-master DMA error: missing interrupt, status 0x20
> wd0: transfer error, downgrading to PIO mode 4
> wd0(pciide0:0:0): using PIO mode 4
> [...]
> pciide0:0:0: lost interrupt
> type: ata tc_bcount: 512 tc_skip: 0
> [and so on...]
>
> Does the driver somehow not recognize that the firmware initialized
> the 646 in compat mode?
No. The 0646 can be configured in strange mode but in hardware only (via
power-on status of some pins); the fact that it works sometimes exclude this.
I also checked with Bill that the PCI config space registers are identical in
both case, so the difference is somewhere else; either at the HD level (but
this seems unlikely, at last I can't see anything in the ATA specs that
could explain this) or at the PCI bridge level.
Maybe you could dump the config of ppb0 in both cases and see if there's
something different ? What about grackle0 ?
--
Manuel Bouyer, LIP6, Universite Paris VI. Manuel...@lip6.fr
--