Subject: Re: Shark and igsfb
To: Izumi Tsutsui <email@example.com>
From: Michael Lorenz <firstname.lastname@example.org>
Date: 01/07/2007 14:27:18
-----BEGIN PGP SIGNED MESSAGE-----
On Jan 7, 2007, at 09:55, Izumi Tsutsui wrote:
> macallan@NetBSD.org wrote:
>>> I added ofbus attachment code for uwe's igsfb so now we can use a
>>> resolution graphical console with hardware acceleration on rev. 5
>> This has been committed
> FYI, my FUNAI's DNARD compatible has CT65550 so igsfb doesn't match.
> (should we split dev/pci/chipsfb.c into MI and bus dependent part?)
Yes, please :)
When I wrote chipsfb I didn't think I'd use it anywhere else than on a
PowerBook 3400 but I guess I should have known better. I don't think
I'll have time to do the split immediately but within a week or two
should be doable unless you beat me to it.
The ofbus attachment should probably be done by someone who has the
> XF86_SVGA (3.3.6) log is attached.
> (--) SVGA: Chipset: ct65550
> (--) SVGA: CHIPS: no monitor detected.
> (--) SVGA: CHIPS: 2048 kB VRAM
> (--) SVGA: CHIPS: TFT probed.
> (--) SVGA: CHIPS: CRT
> (--) SVGA: CHIPS: VL Bus
> (--) SVGA: CHIPS: base address is set at 0x6800000.
> (--) SVGA: CHIPS: Linear addressing is enabled at 0x6800000.
> (--) SVGA: CHIPS: using programmable clocks.
> (--) SVGA: CHIPS: probed memory clock of 39650 KHz
> (--) SVGA: CHIPS: GJS: About to test for builtin modes. eg NTSC
> Mode = 640x480(--) SVGA: chipset: ct65550
This should Just Work - chipsfb was written specifically for the 65550,
it doesn't attempt to mess with video modes or the memory clock (yet) -
just attempts to go with whatever it finds.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----