SUMMARY: Configuring frame buffer board (PMAGD-BA / ZLX-E2)

From: Kim Greer <klg_at_dec4.mc.duke.edu>
Date: Fri, 05 Jun 1998 09:55:03 -0400 (EDT)

I had a question about the configuring of a new frame buffer
into the kernel, which was quickly and correctly answered by
Oisin McGuinness <oisin_at_sbcm.com>. I include his answer, in
its entirety, below. To summarize his answer:

   1) use a generic configuration entry:
        controller fb1 at * slot ? vector fbint

        or,
       use a specific configuration:
        controller fb1 at tc0 slot 2 vector fbint

   2) generate new kernel and reboot

   3) "As regards the X setup, once you get X running, the DISPLAY variable
        should be machinename:0.1"


Thanks Oisin!!

KG


Kim L. Greer klg_at_dec3.mc.duke.edu
Duke University Medical Center voice: 919-684-7223
Div. Nuclear Medicine POB DUMC-3949 fax: 919-684-7123
Durham, NC 27710



------begin reply from Oisin McGuinness <oisin_at_sbcm.com>---------

You could boot with genvmunix to detect exactly what lines to add to the kernel config
file. But it is more fun to work it out:

If you look at /sys/data/tc_option_data.c, there is are lines that look like:
    { "PMAGD ", "fb", 0, 1, 'C', 0}, /* SFBP-8,-32,-32Z */
    { "PMAGD-AA", "fb", 0, 1, 'C', 0}, /* SFBP-8 */
    { "PMAGD-BA", "fb", 0, 1, 'C', 0}, /* SFBP-32 */
(this is from 4.0D system), so your card should get recognized as "fb",
and these lines from the GENERIC kernel config,

controller fb0 at * slot ? vector fbint
controller fb1 at * slot ? vector fbint
etc.
suggest to me that adding the line (more precise than the GENERIC version) to
your config file:

controller fb1 at tc0 slot 2 vector fbint

will do the job.

As regards the X setup, once you get X running, the DISPLAY variable should be
machinename:0.1


>From "man X":

>From the user's prospective, every X server has a display name of the form:

       hostname:displaynumber.screennumber

  This information is used by the application to determine how it should con-
  nect to the server and which screen it should use by default (on displays
  with multiple monitors):

  hostname
      The hostname specifies the name of the machine to which the display is
      physically connected. If the hostname is not given, the most efficient
      way of communicating to a server on the same machine will be used.

  displaynumber
      The phrase "display" is usually used to refer to collection of monitors
      that share a common keyboard and pointer (mouse, tablet, and so
      forth.). Most workstations tend to only have one keyboard, and there-
      fore, only one display. Larger, multi-user systems, however, fre-
      quently have several displays so that more than one person can be doing
      graphics work at once. To avoid confusion, each display on a machine
      is assigned a display number (beginning at 0) when the X server for
      that display is started. The display number must always be given in a
      display name.

  screennumber
      Some displays share a single keyboard and pointer among two or more
      monitors. Since each monitor has its own set of windows, each screen is
      assigned a screen number (beginning at 0) when the X server for that
      display is started. If the screen number is not given, screen 0 will
      be used.

(end of excerpt from man X)


I'm not sure how to do the X setup in this situation. It partly depends whether you run XDM
or CDE. For Xdm, see the file Xservers in /usr/lib/X11/xdm/.

On Ultrix (remember that?) one gave
parameters like
"/usr/bin/Xws -bs -edge_right1 0 -edge_left0 1"
to describe to the X server how to attach the right edge of screen 0 to the left edge of screen 1
to allow the mouse to move transparently from 1 screen to the other.

There are also fancy X clients that allow you to actually move applications from 1 screen to another
,
but in general, if you start a client on 1 screen, there it stays.


Oisin McGuinness

Sumitomo Bank Capital Markets
277 Park Avenue
New York NY 10172
USA

(212)-224-4913, email: oisin_at_sbcm.com

-------end of reply----------
Received on Fri Jun 05 1998 - 15:56:38 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:37 NZDT