On Wed, Nov 13, 2002, Egbert Eich <[EMAIL PROTECTED]> wrote:
>
> I don't see what special support is required for VLB bus.
> It should work like an ISA Bus system as long as you are
> not trying to get a VLB/PCI motherboard to work.
> We have no knowledge of VLB-PCI bridges therefore it is not
> unlikely that you run into trouble with these systems.
>
The board is an old 486 VLB + ISA buses without PCI connectors.
I too don't know what special support is required for VLB bus. Yet I
believe I have read somewhere that one problem of the ISA cards is that
letting them have lot of on board memory is problematic because this
memory can be mapped to other memory areas which might have memory
installed in them. This was no problem when memory chips were specified
in KB, but is sure problematic when 100th of MB is considered standard.
This might be connected with the fact that ISA is a 16 bits bus while
VLB is a 32 bits. Or am I wrong about it? BTW, my card has 2 MB on board
memory. I am quite sure that ISA cards with more then 1 MB of memory are
rare if not non existent.
In addition, the same hardware is working with 3.3.6 and I will try to
explain below why I was expecting it to work with 4.2.1. Another thing
is that 4.2.1 tells me that:
(II) S3: driver (version 0.3.5 for S3 chipset: 964-0, 964-1, 968,
Trio32/64, Aurora64V+
(II) Primary Device is: ISA
(EE) No devices detected.
> That you cannot get the S3 Trio32 to work under 4.2. is
> more likely due to the fact that this chip isn't supported
> by 4.2.
>
$ zgrep -C5 Trio32 /usr/share/doc/xserver-xfree86/Status.gz
28. S3
3.3.6:
Support (accelerated) for the S3 911, 924, 801, 805, 928, 864,
868, 964, 968, Trio32, Trio64, Trio64V+, Trio64UV+, Aurora64V+,
Trio64V2, and PLATO/PX is provided by the XF86_S3 server and the
XF86_SVGA server with the s3_svga driver. Support (accelerated)
for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX,
ViRGE/MX+ is provided by the XF86_S3V server. Support (acceler-
ated) for the ViRGE chipsets, as well as the Trio3D and
--
Savage4, and Savage2000, is provided by the XF86_SVGA server with
the s3_savage driver on some OSes (Linux, *BSD).
4.2.1:
Support (accelerated) for the 964 (revisions 0 and 1), 968,
Trio32, Trio64, Trio64, Trio64V+, Trio64UV+, Aurora64V+,
Trio64V2, and PLATO/PX is provided by the "s3" driver (however,
only models using the IBM RGB 524, Texas Instruments 3025, or an
internal TrioDAC RAMDAC chip are supported). Support (acceler-
ated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2,
ViRGE/MX, ViRGE/MX+, Trio3D and Trio3D/2X is provided by the
$
Now if I understand this correctly, the only thing that I am left to
show is that my card satisfies the condition about the RAMDAC. Isn't
the following quotation from the output of 3.3.6 (BTW, with the same
board) shows it:
(--) S3: chipset: Trio32 rev. 0
(--) S3: chipset driver: mmio_928
(**) S3: Option "power_saver"
(--) S3: card type: 386/486 localbus
(--) S3: videoram: 2048k
(--) S3: Ramdac type: s3_trio32
(--) S3: Ramdac speed: 135 MHz
(--) S3: Using Trio32/64 programmable clock (MCLK 54.886 MHz)
(--) S3: Maximum allowed dot-clock: 80.000 MHz
(**) S3: Mode "800x600": mode clock = 49.500
(**) S3: Mode "640x480": mode clock = 31.500
(**) S3: Using 16 bpp. Color weight: 565
(**) S3: Virtual resolution set to 1152x900
(--) S3: Local bus LAW is 0xF3000000
(--) S3: Using a banksize of 2048k, line width of 1152
(--) S3: Using a single 9x9 area at (1143,901) for expanding pixmaps
(--) S3: No font cache available
?
While I am at it, perhaps the problem is not the VLB bus but the fact
that both the supported Trio32 and the unsupported 928 were mentioned
in this output together?
>
> Shaul Karl writes:
> > Hello,
> >
> > It is my understanding that 4.2.1 does not support the VLB bus. Am I
> > correct?
> > Are there other people who would be interested in having this bus
> > supported?
> > Is there work in progress to have this bus supported? Can I help by
> > testing what was being done so far?
> > Are there any pointers for reading material for a beginner who want
> > to get his VLB card supported? How difficult it would be to import the
> > VLB supporting code from 3.3.6 to 4.2.1?
> >
> > My hardware is an S3 Trio32 VLB card: Miro CRYSTAL 12sd. The card works
> > well with 3.3.6 but not with 4.2.1. The platform is i386 Linux 2.4.19.
> > I can post the output of X when it starts if this is of interest to
> > someone.
>
--
Shaul Karl, [EMAIL PROTECTED] e t
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
