linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Smart LCD Linux driver
Date: Fri, 2 Jul 2004 13:43:24 +0200	[thread overview]
Message-ID: <20040702114323.GE18841@lug-owl.de> (raw)
In-Reply-To: <DC91351678E31E4FB24B551221F507ECB771E4@blr-itp-msg.wipro.com>

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

On Fri, 2004-07-02 16:50:44 +0530, kiran.tigadi@wipro.com <kiran.tigadi@wipro.com>
wrote in message <DC91351678E31E4FB24B551221F507ECB771E4@blr-itp-msg.wipro.com>:
> Hi,
>  
> I am working on Smart LCD Linux driver interfaced Asynchronous Display
> controller. I want info in this regard.

Asynchronous display controller? Attached via a serial link (or by other
means), but no shared video RAM?

That's one of the more complicated drivers then... You'd need to prepare
some buffer you can provide to the FB API and poll it for changes, which
you then need to hammer down to your display controller.

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-02 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02 11:20 Smart LCD Linux driver kiran.tigadi
2004-07-02 11:43 ` Jan-Benedict Glaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-02 13:46 kiran.tigadi
2004-07-04 19:41 ` Jan-Benedict Glaw

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=20040702114323.GE18841@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).