linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: "Shuangjun Zhu (r44089)" <r44089@email.sps.mot.com>
Cc: linuxppc-dev@lists.linuxppc.org, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Help about device driver in Linux
Date: Tue, 28 Dec 1999 12:35:39 -0500	[thread overview]
Message-ID: <3868F4EB.498E3466@netx4.com> (raw)
In-Reply-To: 004a01bf50df$312fab80$70f102de@sjzhu


Shuangjun Zhu wrote:

> I want to make two device driver for MPC823,
> one is for MPC823 Video, one is for MPC IIC.


Both of these exist in the 2.2.13 kernel on ppc.kernel.org.
I regularly use the video driver for LCDs.  It is pretty trivial,
just initializes the 823 and you can mmap() the frame buffer.
There is an ioctl() to set the color map.  I don't know what
to do with it from here, it works well enough for demos and
some custom software I have written.

There are some (relatively) undocumented features to set
aggressive mode display updates, don't mess this up or the
PPC core won't make any progress.  This code works equally
well on the 823 and 823e.  It will not work on the 821.


> Because in the Video driver, it must write configuration
> parameters to the video controller through the IIC driver.

I normally let the application program do this.  We can argue all
day about whether the video driver should have this knowledge, but
it is clearly easier if the application does it.



	-- Dan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-12-28 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-28  2:56 Help about device driver in Linux Shuangjun Zhu
1999-12-28 17:35 ` Dan Malek [this message]
     [not found] <OF9209481E.5CD82FF1-ON00256855.00326F88@flaga.is>
1999-12-28 16:53 ` Dan Malek

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=3868F4EB.498E3466@netx4.com \
    --to=dan@netx4.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=r44089@email.sps.mot.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 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).