From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IiwJE-0000fp-Ow for qemu-devel@nongnu.org; Fri, 19 Oct 2007 14:10:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IiwJ9-0000ew-E3 for qemu-devel@nongnu.org; Fri, 19 Oct 2007 14:10:54 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IiwJ9-0000et-AJ for qemu-devel@nongnu.org; Fri, 19 Oct 2007 14:10:51 -0400 Received: from mercury.realtime.net ([205.238.132.86] helo=ruth.realtime.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IiwJ3-0000Qc-DN for qemu-devel@nongnu.org; Fri, 19 Oct 2007 14:10:51 -0400 In-Reply-To: <1192815587.11576.32.camel@jma4.dev.netgem.com> References: <200710181912.57825.rob@landley.net> <20071019151916.GA17481@hall.aurel32.net> <1192815587.11576.32.camel@jma4.dev.netgem.com> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Milton Miller Subject: Re: [Qemu-devel] I got a kernel booted under qemu-system-ppc ! Date: Fri, 19 Oct 2007 13:10:27 -0500 Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: l_indien@magic.fr Cc: qemu-devel@nongnu.org, Aurelien Jarno On Oct 19, 2007, at 12:39 PM, Jocelyn Mayer wrote: > On Fri, 2007-10-19 at 17:19 +0200, Aurelien Jarno wrote: >> The small patch below fixes the IDE problem, but not the NE2000 ISA >> one. >> Please apply. > > Interesting, thanks. I'll test this and apply or check for more fixes > if > needed... I'll also try to check what's happening with the NE2000. > Could > it be the ne2000_irq table in ppc_prep.c would not be correct ? I started to look at ne2k also but don't remember the details. Evenutally the driver shoudl learn the interrupt thorugh the information in the device tree but I'm sure the isa driver does not presently. > It may > also be usefull to be able to use PCI network devices, if the target > runs properly, isn't it ? It would mean the interrupt code could eb discovered easily, once we get pci to fully work. > If the proposed ROM image is best suitable to make PreP target run (and > as I don't spend a lot of time hacking OHW those days), it may also be > interesting to add a ppc_prep_rom.bin to the repository... In fact, it > was maybe not a good idea to try to use the same BIOS image on all > PowerPC targets... The code has drawbacks, as I mentioned. Its very linux specific and the only error it finds is no load segement in the presumed elf header. It wouldn't be that hard to add some error checking and even print error to the serial. The code itself is not platform specific but the device tree attached to it is. As I said, we could link multiple copies together (one for each platform) and search until we got the right one; or just search trees based on the platform with the fixups in code specific to that tree. In that regard, this would be an option to use when using -kernel instead of being tied to the prep platform.