From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: keir.fraser@cl.cam.ac.uk, xen-devel@lists.xensource.com
Subject: Re: latest USB code including Xenidc documentation
Date: Mon, 19 Dec 2005 10:54:11 +0000 [thread overview]
Message-ID: <1134989651.5070.6.camel@localhost> (raw)
In-Reply-To: <20051217081617.GK14690@granada.merseine.nu>
On Sat, 2005-12-17 at 10:16 +0200, Muli Ben-Yehuda wrote:
> > Do you think it's worthwhile to try
> > to achieve a high level inter-domain communication API which allows
> > different split drivers to reuse the channel set-up, messaging,
> > interrupt handling, flow-control and bulk data transfer code?
>
> Yes. But I'd like to see it developed and integrated piece by piece,
> as a natural evolution of the existing code.
If you churn the existing code by integrating a lot of incremental
changes across all the drivers it may introduce significant instability
and prevent other development from proceeding. An alternative approach
would be to provide the infrastructure on the side and port the drivers
to it one by one. That way the old and new versions of drivers could
coexist in the tree which would allow other developers to use the old,
stable set until the new ones were finished.
Just a thought.
--
Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
prev parent reply other threads:[~2005-12-19 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 16:51 latest USB code including Xenidc documentation Harry Butterworth
2005-12-16 17:01 ` Muli Ben-Yehuda
2005-12-16 17:23 ` Harry Butterworth
2005-12-16 17:38 ` Muli Ben-Yehuda
2005-12-16 19:00 ` Harry Butterworth
2005-12-16 20:13 ` Anthony Liguori
2005-12-16 20:45 ` Harry Butterworth
2005-12-17 8:16 ` Muli Ben-Yehuda
2005-12-19 10:54 ` Harry Butterworth [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=1134989651.5070.6.camel@localhost \
--to=harry@hebutterworth.freeserve.co.uk \
--cc=keir.fraser@cl.cam.ac.uk \
--cc=mulix@mulix.org \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.