qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] PreP kernels boot using Qemu
Date: Sat, 27 Oct 2007 03:00:54 -0500	[thread overview]
Message-ID: <200710270300.55102.rob@landley.net> (raw)
In-Reply-To: <20071022162810.GA12778@hall.aurel32.net>

On Monday 22 October 2007 11:28:10 am Aurelien Jarno wrote:
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
>
> 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.

  parent reply	other threads:[~2007-10-27  7:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22  7:36 [Qemu-devel] PreP kernels boot using Qemu J. Mayer
2007-10-22  9:23 ` Jocelyn Mayer
2007-10-27  1:59   ` Rob Landley
2007-10-22 16:28 ` Aurelien Jarno
2007-10-22 21:12   ` J. Mayer
2007-10-22 22:05     ` Aurelien Jarno
2007-10-22 22:36       ` J. Mayer
2007-10-23 11:47         ` Thiemo Seufer
2007-10-23 21:53           ` J. Mayer
2007-10-23 21:59             ` Aurelien Jarno
2007-10-23 23:06               ` J. Mayer
2007-10-24  0:08             ` Thiemo Seufer
2007-10-27  8:00   ` Rob Landley [this message]
2007-10-27  8:07     ` Aurelien Jarno
2007-10-28 10:25       ` Rob Landley
2007-10-28  9:29         ` Aurelien Jarno
2007-10-28 14:17           ` Rob Landley
2007-10-31  2:30             ` Ed Swierk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200710270300.55102.rob@landley.net \
    --to=rob@landley.net \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).