public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: Debian m68k <debian-68k@lists.debian.org>, linux-m68k@vger.kernel.org
Subject: Re: atafb and X/fbdev
Date: Sun, 08 Jul 2012 15:47:40 +1200	[thread overview]
Message-ID: <4FF902DC.4010208@gmail.com> (raw)
In-Reply-To: <Pine.BSM.4.64L.1207070751590.7146@herc.mirbsd.org>

Thorsten,
>> Have you tried the VGA modes (vga256 for instance)? That might boil down to
>> interleaved planes in the end though.
>>     
>
> Yes, vgs256 was interleaved too. From my limited understanding of
> atafb.c all modes are interleaved or monochrome.
>   

That's the way the Falcon VIDEL is wired up then.

>> You will have to go back to one of the earlier Debian releases (slink or
>> potato) for Atari support in the X server. potato should still have the
>> required code.
>>     
>
> Hrm, okay. I couldn’t find much in the ’net except a reference to
> xfree68 but was unable to find that, either. Too bad, all the history…
>   

Seaching for "xfree86 fbdev server m68k" does refresh my memory a bit -
the server package was called xserver-fbdev and you will find a sample 
config
file at http://people.debian.org/~cts/debian-m68k/slink/XF86Config - 
Christian is
away overseas ATM or else he might be able to give a few hints here.

The entry

    Driver      "FBDev"


in the 'Screen' section is what directs xfree86 to use the generic frame 
buffer server.
> you don’t happen to know the _package_ name of the server, and the
> needed config? ;-)
>
>   

See above - it's xserver-fbdev, IIRC version 3.3.6 was the last to work. 
Also take a look at 
http://people.debian.org/~cts/debian-m68k/slink/debian-m68k-faq
for a few likely X troubleshooting hints.

Blast from the past really - I never had much fun running X on my 
(unaccelerated) Falcon
mainly because the system became really unstable at high resolution or 
color depth.
Waiting for 10 minutes while the X server starts up was a bit annoying, 
too.

Are you trying to get the old X server running in ARAnyM, or 'just' port 
the interleaved bit
planes code to current Xorg? If it's questions on the framebuffer memory 
layout and the VIDEL
that you need answered, Andreas and Petr might be better suited here. 
Regarding building
xfree from source - that's memories well suppressed which do not bear 
recalling.

Cheers,

  Michael

  parent reply	other threads:[~2012-07-08  3:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 23:03 atafb and X/fbdev Thorsten Glaser
2012-07-07  3:41 ` schmitz
2012-07-07  7:54   ` Thorsten Glaser
2012-07-07  8:06     ` Geert Uytterhoeven
2012-07-07  9:18       ` Thorsten Glaser
2012-07-07 15:38         ` Thorsten Glaser
2012-07-08  4:38           ` Michael Schmitz
2012-07-10 22:57             ` Michael Schmitz
2012-07-14  3:42               ` Michael Schmitz
2012-07-14  8:44                 ` Geert Uytterhoeven
2012-07-15  7:12                   ` Michael Schmitz
2012-07-15  8:49                     ` Geert Uytterhoeven
2012-07-17  2:59                       ` Michael Schmitz
2012-07-08  3:47     ` Michael Schmitz [this message]
2012-07-08 19:09       ` Christian T. Steigies

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=4FF902DC.4010208@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=debian-68k@lists.debian.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@mirbsd.de \
    /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