On Monday 22 October 2007 11:28:10 am Aurelien Jarno wrote:
> Signed-off-by: Aurelien Jarno <[EMAIL PROTECTED]>
>
> diff --git a/arch/ppc/syslib/i8259.c b/arch/ppc/syslib/i8259.c
> index 1e5a00a..559f27c 100644
> --- a/arch/ppc/syslib/i8259.c
> +++ b/arch/ppc/syslib/i8259.c
> @@ -127,6 +127,7 @@ static void i8259_unmask_irq(unsigned int irq_nr)
> static struct irq_chip i8259_pic = {
> .typename = " i8259 ",
> .mask = i8259_mask_irq,
> + .disable = i8259_mask_irq,
> .unmask = i8259_unmask_irq,
> .mask_ack = i8259_mask_and_ack_irq,
> };
Using mdm's qemu target platform and the 4k bios that supplies a device tree,
I applied this but it didn't make any difference in the ne2k-pci adapter (not
that I noticed). It still doesn't bind to anything during bootup. (There's
no eth0.)
I also tried enabling the 8139too driver and telling qemu "-net
nic,model=rtl8139 -net user" (which made arm work), and it goes:
> PCI: Probing PCI hardware
> Memory resource not set for host bridge 0
> PCI: Cannot allocate resource region 2 of PCI bridge 0
> PCI: can't move host bridge resource
> PCI: Cannot allocate resource region 0 of device 0000:00:0d.0
> PCI: Cannot allocate resource region 1 of device 0000:00:0d.0
...
> 8139too Fast Ethernet driver 0.9.28
> 8139too 0000:00:0d.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip
> 8139too 0000:00:0d.0: Use the "8139cp" driver for improved performance and
> stability.
And then there's an eth0, but it doesn't work. I can assign an address to it
but no matter what I try, no packets are sent and received (the packet
transmit/receive/error counts never even go up, they stay at zero).
Am I doing something wrong?
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
