From: Johan Bolmsjo <johan@nocrew.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: status
Date: 25 Nov 2002 22:35:52 +0100 [thread overview]
Message-ID: <1038260153.1027.26.camel@skalman> (raw)
In-Reply-To: <Pine.LNX.4.44.0211251832200.22897-100000@phoenix.infradead.org>
mån 2002-11-25 klockan 19.47 skrev James Simmons:
>
> > > Geert is busy porting the Amigia driver to the new api. That means all the
> > > ilbm, iplan stuff will go away :-)
> >
> > I have first code for amifb, but it doesn't work yet, due to other problems
> > with 2.5.x on Amiga. I hope to fix these tomorrow...
>
> Yeah!!!
>
> > Besides, we still need someone to take care of the Atari 2-byte interleaved
> > bitplanes (iplan2p*), since I don't have the hardware, and am not 100% sure
> > how they work. But reviving 2.5.x on Atari will be even harder...
For what it's worth, the interleaved modes on atari works like this:
The bitplanes are interleaved on 16 bit big-endian word basis so if you
have two bitplanes, bit 0 of the first 16 pixels would be in the first
16 bit word in the display memory, bit 1 of the first 16 pixels would be
in the second word. With bit 0 I mean as masked out by & 0x0001 in C,
and bit 1 as masked out by 0x0002.
The Atari ST line support three resolutions by default:
320x200 4 bit planes
640x200 2 bit planes
640x400 1 bit plane
The Atari Falcon has a programmable clock so many resolutions are
possible and it also features a 8 bit planes mode and 16 bit high colour
mode.
P.S.
I don't have any Atari hardware myself anymore.
> Me neither. But there is a way to find out. A trick I used to figure
> out the hga framebuffer lay out. Build just the fbdev layer without fbcon.
> Then do a write to /dev/fbX to see what happens.
> The way I have fbdev now is when you open /dev/fb0 the hardware mode is
> set. When you close the /dev/fb the hardware goes back to text mode. I did
> it this way so you could insmod the driver and NOT change the hardware
> state. Also fb_open is the function register_framebuffer needs just before
> take_over_console happens. The other benifiet is if X dies that uses
> /dev/fb to set it modes then the file will be closed automatically and teh
> hardware state will be set to a sane state. This is for the case of vgacon
> with fbdev. WHat about from fbco? Well that is easy since fb_open passes a
> falg to let us knwo if it is from userland for fbcon.
>
> P.S
> It appears fbcon is totally broken in BK. I'm using the above trick to
> test the code. Tonight I'm going to work on making fbcon completely
> modular. Yeah!!!!
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
next prev parent reply other threads:[~2002-11-25 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 17:52 status James Simmons
2002-11-22 21:45 ` status Antonino Daplas
2002-11-22 19:04 ` status James Simmons
2002-11-22 22:12 ` status Antonino Daplas
2002-11-22 22:57 ` status Antonino Daplas
2002-11-23 21:07 ` status Geert Uytterhoeven
2002-11-25 18:47 ` James Simmons
2002-11-25 21:35 ` Johan Bolmsjo [this message]
2002-11-26 0:39 ` James Simmons
2002-11-27 23:02 ` Geert Uytterhoeven
2002-12-08 11:47 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2002-11-28 12:24 Szymanski, Frank-Peter
2002-11-28 12:32 ` Geert Uytterhoeven
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=1038260153.1027.26.camel@skalman \
--to=johan@nocrew.org \
--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).