From: Thomas H?henleitner <th@visuelle-maschinen.de>
To: Adrian Cox <apc@agelectronics.co.uk>, th@visuelle-maschinen.de
Cc: Linux Frame Buffer Device Development
<linux-fbdev@vuser.vu.union.edu>,
LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: CTFB 0.30 now availiable (CT65554...CT69000)
Date: Mon, 19 Jun 2000 19:31:06 +0200 [thread overview]
Message-ID: <00061919325606.10856@iris> (raw)
In-Reply-To: <394DFFEF.162E7785@agelectronics.co.uk>
Am Mon, 19 Jun 2000 schrieb Adrian Cox:
> Thomas Hhenleitner wrote:
> >
> > The driver works now quite well with my hw.
> >
> > Check the ctfb_README for limits and features.
> >
> > What about a merge with the old chipsfb.o?
>
> I'm working on my 69030 driver as a separate driver currently, because
> of the requirement to use memory mapped IO and avoid all fixed IO
> addresses, which makes it incompatible with the 65550. I did look at
> your driver, but I decided to base mine on the existing chipsfb.c
> because I needed PowerPC support, and because the coding style of your
> driver was quite different to existing frame buffer drivers.
>
> My priorities are:
> 1) Not assume any BIOS setup, as BIOS setup only occurs on x86 hosts,
> and only on the primary display.
> 2) Avoid use of the big-endian region in the chip, while still
> supporting big-endian hosts. This is necessary to support the
> twin-pipeline mode of the 69030 in future.
> 3) Support multiple displays. This requires use of memory mapping.
>
> - Adrian Cox, AG Electronics
Where can I get the source of your driver to have a look at it?
Is the CT69030 availiable? The last I heard about it was, that it was cacelled.
Thomas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-19 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-16 9:31 copy_from_user in drivers/video/fbmem.c Adrian Cox
2000-06-16 11:14 ` Geert Uytterhoeven
2000-06-16 14:04 ` [linux-fbdev] " James Simmons
2000-06-19 10:15 ` CTFB 0.30 now availiable (CT65554...CT69000) Thomas H?henleitner
2000-06-19 11:11 ` Adrian Cox
2000-06-19 17:31 ` Thomas H?henleitner [this message]
2000-06-19 14:12 ` [linux-fbdev] " James Simmons
2000-06-19 14:28 ` Geert Uytterhoeven
2000-06-19 14:41 ` James Simmons
2000-06-19 17:27 ` Thomas H?henleitner
2000-06-19 19:11 ` James Simmons
2000-06-20 9:03 ` name space pollution Was " Thomas H?henleitner
2000-06-20 23:40 ` James Simmons
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=00061919325606.10856@iris \
--to=th@visuelle-maschinen.de \
--cc=apc@agelectronics.co.uk \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linuxppc-dev@lists.linuxppc.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).