From: "Blue Swirl" <blauwirbel@gmail.com>
To: l_indien@magic.fr, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/hw pckbd.c
Date: Wed, 18 Apr 2007 18:37:36 +0300 [thread overview]
Message-ID: <f43fc5580704180837o1c9c0a3exf975d657218a1d2f@mail.gmail.com> (raw)
In-Reply-To: <1176906055.16811.24.camel@jma4.dev.netgem.com>
On 4/18/07, Jocelyn Mayer <l_indien@magic.fr> wrote:
> On Wed, 2007-04-18 at 14:06 +0100, Thiemo Seufer wrote:
> > J. Mayer wrote:
> > > On Mon, 2007-04-16 at 22:47 +0000, Thiemo Seufer wrote:
> > > > CVSROOT: /sources/qemu
> > > > Module name: qemu
> > > > Changes by: Thiemo Seufer <ths> 07/04/16 22:47:54
> > > >
> > > > Modified files:
> > > > hw : pckbd.c
> > > >
> > > > Log message:
> > > > Support it_shift for mmapped pckbd.
> > > >
> > > > CVSWeb URLs:
> > > > http://cvs.savannah.gnu.org/viewcvs/qemu/hw/pckbd.c?cvsroot=qemu&r1=1.19&r2=1.20
> > >
> > > Thanks for the update.
> > > Here's another small patch, based on the same idea of what is done for
> > > the memory-mapped serial ports and which seems useful to implement some
> > > targets: it may be needed not to register the I/O memory area in the
> > > pckbd driver but let the caller do it.
> > > Please take a look.
> >
> > Actually, I thought about adding such a feature but then decided to
> > defer it until it is actually needed. OTOH, with qemu handling mmio
> > at page granularity it is likely needed sooner or later, so we could
> > just declare it a standard implementation feature. I am ok with it
> > either way.
>
> If you're interressed in such a feature, you may take a look of what
> I've done in hw/ppc405_uc.c. There are some device sharing the same
> memory page on those microcontrollers so I introduced a fake device
> called mmio that allow to register multiple devices into a single page
> in Qemu. I do use the serial_mm_init with the ioregister parameter set
> to 0 for those designs.
> This code may not be as generic as it would be if we want to make it a
> standard Qemu function, but this may give a basis or ideas for it.
On Sparc32 there are several devices that would benefit from sub-page
granularity, so I vote for making this generic.
next prev parent reply other threads:[~2007-04-18 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 22:47 [Qemu-devel] qemu/hw pckbd.c Thiemo Seufer
2007-04-18 9:29 ` J. Mayer
2007-04-18 13:06 ` Thiemo Seufer
2007-04-18 14:20 ` Jocelyn Mayer
2007-04-18 15:37 ` Blue Swirl [this message]
2007-04-18 16:08 ` Paul Brook
2007-04-19 8:43 ` J. Mayer
2007-04-19 14:44 ` Paul Brook
2007-04-19 18:15 ` Blue Swirl
-- strict thread matches above, loose matches on Subject: below --
2008-02-10 13:39 Andrzej Zaborowski
2007-10-20 20:48 Thiemo Seufer
2007-02-18 0:08 Thiemo Seufer
2005-01-27 22:32 Fabrice Bellard
2005-01-17 22:31 Fabrice Bellard
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=f43fc5580704180837o1c9c0a3exf975d657218a1d2f@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=l_indien@magic.fr \
--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).