VPro V12 and oddball 1280x1440 resolution?

SGI hardware problems, solutions, tips, hacks, etc.
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
User avatar
jan-jaap
Donor
Donor
Posts: 4881
Joined: Thu Jun 17, 2004 11:35 am
Location: Wijchen, The Netherlands
Contact:

VPro V12 and oddball 1280x1440 resolution?

Unread postby jan-jaap » Wed Sep 28, 2016 5:11 am

I'm looking for a new PC monitor and the NEC EA275WMi is on my shortlist. This is a 27" 2560x1440 screen. It happens to support an interesting feature called 'picture by picture', where it displays two sources side by side:
side-by-side.jpg

In general, the native resolution of any screen I'd consider buying in 2016 is higher than what any SGI can put out (1920x1200), but most SGIs with DVI have multiple outputs to make up for this.

You can see where this is going :D

Apparently, in the image shown above, each "computer" sees a 1280x1440 screen. What are my chances of squeezing twice 1280x1440 out of a V12 with DCD?
:PI: :Indigo: :Indigo: :Indy: :Indy: :Indy: :Indigo2: :Indigo2: :Indigo2IMP: :Octane: :Octane2: :O2: :O2+: Image :Fuel: :Tezro: :4D70G: :Skywriter: :PWRSeries: :Crimson: :ChallengeL: :Onyx: :O200: :Onyx2: :O3x02L:
To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. (IRIS 4D/70 Superworkstation Technical Report)

User avatar
Geoman
Donor
Donor
Posts: 825
Joined: Thu May 26, 2005 3:37 am
Location: Munich, Germany
Contact:

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby Geoman » Wed Sep 28, 2016 8:25 am

I remember that Hamei has a dual V12 with DCDs running an IBM T221, at 3840×2400. That is 4x 960X2400.

You would need that beauty here: http://forums.nekochan.net/viewtopic.php?f=14&t=16730279&hilit=dual+head+v12

EDIT

jan-jaap wrote:What are my chances of squeezing twice 1280x1440 out of a V12 with DCD?

therefor one DCD V12 should do 2x960X2400 which is 2400x1920. So the chances are good.
:Indy: :O2: :O2: :Indigo: :Indigo2IMP: :Octane: :Octane2: :Octane2:
SGI - the legend will never die!!

User avatar
uunix
Donor
Donor
Posts: 1795
Joined: Sun Mar 27, 2011 12:48 pm
Location: Stourbridge / England / UK

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby uunix » Wed Sep 28, 2016 8:54 am

I have an LG TV that does the screen split also, I've used it with a mac, but that was some time ago, I only use it as a very wide TV currently.
-----------------------------------------------------------------------
Hey Ho! Pip & Dandy!
:Octane2: :O2: :Indigo: :Indy:
-----------------------------------------------------------------------

User avatar
jan-jaap
Donor
Donor
Posts: 4881
Joined: Thu Jun 17, 2004 11:35 am
Location: Wijchen, The Netherlands
Contact:

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby jan-jaap » Wed Sep 28, 2016 12:25 pm

Geoman wrote:I remember that Hamei has a dual V12 with DCDs running an IBM T221, at 3840×2400. That is 4x 960X2400

I think it's more likely 4x 1920x1200 ... I'm a bit worried about the vertical resolution of 1440 lines, which is beyond any of the standard modes
:PI: :Indigo: :Indigo: :Indy: :Indy: :Indy: :Indigo2: :Indigo2: :Indigo2IMP: :Octane: :Octane2: :O2: :O2+: Image :Fuel: :Tezro: :4D70G: :Skywriter: :PWRSeries: :Crimson: :ChallengeL: :Onyx: :O200: :Onyx2: :O3x02L:
To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. (IRIS 4D/70 Superworkstation Technical Report)

User avatar
archaic
Posts: 354
Joined: Mon Mar 08, 2004 9:28 pm
Location: Houston, TX

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby archaic » Wed Sep 28, 2016 3:12 pm

jan-jaap wrote:
Geoman wrote:I remember that Hamei has a dual V12 with DCDs running an IBM T221, at 3840×2400. That is 4x 960X2400

I think it's more likely 4x 1920x1200 ... I'm a bit worried about the vertical resolution of 1440 lines, which is beyond any of the standard modes



You might check out some of the monitor format files on Linux to get close to the data you're going to need to make a custom vfo file. (Front porch, back porch, etc.). There used to be somebody here that was good with custom resolutions who made me a vfo of 2048x1152 to run on my old fuel.
Patrick

- You have got to be kidding... -

User avatar
vishnu
Donor
Donor
Posts: 3174
Joined: Sun Mar 18, 2007 3:25 pm
Location: Minneapolis, Minnesota USA

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby vishnu » Wed Sep 28, 2016 3:27 pm

archaic wrote:There used to be somebody here that was good with custom resolutions who made me a vfo of 2048x1152 to run on my old fuel.


recondas...
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...

:Tezro: :Octane2:

User avatar
recondas
Moderator
Moderator
Posts: 5441
Joined: Sun Jun 06, 2004 5:55 pm
Location: NC - USA

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby recondas » Sat Oct 01, 2016 4:35 pm

jan-jaap wrote:I'm looking for a new PC monitor and the NEC EA275WMi is on my shortlist. This is a 27" 2560x1440 screen. It happens to support an interesting feature called 'picture by picture', where it displays two sources side by side.....In general, the native resolution of any screen I'd consider buying in 2016 is higher than what any SGI can put out (1920x1200), but most SGIs with DVI have multiple outputs to make up for this.

Apparently, in the image shown above, each "computer" sees a 1280x1440 screen. What are my chances of squeezing twice 1280x1440 out of a V12 with DCD?

I couldn't find any specifics on the timing used by the EA275WMi while in 1280x1440 mode, but I was able to google up a *generic* 1280x1440 modeline:

Code: Select all

"1280x1440_59.9"  156.00  1280 1376 1512 1744  1440 1443 1453 1493 -hsync +vsync
The 156MHz pixel clock on that one came in under the V12's 165MHz single-link DVI threshold, so if the timing for the EA275WMi is similar, and the DCD will play nice with the DVI-to-Display_Port conversion, it *might* be possible.


I went ahead and ran a test using the timing from the generic modeline. It successfully created micro-code.:

Code: Select all

% make 1280x1440_59.9_modeline.vfo
--- 1280x1440_59.9_modeline.vfo ---
        /usr/sbin/vfc  -a ascii=1280x1440_59.9_modeline.info
        -c chip=/usr/gfx/ucode/vfc/rules/VPro_Chip.def,board=/usr/gfx/ucode/vfc/rules/VPro_Board.def 
        -o 1280x1440_59.9_modeline.vfo 1280x1440_59.9_modeline.vfs
DesiredFrequency is 155.967141
   Setting frequency to 155.967153MHz
       Feedback divider = 14245
       Reference divider = 1096
       Post Scaler divider = 1
         Error is 0.080047
Resetting FramesPerSecond from 59.900000 to 59.900005.
g_HorizontalSync_P  0
g_DesiredFrequency  155.967141
g_ActiveLinesPerFrame  1440
g_FramesPerSecond  59.900005
g_TotalLinesPerFrame  1493
g_TotalPixelsPerLine  1744

FR_delay 0

HSYNC_freq 89
N_post 1
VCOSPD 0
sqrt_A 2.435843
I_pump 19.364608
MLCP 3

genlock register values
ODY_GEN_hPFD  1
ODY_GEN_lPFD  -16252918
ODY_GEN_hPFD_HI  0
ODY_GEN_hPFD_LO  0
ODY_GEN_lPFD_HI  0
ODY_GEN_lPFD_LO  0
ODY_GEN_hPSD  1840
ODY_GEN_lPSD  521702
ODY_GEN_hHMASK  10368
ODY_GEN_lHMASK  452985530
ODY_GEN_BP_CLAMP  55
ODY_GENLOCK  0
ODY_GEN_CONTROL  0
Here's a copy of the info file spawned during the build process:

Code: Select all

1280x1440_59.9_modeline.vfo:
 Total lines per frame:   1493
 Total pixels per line:   1744
 Active lines per frame:  1440
 Active pixels per line:  1280
 Frames per second:       59.9
 Fields per frame:        1
 Swaps per frame:         1
 Pixel clock:             155.967 MHz, period = 6.41161 nsec
 Hardware pixel rounding:  every 1 pixels
 Line analysis:
  Length:                 1744 Pixels, 1 Lines, 11.1818 usec; (line 0)
  Frequency:              89.4307 KHz, period = 11.1818 usec
 Horizontal Sync:         136 Pixels, 871.978 nsec; (line 50)
 Horizontal Back Porch:   232 Pixels, 1.48749 usec; (line 50)
 Horizontal Active:       1280 Pixels, 8.20686 usec; (line 50)
 Horizontal Front Porch:  96 Pixels, 615.514 nsec; (line 50)
 Field Information:
  Field Duration:           2.60379e+06 Pixels, 1493 Lines, 16.6945 msec; (line 0)
  Vertical Sync:            19184 Pixels, 11 Lines, 123 usec; (line 0)
  Vertical Sync Pulse:      19320 Pixels, 11.078 Lines, 123.872 usec; (line 0)
  Vertical Back Porch:      68016 Pixels, 39 Lines, 436.092 usec; (line 11)
  Vertical Active:          2.51136e+06 Pixels, 1440 Lines, 16.1019 msec; (line 50)
  Vertical Front Porch:     5232 Pixels, 3 Lines, 33.5455 usec; (line 1490)

In my experience display formats built from random modelines are 50/50 proposition at best, but if you'd like to give it a shot, here's the source file:

Code: Select all

/*

The generic modeline:
"1280x1440_59.9"  156.00  1280 1376 1512 1744  1440 1443 1453 1493

Modeline values sorted by name
PixClk
156.00

HDisp   HSyncStart  HSyncEnd  HTotal
 1280       1376       1512    1744

VDisp   VSyncStart  VSyncEnd  VTotal
 1440       1443       1453    1493

Calculations to obtain parameters needed by VFC.

From the horizontal portition of the modeline (HDisp HSyncStart HSyncEnd HTotal):
TotalPixelsPerLine = HTotal (1744)
HorizontalBackPorch = HTotal - HSyncEnd (1744 - 1512 = 232)
HorizontalSync = HsyncEnd - HSyncStart (1512 - 1376 = 136)
HorizontalFrontPorch = HSyncStart - HDisp (1376 - 1280 = 96)
ActivePixelsPerLine = HDisp (1280)

From the vertical portion of the modeline (VDisp VSyncStart VSyncEnd VTotal):
TotalLinesPerFrame = VTotal (1493)
VerticalBackPorch =  VTotal - VSyncEnd (1493 - 1453 = 40 - 2 = 38)
VerticalSync = VSyncEnd - VSyncStart (1453 - 1443 = 10)
VerticalFrontPorch = VSyncStart - VDisp (1443 - 1440 = 3)
ActiveLinesPerFrame = VDisp (1440)

In most cases, FieldsPerFrame will equal 1, and FramesPerSecond will be the target refresh rate.
*/

General {
    FormatName = "1280x1440_59.9";

    FieldsPerFrame          = 1;
    FramesPerSecond         = 59.9;
    TotalLinesPerFrame      = 1493;
    TotalPixelsPerLine      = 1744;
    ActiveLinesPerFrame     = 1440;
    ActivePixelsPerLine     = 1280;

}
Active Line {
    HorizontalFrontPorch    = 96 pixels;
    HorizontalSync          = 136 pixels;
    HorizontalBackPorch     = 232 pixels;
}
Field
{
    Vertical Sync =
    {
        {
            Length = 1.0H;
            Low = 0.0 usec;
        }
        repeat 10
        {
            Length = 1.0H;
        }
    }
    Initial Low;
    Vertical Back Porch =
    {
        {
            Length = 1.0H;
            High = HorizontalSync;
        }
        repeat 38
        {
            Length = 1.0H;
            Low = 0.0 usec;
            High = HorizontalSync;
        }
    }
    Initial High;
    Active =
    {
        repeat 1440
        {
            Length = 1.0H;
            Low = 0.0 usec;
            High = HorizontalSync;
        }
    }
    Vertical Front Porch =
    {
        repeat 3
        {
            Length = 1.0H;
            Low = 0.0 usec;
            High = HorizontalSync;
        }
    }
}
#if 0
    postprocess
    {
        dump edge;
    }
#endif
....and the VFO
1280x1440_59.9_modeline.vfo
(8.2 KiB) Downloaded 13 times

jan-jaap previously wrote:What are my chances of squeezing twice 1280x1440 out of a V12 with DCD?
It would make for a nice setup if used with a DCD and a 2@ format, but that's an idea probably best held in reserve until we have the timing for the EA275WMi dialed in a little closer....preferably something along the lines of an EDID read. I tried 2@1280x1440_59.9 (using the timing from generic modeline); with the overhead for the DCD transitions, the pixel clock comes in at 165.474MHz, which doesn't bode well for the single-link V12.

Hopefully the EA275WMi will have better timing and/or sync to a lower refresh rate (lowering the refresh rate of the generic modeline to 58Hz results in a 2@ format with a single-link friendly pixel clock of 162.711MHz).

Know any friendly shopkeepers that would allow you to do some in-store EA275WMi testing with an EDID-tool compatible laptop?
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

User avatar
jan-jaap
Donor
Donor
Posts: 4881
Joined: Thu Jun 17, 2004 11:35 am
Location: Wijchen, The Netherlands
Contact:

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby jan-jaap » Sun Oct 02, 2016 2:48 am

Thanks! I bought the screen so I guess we'll find out in a week or so. If it works: great, if it doesn't then it'll still work fine with my MacBook and PC.
:PI: :Indigo: :Indigo: :Indy: :Indy: :Indy: :Indigo2: :Indigo2: :Indigo2IMP: :Octane: :Octane2: :O2: :O2+: Image :Fuel: :Tezro: :4D70G: :Skywriter: :PWRSeries: :Crimson: :ChallengeL: :Onyx: :O200: :Onyx2: :O3x02L:
To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. (IRIS 4D/70 Superworkstation Technical Report)

User avatar
jan-jaap
Donor
Donor
Posts: 4881
Joined: Thu Jun 17, 2004 11:35 am
Location: Wijchen, The Netherlands
Contact:

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby jan-jaap » Fri Oct 07, 2016 12:35 am

Thanks Recondas!
recondas wrote:It would make for a nice setup if used with a DCD and a 2@ format, but that's an idea probably best held in reserve until we have the timing for the EA275WMi dialed in a little closer....preferably something along the lines of an EDID read.

I received the monitor. Had me scratching my head for a moment because I was sure my existing monitor cable was dual-link DVI-D, except of course it wasn't. Anyway, I extracted this using the Windows drivers (NVIDIA Quadro):

Code: Select all

00 ff ff ff ff ff ff 00 38 a3 a6 2b 01 01 01 01 01 1a 01 03 80 3c 22 78 ea 4b b5 a7 56 4b a3 25 0a 50 54 bf ef 80 81 00 81 40 81 80 81 c0 95 00 90 40 b3 00 d1 c0 56 5e 00 a0 a0 a0 29 50 2f 20 35 00 55 50 21 00 00 1a 00 00 00 fd 00 38 4c 1f 5e 19 00 0a 20 20 20 20 20 20 00 00 00 fc 00 45 41 32 37 35 57 4d 69 0a 20 20 20 20 00 00 00 ff 00 36 31 31 30 32 32 35 37 4e 42 0a 20 20 01 63 02 01 04 00 01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 55 50 21 00 00 18 8c 0a d0 90 20 40 31 20 0c 40 55 00 55 50 21 00 00 18 01 1d 00 bc 52 d0 1e 20 b8 28 55 40 55 50 21 00 00 1e 02 3a 80 d0 72 38 2d 40 10 2c 45 80 55 50 21 00 00 1e f0 3c 00 d0 51 a0 35 50 60 88 3a 00 55 50 21 00 00 1c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 95

That was still with the single link cable, I don't know if the monitor is clever enough to somehow probe this and adjust it's available modelines. Then again, SGI VPro is single link as well.
I used an online service (http://www.edidreader.com/) to extract this bit:

Code: Select all

Detailed Timing Descriptor
Pixel Clock: 156MHz
Horizontal Active: 1280
Horizontal Blanking: 464
Vertical Active: 1440
Vertical Blanking: 53
Horizontal Sync Offset: 96
Horizontal Sync Pulse: 136
Vertical Sync Offset: 3
Vertical Sync Pulse: 10
Horizontal Display Size: 597
Vertical Display Size: 336
Horizontal Border: 0
Vertical Border: 0
Interlaced: false
Stereo Mode: 0
Sync Type: 3

I'll try to dig up a DVI-HDMI cable somewhere. I need one before I can try a V12+DCD and the side-by-side function of the monitor, because the EA275WMi has only a single DVI input.
:PI: :Indigo: :Indigo: :Indy: :Indy: :Indy: :Indigo2: :Indigo2: :Indigo2IMP: :Octane: :Octane2: :O2: :O2+: Image :Fuel: :Tezro: :4D70G: :Skywriter: :PWRSeries: :Crimson: :ChallengeL: :Onyx: :O200: :Onyx2: :O3x02L:
To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. (IRIS 4D/70 Superworkstation Technical Report)

User avatar
jan-jaap
Donor
Donor
Posts: 4881
Joined: Thu Jun 17, 2004 11:35 am
Location: Wijchen, The Netherlands
Contact:

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby jan-jaap » Tue Oct 11, 2016 1:59 pm

A little update. First of all, I extracted EDID information using EnTech Monitor Asset Manager:

Code: Select all

Monitor
  Model name............... EA275WMi
  Manufacturer............. NEC
  Plug and Play ID......... NEC2BA6
  Serial number............ 61102257NB
  Manufacture date......... 2016, ISO week 1
  Filter driver............ None
  -------------------------
  EDID revision............ 1.3
  Input signal type........ Digital
  Color bit depth.......... Undefined
  Display type............. RGB color
  Screen size.............. 600 x 340 mm (27.2 in)
  Power management......... Standby, Suspend, Active off/sleep
  Extension blocs.......... 1 (CEA-EXT)
  -------------------------
  DDC/CI................... Not supported

Color characteristics
  Default color space...... Non-sRGB
  Display gamma............ 2.20
  Red chromaticity......... Rx 0.653 - Ry 0.336
  Green chromaticity....... Gx 0.295 - Gy 0.640
  Blue chromaticity........ Bx 0.146 - By 0.042
  White point (default).... Wx 0.313 - Wy 0.329
  Additional descriptors... None

Timing characteristics
  Horizontal scan range.... 31-94kHz
  Vertical scan range...... 56-76Hz
  Video bandwidth.......... 250MHz
  CVT standard............. Not supported
  GTF standard............. Not supported
  Additional descriptors... None
  Preferred timing......... Yes
  Native/preferred timing.. 2560x1440p at 60Hz (16:9)
    Modeline............... "2560x1440" 241.500 2560 2607 2639 2720 1440 1443 1448 1481 +hsync -vsync

Standard timings supported
     720 x  400p at  70Hz - IBM VGA
     640 x  480p at  60Hz - IBM VGA
     640 x  480p at  67Hz - Apple Mac II
     640 x  480p at  72Hz - VESA
     640 x  480p at  75Hz - VESA
     800 x  600p at  56Hz - VESA
     800 x  600p at  60Hz - VESA
     800 x  600p at  72Hz - VESA
     800 x  600p at  75Hz - VESA
     832 x  624p at  75Hz - Apple Mac II
    1024 x  768p at  60Hz - VESA
    1024 x  768p at  70Hz - VESA
    1024 x  768p at  75Hz - VESA
    1280 x 1024p at  75Hz - VESA
    1152 x  870p at  75Hz - Apple Mac II
    1280 x  800p at  60Hz - VESA STD
    1280 x  960p at  60Hz - VESA STD
    1280 x 1024p at  60Hz - VESA STD
    1280 x  720p at  60Hz - VESA STD
    1440 x  900p at  60Hz - VESA STD
    1400 x 1050p at  60Hz - VESA STD
    1680 x 1050p at  60Hz - VESA STD
    1920 x 1080p at  60Hz - VESA STD

EIA/CEA-861 Information
  Revision number.......... 1
  IT underscan............. Not supported
  Basic audio.............. Not supported
  YCbCr 4:4:4.............. Not supported
  YCbCr 4:2:2.............. Not supported
  Native formats........... 0
  Detailed timing #1....... 1280x720p at 60Hz (16:9)
    Modeline............... "1280x720" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
  Detailed timing #2....... 720x480p at 60Hz (16:9)
    Modeline............... "720x480" 27.000 720 736 798 858 480 489 495 525 -hsync -vsync
  Detailed timing #3....... 720x576p at 50Hz (16:9)
    Modeline............... "720x576" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
  Detailed timing #4....... 1280x720p at 50Hz (16:9)
    Modeline............... "1280x720" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
  Detailed timing #5....... 1920x1080p at 50Hz (16:9)
    Modeline............... "1920x1080" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
  Detailed timing #6....... 1280x1440p at 60Hz (16:9)
    Modeline............... "1280x1440" 156.000 1280 1376 1512 1744 1440 1443 1453 1493 -hsync +vsync

Report information
  Date generated........... 10/11/2016
  Software revision........ 2.90.0.1020
  Data source.............. Real-time 0x0011
  Operating system......... 10.0.14393.2

Raw data
  00,FF,FF,FF,FF,FF,FF,00,38,A3,A6,2B,01,01,01,01,01,1A,01,03,80,3C,22,78,EA,4B,B5,A7,56,4B,A3,25,
  0A,50,54,BF,EF,80,81,00,81,40,81,80,81,C0,95,00,90,40,B3,00,D1,C0,56,5E,00,A0,A0,A0,29,50,2F,20,
  35,00,55,50,21,00,00,1A,00,00,00,FD,00,38,4C,1F,5E,19,00,0A,20,20,20,20,20,20,00,00,00,FC,00,45,
  41,32,37,35,57,4D,69,0A,20,20,20,20,00,00,00,FF,00,36,31,31,30,32,32,35,37,4E,42,0A,20,20,01,63,
  02,01,04,00,01,1D,00,72,51,D0,1E,20,6E,28,55,00,55,50,21,00,00,1E,8C,0A,D0,8A,20,E0,2D,10,10,3E,
  96,00,55,50,21,00,00,18,8C,0A,D0,90,20,40,31,20,0C,40,55,00,55,50,21,00,00,18,01,1D,00,BC,52,D0,
  1E,20,B8,28,55,40,55,50,21,00,00,1E,02,3A,80,D0,72,38,2D,40,10,2C,45,80,55,50,21,00,00,1E,F0,3C,
  00,D0,51,A0,35,50,60,88,3A,00,55,50,21,00,00,1C,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,95

I think that modeline #6:
Modeline............... "1280x1440" 156.000 1280 1376 1512 1744 1440 1443 1453 1493 -hsync +vsync
is the same as the one Recondas used.

Here's a shot of the monitor in side-by-side mode between a PC running Windows 10 and the Octane2 boot screen:
2560x1024_1.jpg

Scary ;)

And this is with the Octane2 in 2@1280x1024_60 mode, using the DVI and HDMI inputs of the screen:
2560x1024_2.jpg

Better :)

Back to the modelines. Using `cvt' I can generate the same 1280x1440 modeline I find in the EDID:

Code: Select all

$ ./cvt 1280 1440 60 -v
 1: [V FIELD RATE RQD]         :       60.000000
 2: [H PIXELS RND]             :     1280.000000
 2.5: [ASPECT_RATIO]           :     Custom
 2.5: [V SYNC]                 :       10.000000
 3: [LEFT MARGIN (PIXELS)]     :        0.000000
 3: [RIGHT MARGIN (PIXELS)]    :        0.000000
 4: [TOTAL ACTIVE PIXELS]      :     1280.000000
 5: [V LINES RND]              :     1440.000000
 6: [TOP MARGIN (LINES)]       :        0.000000
 6: [BOT MARGIN (LINES)]       :        0.000000
 7: [INTERLACE]                :        0.000000
 8: [H PERIOD EST]             :       11.168861
 9: [Actual V_SYNC_BP]         :       49.244053
 9: [Estimated V_SYNC_BP]      :       50.000000
 9: [V_SYNC_BP]                :       50.000000
10: [Back porch]               :       40.000000
11: [TOTAL V LINES]            :     1493.000000
12: [IDEAL DUTY CYCLE]         :       26.649342
13: [H BLANK]                  :      464.000000
14: [TOTAL PIXELS]             :     1744.000000
15: [Non-rounded PIXEL FREQ]   :      156.148422
15: [ACT PIXEL FREQ]           :      156.000000
16: [ACT H FREQ]               :       89.449539
17: [ACT FIELD RATE]           :       59.912617
18: [ACT FRAME RATE]           :       59.912617
20: [H BACK PORCH]             :      232.000000
21: [H SYNC RND]               :      136.000000
22: [H FRONT PORCH]            :       96.000000
23: [V FRONT PORCH]            :        3.000000

  # 1280x1440 @ 60.00 Hz (CVT)
  #   field rate 59.91 Hz; hsync: 89.45 kHz; pclk: 156.00 MHz
  Modeline "1280x1440_60.00"  156.00  1280 1376 1512 1744  1440 1443 1453 1493  -HSync +Vsync

However, this being an LCD screen I can probably get away with reduced blanking which lowers the pixel clock substantially:

Code: Select all

$ ./cvt 1280 1440 60 -v -r
 1: [V FIELD RATE RQD]         :       60.000000
 2: [H PIXELS RND]             :     1280.000000
 2.5: [ASPECT_RATIO]           :     Custom
 2.5: [V SYNC]                 :       10.000000
 3: [LEFT MARGIN (PIXELS)]     :        0.000000
 3: [RIGHT MARGIN (PIXELS)]    :        0.000000
 4: [TOTAL ACTIVE PIXELS]      :     1280.000000
 5: [V LINES RND]              :     1440.000000
 6: [TOP MARGIN (LINES)]       :        0.000000
 6: [BOT MARGIN (LINES)]       :        0.000000
 7: [INTERLACE]                :        0.000000
 8: [H PERIOD EST]             :       11.254630
 9: [Actual VBI LINES]         :       40.872066
 9: [VBI LINES]                :       41.000000
10: [Minimum VBI Lines]        :       19.000000
10: [ACT VBI LINES]            :       41.000000
11: [TOTAL V LINES]            :     1481.000000
12: [TOTAL PIXELS]             :     1440.000000
13: [Non-rounded PIXEL FREQ]   :      127.958397
13: [ACT PIXEL FREQ]           :      127.750000
14: [ACT H FREQ]               :       88.715279
15: [ACT FIELD RATE]           :       59.902283
16: [ACT FRAME RATE]           :       59.902283
20: [H BACK PORCH]             :       80.000000
21: [H SYNC RND]               :       32.000000
22: [H FRONT PORCH]            :       48.000000
23: [V FRONT PORCH]            :        3.000000

  # 1280x1440 @ 60.00 Hz Reduced Blank (CVT)
  #   field rate 59.90 Hz; hsync: 88.72 kHz; pclk: 127.75 MHz
  Modeline "1280x1440_60.00_rb"  127.75  1280 1328 1360 1440  1440 1443 1453 1481  +HSync -Vsync

... and that modeline is apparently present in the NEC PA271W so it might just work in this screen as well.

What I can't seem to find anywhere is how to write a VFS file for a 2@ DCD mode. Recondas posted some VFO files, but not how he made them, or at least I can't find it. Help!!
:PI: :Indigo: :Indigo: :Indy: :Indy: :Indy: :Indigo2: :Indigo2: :Indigo2IMP: :Octane: :Octane2: :O2: :O2+: Image :Fuel: :Tezro: :4D70G: :Skywriter: :PWRSeries: :Crimson: :ChallengeL: :Onyx: :O200: :Onyx2: :O3x02L:
To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. (IRIS 4D/70 Superworkstation Technical Report)

User avatar
recondas
Moderator
Moderator
Posts: 5441
Joined: Sun Jun 06, 2004 5:55 pm
Location: NC - USA

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby recondas » Tue Oct 11, 2016 7:31 pm

Sorry to be so slow getting back to you; when my day off came 'round again a hurricane ate the local power grid.

This one follows the original modeline and your EDID derived #6 fairly closely (took a fresh look at the DCD transitions and realized I had made a simple math error). With that fix the 2@ pixel clock came in at a single-link compatible 155.967Hz.

Here's the info file for the 2@ format.....

Code: Select all

 2@1280x1440_59.9.vfo:
 Total lines per frame:   2982
 Total pixels per line:   1744
 Active lines per frame:  1440
 Active pixels per line:  1280
 Frames per second:       29.95
 Fields per frame:        2
 Swaps per frame:         2
 Pixel clock:             155.758 MHz, period = 6.42021 nsec
 Hardware pixel rounding:  every 1 pixels
 Line analysis:
  Length:                 1744 Pixels, 1 Lines, 11.1968 usec;
  Frequency:              89.3109 KHz, period = 11.1968 usec
 Horizontal Sync:         136 Pixels, 873.148 nsec;
 Horizontal Back Porch:   232 Pixels, 1.48949 usec;
 Horizontal Active:       1280 Pixels, 8.21787 usec;
 Horizontal Front Porch:  96 Pixels, 616.34 nsec;
 Field 0 Information:
  Field Duration:           2.5881e+06 Pixels, 1484 Lines, 16.6161 msec;
  Vertical Sync:            8720 Pixels, 5 Lines, 55.9842 usec;
  Vertical Sync Pulse:      10368 Pixels, 5.94495 Lines, 66.5647 usec;
  Vertical Back Porch:      62784 Pixels, 36 Lines, 403.086 usec;
  Vertical Active:          2.51136e+06 Pixels, 1440 Lines, 16.1235 msec;
  Vertical Front Porch:     5232 Pixels, 3 Lines, 33.5905 usec;
 Field 1 Information:
  Field Duration:           2.61251e+06 Pixels, 1498 Lines, 16.7729 msec;
  Vertical Sync:            15696 Pixels, 9 Lines, 100.772 usec;
  Vertical Sync Pulse:      17344 Pixels, 9.94495 Lines, 111.352 usec;
  Vertical Back Porch:      68016 Pixels, 39 Lines, 436.677 usec;
  Vertical Active:          2.51136e+06 Pixels, 1440 Lines, 16.1235 msec;
  Vertical Front Porch:     17440 Pixels, 10 Lines, 111.968 usec;
......and the one for a single display panel

Code: Select all

1280x1440_59.9_modeline.vfo:
 Total lines per frame:   1493
 Total pixels per line:   1744
 Active lines per frame:  1440
 Active pixels per line:  1280
 Frames per second:       59.9
 Fields per frame:        1
 Swaps per frame:         1
 Pixel clock:             155.967 MHz, period = 6.41161 nsec
 Hardware pixel rounding:  every 1 pixels
 Line analysis:
  Length:                 1744 Pixels, 1 Lines, 11.1818 usec;
  Frequency:              89.4307 KHz, period = 11.1818 usec
 Horizontal Sync:         136 Pixels, 871.978 nsec;
 Horizontal Back Porch:   232 Pixels, 1.48749 usec;
 Horizontal Active:       1280 Pixels, 8.20686 usec;
 Horizontal Front Porch:  96 Pixels, 615.514 nsec;
 Field Information:
  Field Duration:           2.60379e+06 Pixels, 1493 Lines, 16.6945 msec;
  Vertical Sync:            19184 Pixels, 11 Lines, 123 usec;
  Vertical Sync Pulse:      19320 Pixels, 11.078 Lines, 123.872 usec;
  Vertical Back Porch:      68016 Pixels, 39 Lines, 436.092 usec;
  Vertical Active:          2.51136e+06 Pixels, 1440 Lines, 16.1019 msec;
  Vertical Front Porch:     5232 Pixels, 3 Lines, 33.5455 usec;
The timing transitions worked out to keep the single and dual display versions reasonable close. Since the single display version
apparently worked, hopefully the similarities are within the scan range accepted by your monitor.
Attachments
2@1280x1440_59.9.vfo
(9.49 KiB) Downloaded 10 times
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

User avatar
jan-jaap
Donor
Donor
Posts: 4881
Joined: Thu Jun 17, 2004 11:35 am
Location: Wijchen, The Netherlands
Contact:

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby jan-jaap » Wed Oct 12, 2016 12:53 pm

recondas wrote:Sorry to be so slow getting back to you; when my day off came 'round again a hurricane ate the local power grid.

No problem! Hope everything is OK?

recondas wrote:Since the single display version apparently worked, hopefully the similarities are within the scan range accepted by your monitor.

The single version works fine. It isn't practical with the aspect ratio of the screen, but I now know the DCD puts out an identical picture on both DVI ports with non-DCD modes, and when I set my monitor to side-by-side mode, I have the same picture *twice* on the screen ;)

But the DCD '2@' mode results in violent flickering and something that looks interlaced? I quickly switched back to a safe display mode...

How do you create these 2@ modes? I've been browsing around in /usr/gfx/ucode/vfc but I don't find many clues there. It seems VPro-DCD.def can set some variables, and VPro_Board.def and VPro_BlockSync.def seem to do something depending on non-zero values of those -- so do you include VPro-DCD.def in the call to vfc before the other.def files?
:PI: :Indigo: :Indigo: :Indy: :Indy: :Indy: :Indigo2: :Indigo2: :Indigo2IMP: :Octane: :Octane2: :O2: :O2+: Image :Fuel: :Tezro: :4D70G: :Skywriter: :PWRSeries: :Crimson: :ChallengeL: :Onyx: :O200: :Onyx2: :O3x02L:
To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. (IRIS 4D/70 Superworkstation Technical Report)

User avatar
recondas
Moderator
Moderator
Posts: 5441
Joined: Sun Jun 06, 2004 5:55 pm
Location: NC - USA

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby recondas » Wed Oct 12, 2016 8:29 pm

jan-jaap wrote:How do you create these 2@ modes? I've been browsing around in /usr/gfx/ucode/vfc but I don't find many clues there.
Looked pretty hard at that myself, and couldn't turn up squat in the way of documentation (or even anything that'd pass as a reasonably healthy clue).

What I was able to come up with came from repeated trial-n-error experimentation..... attempting to create a source file, attaching VPro_DCD.def as an include statement, then dredging the error messages to figure out missing parameters.

As it turns out, that's actually the easy part. Choosing the right values to plug in to the source file isn't always a straightforward pull-'em-from-the-modeline proposition.

If you'd like to try your hand, here's my spin on a 2@ source file.

Replace the brackets and enclosed text with the requested data. As an example, if your intended refresh rate was 60Hz, the frames definition line in my outline

Code: Select all

#define F_FRM_PER_SEC <numerical value = to 1/2 the target refresh rate>
would appear as

Code: Select all

#define F_FRM_PER_SEC 30.0


You can start by trying values pulled directly from the single display source file (aka modeline #6). So the "P_HORZ_BP" definition in the 2@ source would call for the same data as "HorizontalBackPorch" from our modeline calculations (the leading "P" used in the 2@ source tells VPro_DCD.def the expressed value is in pixels, "L" lines, and "F" frames).

Code: Select all

/* Note: call with the Makefile located in /usr/gfx/ucode/vfc/vfs */

/*
 * The following variables are required for 2@ VPro_DCD formats.
 */

#define FORMAT_NAME "<insert source file name between quotations replacing bracketed text>; "
#define F_FRM_PER_SEC <numerical value = to 1/2 the target refresh rate>
#define L_ACT_LINES_PER_FRM <replace with numerical value>
#define P_ACT_PIX_PER_LINE <numerical value>

#define P_HORZ_BP <numerical value>
#define P_HORZ_SYNC <numerical value>
#define P_HORZ_FP <numerical value>

#define L_VERT_FP_0 <numerical value>
#define L_VERT_SYNC_0 <numerical value>
#define L_VERT_BP_0 <numerical value>
/*
 * The following inclusion will direct VFC to use the VPro_DCD definitions
 * while building the format microcode.
 */
#include "/usr/gfx/ucode/vfc/rules/VPro_DCD.def"


jan-jaap wrote:It seems VPro-DCD.def can set some variables, and VPro_Board.def and VPro_BlockSync.def seem to do something depending on non-zero values of those -- so do you include VPro-DCD.def in the call to vfc before the other.def files?
VPro_DCD.def is our focus; VPro_BlockSync.def isn't called upon when creating 2@ formats. You won't directly call on VPro_Board.def or VPro_Chip.def, but you will want to make sure the Makefile you use calls on them in the rules section. As an example, line 46 in the Makefile I call on when creating VPro specific 2@ formats reads:

Code: Select all

   $(VFC) -a ascii=$*.info -c chip=${RULES}/VPro_Chip.def,board=${RULES}/VPro_Board.def $(VFCOPTS) -o $*.vfo $*.vfs
FWIW, I have multiple copies of the Makefile in separate directories, each editied with the Board and Chip rules definitions for different (VFC supported) graphics platforms.

My trial and error experimentation's have barely scratched the surface of what's needed to create useful 2@ formats. There's lots more to be discovered, so the more eyes on the subject the better.
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

Y888099
Posts: 523
Joined: Mon Jul 11, 2016 11:00 am

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby Y888099 » Tue Dec 27, 2016 4:32 am

wow, amazing.
Head Full of Snow. Lemon Scented You

User avatar
Zerolapse
Posts: 416
Joined: Mon Sep 12, 2005 8:32 pm
Location: New York, USA

Re: VPro V12 and oddball 1280x1440 resolution?

Unread postby Zerolapse » Thu Jun 29, 2017 9:48 pm

Hey Guys!

Sorry to thread dredge, but did you ever get this working? I've got a Samsung monitor with the same resolution and same capability and it would be super handy! :-)

-Jesse
:O3x06R: :ChallengeL: :Octane: :Octane2: :O2: :Indy: (4x Challenge S)
The current fleet.


Return to “SGI: Hardware”

Who is online

Users browsing this forum: Bing [Bot] and 1 guest