From: "Blue Swirl" <blauwirbel@gmail.com>
To: dsilvers@simtec.co.uk, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] DM9000 network card driver
Date: Tue, 11 Nov 2008 20:01:28 +0200 [thread overview]
Message-ID: <f43fc5580811111001h36e1f281l4a09c7ff1e3a6d9d@mail.gmail.com> (raw)
In-Reply-To: <1226402471.14868.5.camel@petitemort>
On 11/11/08, Daniel Silverstone <dsilvers@simtec.co.uk> wrote:
> On Mon, 2008-11-10 at 18:47 +0200, Blue Swirl wrote:
> > > I appreciate that you're all busy, so if the answer is simply "You're on
> > > the list, just it'll be a while" then at least I can carry that back to
> > > my boss who wants to know how it's going getting these patches to you.
>
> > Your patch looks very clean. I wouldn't use devices.h for the
> > prototype, but instead some board file (for example arm-misc.h).
>
>
> I think I was told to use devices.h quite a while back. It's not
> appropriate to put it in arm-misc.h since the device itself has no
> specific isolation in ARM stuff. Despite being made to put the HW in the
> ARM HW bits of the Makefile.
I see. Then devices.h seems correct. I was wondering about NEED_CPU stuff.
> > The device is not used by any board, so it's not possible even for the
> > maintainer to test the patch.
>
>
> It is used by the board I am trying to get all the patches up-to-snuff
> for.
Maybe you could add it as an ISA device to PC (pc.c) and see if it works?
> > As there is a reset function already, it should not be too difficult
> > to register that for system_reset use.
>
>
> Can you explain what you mean by that?
Just add a line like
qemu_register_reset(dm9000_hard_reset, state);
to dm9000_init().
Then if the machine gets reset by monitor command "system_reset" or a
hardware device, the reset function will be called to make the device
state predictable like on a real machine.
prev parent reply other threads:[~2008-11-11 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 10:49 [Qemu-devel] [PATCH] DM9000 network card driver Daniel Silverstone
2008-11-10 10:31 ` Daniel Silverstone
2008-11-10 16:47 ` Blue Swirl
2008-11-11 11:21 ` Daniel Silverstone
2008-11-11 18:01 ` Blue Swirl [this message]
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=f43fc5580811111001h36e1f281l4a09c7ff1e3a6d9d@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=dsilvers@simtec.co.uk \
--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).