qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <Laurent@Vivier.EU>
To: "Hervé Poussineau" <hpoussin@reactos.org>, qemu-devel@nongnu.org
Cc: Leon Alrae <leon.alrae@imgtec.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 0/3] dp8393x update
Date: Fri, 02 Jan 2015 02:34:56 +0100	[thread overview]
Message-ID: <54A5F5C0.4030402@Vivier.EU> (raw)
In-Reply-To: <54A5B5A0.7000600@reactos.org>

[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]

Hi Hervé,

Le 01/01/2015 22:01, Hervé Poussineau a écrit :
> Hi Laurent,
> 
> Le 29/12/2014 01:39, Laurent Vivier a écrit :
>> This is a series of patches I wrote to use dp8393x (SONIC) with
>> Quadra 800 emulation. I think it is interesting to share them with the
>> mainline.
>>
>> Qdev'ifying allows to remove the annoying warning:
>> "requested NIC (anonymous, model dp83932) was not created
>>   (not supported by this machine?)"
>>
>> [PATCH 1/3] dp8393x: add registers offset
>> [PATCH 2/3] dp8393x: add PROM to store MAC address
>> [PATCH 3/3] qdev'ify dp8393x
>>
> 
> I also had some patches to QOM'ify dp8393x.
> Those are available at
> http://repo.or.cz/w/qemu/hpoussin.git/shortlog/refs/heads/sonic
> 
> Main differences are:
> - dp8393x uses an AddressSpace, instead of an offset in a MemoryRegion
> in yours
> - no PROM support, but should be easy to add
> - rc4030 (MIPS Jazz chipset) also converted to QOM (but that was not the
> goal of your patch series)
> 
> Minor points are:
> - have load/save support
> - all functions have the same dp8393x_ prefix
> - old_mmio-style functions are not used anymore
> 
> What do you think of them?

I don't know if it's a good idea to use AddressSpace into device. For
me, AddressSpace must stay in the machine definition. SysBus is there
for that. But it seems to be a good way to do DMA. I have to think about
that...

As I use the dp8393x with a quadra 800 implementation, I don't want to
work on rc4030 part, and I need the PROM and the register offset (but as
you said it is easy to add).

Except for this particular patch I like all the other dp8393x patches.

What I propose is to steal these patches (except the QOM one) and
include them in my series with the modifications done according comments
from Andreas (and perhaps something about the address space, i.e your
patch...). Your comments will be welcome.

Regards,
Laurent






[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-01-02  1:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29  0:39 [Qemu-devel] [PATCH 0/3] dp8393x update Laurent Vivier
2014-12-29  0:39 ` [Qemu-devel] [PATCH 1/3] dp8393x: add registers offset Laurent Vivier
2014-12-29  0:39 ` [Qemu-devel] [PATCH 2/3] dp8393x: add PROM to store MAC address Laurent Vivier
2014-12-29  0:39 ` [Qemu-devel] [PATCH 3/3] qdev'ify dp8393x Laurent Vivier
2015-01-01 16:15   ` Andreas Färber
2015-01-01 17:32     ` Laurent Vivier
2015-01-01 21:01 ` [Qemu-devel] [PATCH 0/3] dp8393x update Hervé Poussineau
2015-01-02  1:34   ` Laurent Vivier [this message]
2015-01-02  9:25     ` Laurent Vivier
2015-01-02 10:19       ` Peter Maydell
2015-01-02 11:33         ` Laurent Vivier
2015-01-02 12:31           ` Peter Maydell

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=54A5F5C0.4030402@Vivier.EU \
    --to=laurent@vivier.eu \
    --cc=aurelien@aurel32.net \
    --cc=hpoussin@reactos.org \
    --cc=leon.alrae@imgtec.com \
    --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).