Port-amiga archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Amiga X woes with custom graphics card driver



Hi,

Radoslaw Kujawa told me to send my details here. I built a graphics card for classic Amiga computers (using the Zorro bus) and started writing a NetBSD driver for it. I managed to use it as a wsdisplay console but ran into problems with X and wsfb (Bus error, screenshot attached).

The driver sources and kernel config files are here:
https://github.com/mntmn/va2000-netbsd

I have several problems:
1. Using mntva as console:

If I enable the console setup part in my driver and configure GENERIC like this:

wsdisplay0 at wsdisplay0 at wsemuldisplaydev ? console ?

Then the boot starts on the internal Amiga chipset display and then switches over to my driver's display. But even if I have a working terminal on my card on ttyE0, X or any opening of the file "/dev/ttyE0" will complain about "device not configured". 

2. Using amidisplaycc as console:

Disabling console setup in mntva.c and configuring GENERIC like:

wsdisplay1 at amidisplaycc0 console ?
wsdisplay0 at wsdisplay0 at wsemuldisplaydev ?

Then my driver will initialize, and the boot console will stay on the Amiga chipset display. After login I can do:

wsconscfg 0

This seems to correctly configure /dev/ttyE0 and the gfx card screen is cleared and a white cursor appears. The /dev/ttyE0 file can be opened and X -config ./xorg.conf starts sending ioctls and mmaps to my driver, ultimately crashing with a Bus error though.

Can you see anything fishy/wrong in the driver source? Do I have to do any special setup of /etc/ttys or /etc/wscons.conf?

Thanks for any input.
Cheers,
Lukas F. Hartmann (@mntmn)

Attachment: va2000-x-crash.jpg
Description: JPEG image



Home | Main Index | Thread Index | Old Index