From: linas@austin.ibm.com (Linas Vepstas)
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 5/7] Celleb: Supports VFD on Celleb 2
Date: Thu, 27 Sep 2007 11:54:12 -0500 [thread overview]
Message-ID: <20070927165412.GD7970@austin.ibm.com> (raw)
In-Reply-To: <200709271107.33696.arnd@arndb.de>
On Thu, Sep 27, 2007 at 11:07:33AM +0200, Arnd Bergmann wrote:
> On Thursday 27 September 2007, Ishizaki Kou wrote:
> > This is a patch to support VFD on Celleb 2.
> > VFD is a small LCD to show miscellaneous messages.
> >
> > Signed-off-by: Kou Ishizaki <Kou.Ishizaki@toshiba.co.jp>
>
> My feeling is that your interface should better be
> implemented as a character device, or be integrating into some other
> existing message interface, if we can find one.
>
> * The firmware seems to implement the generic rtas interface for
> display-character and set-indicator, but your driver is celleb specific.
> I'd be feel more comfortable if we could come up with a driver that also
> works on other systems that implement the same rtas calls.
Yep, I think I agree. Most pseries systems have a small two-line
LCD display. Right now, the code that talks to it is implemented in
rtas_progress(). It has this name because its used only for printing
out boot progress messages. This is great for debugging hangs, but
its not othrewise used.
I suppose it would be nice to have a "geeric" interface to the thing,
and, after a quickie skim of the code, the celleb display looks similar
enogh that this abstraction could be made.
--linas
prev parent reply other threads:[~2007-09-27 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 7:56 [PATCH 5/7] Celleb: Supports VFD on Celleb 2 Ishizaki Kou
2007-09-27 9:07 ` Arnd Bergmann
2007-09-27 16:54 ` Linas Vepstas [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=20070927165412.GD7970@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).