T.R | Title | User | Personal Name | Date | Lines |
---|
1862.1 | | STAR::KLEINSORGE | Frederick Kleinsorge | Fri Feb 21 1997 08:49 | 7 |
| Is it possible? Sure, but it would take special console logic, and
special driver logic. Taking the next step, how do you convince the
firmware group, and the driver maintainer (what is the PBXGB-CA? A
TGA2?) to make the changes needed, for a monitor they don't have, or
support. Maybe this is a CSS job? (Do we still have a CSS?)
|
1862.2 | Considered A Serial Console? | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Fri Feb 21 1997 09:12 | 5 |
|
Has the customer considered `aiming' the console out the serial port?
One could use an LCD panel or ruggedized terminal -- years back, there
was a hand-held terminal used by field service -- as the console.
|
1862.3 | yep | WRKSYS::DISCHLER | I don't wanna wait in vain | Fri Feb 21 1997 09:54 | 2 |
| I agree with Steve. set console serial and drive
some other screen device.
|
1862.4 | sold from DEC ... | NETRIX::"[email protected]" | Hans Donauer | Fri Feb 21 1997 10:07 | 22 |
| to .1:
The PBXGB-CA ist the Digital Powerstorm 4D20, TGA2.
I would agree, its not our job, but the problem is :
The very good and very expensive (48 K$) Monitors were sold
from Digital sales, without checking the low resolutions.
So the customer spent some extra $s to buy also the Monitors from Digital,
for not to run in such problems.
Now the customer insists on what he payed for.
I don�t know the amount of work this means, but i thought of a console-
parameter like " set console VGA / set console SVGA"
The monitor is Multisync, it would work with every resolution greater then
640x480.
to .2:
the customer is not very cooperativ ....
Hans
[Posted by WWW Notes gateway]
|
1862.5 | | STAR::KLEINSORGE | Frederick Kleinsorge | Fri Feb 21 1997 10:18 | 14 |
| The console calls the BIOS emulator to set the text mode when in
console mode. It's not clear to me how much work it is, or if the
Cirrus graphics chip on the controller supports a higher-res text
mode at 80x25. Now, it's always possible to run the card in graphics
mode (no VGA), like the TGA. However, that is 180� from the direction
that graphics and console is headed (that is, explicit console logic
for specific hardware).
At the device driver level, the WS group would also need to modify
their code to make the runtime console run at another resolution. I've
done this on the Alphabook (which had to run in 800x600 pixel mode), so
it's possible, but again - it's extra work that I'm sure isn't
budgeted by the WS group.
|
1862.6 | consoles are ALWAYS VGA | WRKSYS::SCHUMANN | | Fri Feb 21 1997 10:59 | 9 |
| >> I don�t know the amount of work this means, but i thought of a console-
>> parameter like " set console VGA / set console SVGA"
How do you set it when you can't see the picture???
This dilemma is the reason why there is one and only one and exactly one
console display standard in the PC industry.
--RS
|
1862.7 | I've got a similar problem | BBPBV1::WALLACE | john wallace @ bbp. +44 860 675093 | Sat Feb 22 1997 07:56 | 15 |
| The ZLXp-E1 (TGA 1) had some switches which console code acted upon in
every case I can remember seeing.
There's no equivalent switches on the TGA2, presumably, given that it
has a builtin VGA chip?
I have a horrible feeling a customer of mine is about to discover this
problem too (BARCO monitor, won't sync in console mode, OK once OS is
up).
What would be the implications of using good ole ZLXp-E* instead of
trendy new stuff ?
regards
john
|
1862.8 | | STAR::KLEINSORGE | Frederick Kleinsorge | Mon Feb 24 1997 09:45 | 36 |
| I would ammend your proclamation to say "All new, Digital supported
graphics cards now come with a VGA for console use".
It's only a recent development here at DEC that there is a "standard"
console. The history of the console is that custom firmware and O/S
software was needed for each graphics device. The ZLXp-E* was the last
of this breed (or until we change our minds again).
The ZLXp-E* used system embedded firmware to drive the dumb frame
buffer logic that was used for the device (there is no VGA). And the
switches were read by FW to set the default resolution for the card.
If I were to try and design a solution to the problem (and mind you, I
don't think you are going to convince anybody to solve the problem),
I would have the console do something like:
Console == Graphics?
- Yes:
Any VGA found?
- No:
Any "known" non-VGA devices found (TGA, TGA2, etc)?
- Yes:
Use embedded high-res dumb frame buffer console logic.
- No:
Fail over to serial console.
- Yes:
Use VGA as console.
- No:
Use serial console.
The TGA2 can be supported using 95% of the same logic as the TGA in
dumb frame buffer mode, with maybe a little change in the init logic.
To use the TGA2 in dumb frame buffer mode, at a higher res, you would
disable the VGA (jumper).
|
1862.9 | not so easy.. | NETRIX::"[email protected]" | Hans Donauer | Tue Feb 25 1997 03:28 | 18 |
| Thank You for all the replies.
Frederick: When i see this right, its not only the consolcode, but also the
OS driver and much work on both ends.
So can You give me the names for the right persons to contact for
both sides, to check for practicability offline.
Thank You
Hans
VAXmail VNABRW::DONAUER_H
Exchange [email protected]
[Posted by WWW Notes gateway]
|
1862.10 | | STAR::KLEINSORGE | Frederick Kleinsorge | Tue Feb 25 1997 08:45 | 10 |
|
As there is no "console" group in the workstation organization, I can
only suggest contacting the product manager (Keith Bellamy?), or
someone in engineering management like Fred Roemer.
The O/S driver and the console code are both owned by the workstation
organization for the TGA2. The engineering manager for the driver is
Dick Coulter.
|