From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Anderson <scott_anderson@mvista.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
Armin Kuster <akuster@mvista.com>,
linuxppc-embedded@lists.linuxppc.org,
Paul Mackerras <paulus@samba.org>
Subject: Re: Trivial cleanup in ocp_uart.c
Date: Fri, 28 Jun 2002 10:59:08 +1000 [thread overview]
Message-ID: <20020628005908.GC11095@zax> (raw)
In-Reply-To: <3D1B3C0D.9B36EB42@mvista.com>
On Thu, Jun 27, 2002 at 09:23:41AM -0700, Scott Anderson wrote:
>
> David Gibson wrote:
> > Eek, wibble. It still seems somewhat unlikely to me that you'd be
> > changing the peripherals "on the fly" in a real life embedded
> > application. Especially considering that reboots are likely to be
> > much less of an issue on an embedded system than on a big server.
>
> My contrived example is a piece of test equipment that has an LCD
> touchscreen and some high speed serial collection device. The LCD is
> only used when interacting with the UI and the serial is only used
> during a run when the LCD can be blank. By reprogramming part of the
> FPGA on the fly you can squeeze more into a smaller FPGA. It appears
> that Xilinx already has this working:
> http://www.xilinx.com/xapp/xapp290.pdf
>
> I guess I wouldn't be quite so quick to dismiss this as unlikely, but
> I must admit, my crystal ball is in the shop this week. It sure would
> be nice to keep such things in mind as OCP is evolving, though.
Heh, well, maybe. In any case this sounds more like a 2.5 and later
timerframe thing to me, in which case integration into the unified
device model should give us what's needed.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-28 0:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 7:34 Trivial cleanup in ocp_uart.c David Gibson
2002-06-20 15:50 ` Tom Rini
2002-06-21 0:52 ` David Gibson
2002-06-21 14:39 ` Tom Rini
2002-06-24 7:40 ` David Gibson
2002-06-26 17:27 ` Scott Anderson
2002-06-27 0:41 ` David Gibson
2002-06-27 16:23 ` Scott Anderson
2002-06-27 16:52 ` Kenneth Johansson
2002-06-28 0:59 ` David Gibson [this message]
2002-06-28 14:57 ` Tom Rini
2002-06-27 21:21 ` Armin Kuster
2002-06-27 20:30 ` Paul Mackerras
2002-06-27 21:12 ` Kenneth Johansson
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=20020628005908.GC11095@zax \
--to=david@gibson.dropbear.id.au \
--cc=akuster@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=scott_anderson@mvista.com \
--cc=trini@kernel.crashing.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).