From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mw9dK-0000ZD-N2 for qemu-devel@nongnu.org; Fri, 09 Oct 2009 03:11:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mw9dG-0000YN-Jr for qemu-devel@nongnu.org; Fri, 09 Oct 2009 03:11:22 -0400 Received: from [199.232.76.173] (port=37591 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mw9dG-0000YK-DV for qemu-devel@nongnu.org; Fri, 09 Oct 2009 03:11:18 -0400 Received: from mx20.gnu.org ([199.232.41.8]:8681) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mw9dF-0006YE-Sf for qemu-devel@nongnu.org; Fri, 09 Oct 2009 03:11:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mw9dF-0000ja-83 for qemu-devel@nongnu.org; Fri, 09 Oct 2009 03:11:17 -0400 Subject: Re: [Qemu-devel] [PATCH 00/16] Add a -netdev option From: Mark McLoughlin In-Reply-To: <4ACE4B99.2010606@mail.berlios.de> References: <1255028312-28180-1-git-send-email-markmc@redhat.com> <4ACE4B99.2010606@mail.berlios.de> Content-Type: text/plain Date: Fri, 09 Oct 2009 08:09:35 +0100 Message-Id: <1255072175.2786.11.camel@blaa> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: Mark McLoughlin List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: qemu-devel@nongnu.org Hi Stefan, On Thu, 2009-10-08 at 22:29 +0200, Stefan Weil wrote: > Hi Mark, > > today, qemu's ethernet devices are a fixed combination of > MAC (Media Access Controller) and PHY (Physical Layer). > > Real hardware is different: the controllers provide a MAC, > and many provide a PHY, too, but all controllers allow > one or even several external PHY(s). > > Most (or all?) controllers use the same standard interface > to address their PHY (internal or external), something > which is completely missing today in qemu. > > A better solution would use separate code for MAC and > PHY, so the controllers could share common code for the > PHY. > > Configuration of a different PHY should be possible, > so users can run a system emulation of different > MAC-PHY combinations. > > In addition to the PHY type, a PHY needs attributes > (link speed and link status). > > Maybe you can address these requirements in your > redesign. Doesn't that sound like something purely for the device model itself, as opposed to the core packet handling code? Thanks, Mark.