Re: call for testing: completing the device/softc split
matt@ wrote: > On Oct 10, 2012, at 10:55 AM, Izumi Tsutsui wrote: > > > I wrote: > > > >> ite chnages seem to cause silent hang at early bootstrap at least on XM6i, > >> so I'll check it on real X68030 with serial console later. > >> (IIRC atari's ite also had annoying quirks around console probe code..) > > > > I've also fixed and committed x68k ite. > > > > It has a static struct softc for early console, > > so we should also prepare a static struct device > > after it's split out from softc. Oh well. > > No. Just use a softc size of 0 and set self->dv_private to > the static softc in the attach and sc->sc_dev to self as well Hmm. If the driver requires whole members in the static softc, probably it's right. But I guess the current implementation of the ite driver is a result of kludges to adapt ancient drivers (derived from HPBSD) to 4.4BSD newconfig. The only necessary stuff for early console seems struct grf_softc that is copied in iteattach (as struct rasops_info in modern wscons drivers), but struct device is still referred in iteinit() etc only to get a device unit number, which is not necessary for console. Anyway, the ite drivers should be replaced by wscons in future and troubles during early console are really annoying, so I'd like to keep changes minimum on device_t/softc split. Thanks, --- Izumi Tsutsui
Re: 5.1 video(4) mmap interface?
> I'm trying to use the video(4) interface under 5.1. > [...mmap(2)-based interface doesn't work for me...] Jared McNeill very kindly pointed out I wasn't using VIDIOC_QBUF at all, which of course explains it. I'm fairly sure I wrote a loop with those in it. I don't know whether I'm hallucinating, or I managed to completely lose it during edits at some point, or what, but I find that (a) he's right, of course, and (b) when I supply them, it works just fine. My thanks to him for the thawck with the cluestick and my apologies to everyone for being such a friggin' idiot and bothering the list with a stupid mistake that could have been corrected with a careful reading of the manpage and the code. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTMLmo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
wscons russification
Hello all. I don't sure which mail-list to use(conf file editing is userlevel related, /dev is kern related). I'm trying to configure the wscons to use KOI8-R encoding. First of all I dumped fonts (vt220l.816 and vt220h.816) and I did not find any differences in their structure. I don't need the VESA video modes thus I don't need to resompile the kernel with WSCONS_SUPPORT_PCVTFONTS as suggested from /etc/wscons.conf: # Note: "pcvt" encoded fonts are only useful with the "*bf" screen types # of the "vga" driver. The kernel must be compiled with the option # "WSCONS_SUPPORT_PCVTFONTS" turned on. See vga(4). I just downloaded FreeBSD's http://www.freebsd.org/cgi/cvsweb.cgi/src/share/syscons/fonts/koi8-r-8x16.fnt, dumped it and found it has structure like vt220h.816. Thus I load it from /etc/wscons.conf via: # /etc/wscons.conf add-on font ibm - 16 iso /usr/share/wscons/fonts/koi8r.816 # end add-on and # /etc/wscons.conf add-on setvar ttyEx font ibm # end add-on It works perfectly. I've had koi8-r encoded file and I see it in right encoding via "more" command. Question 1: Are there any legal issues on FreeBSD's font adding into NetBSD's repository? If No I could make the patch. The NetBSD's keymap file doesn't work. I have: # /etc/wscons.conf add-on mapfile=/usr/share/wscons/keymaps/pckbd.ru.koi8-r # end add-on but "wsconsctl -a" shows: encoding=us and "wsconsctl map" doesn't show the third and forth colomns which exist in the keymap file. I tried by root: # wsconsctl -w encoding=ru which generates: wsconsctl: WSKBDIO_SETENCODING: Invalid argument grepping shows WSKBDIO_SETENCODING in the /usr/src/dev/wscons/wskbd.c, the code is trying to load keymapping as I understood at glance. Question 2: Is that error produced by non-exist binding between wskbd.ru.koi8-r file and "ru" keyword or by bad data in the wskdb.ru.koi8-r file itself? I've not found the answer on this question by myself. BTW meta key (Alt) works but keycodes are different from desired. I'm sure that wskbd.ru.koi8-r have to be recreated, but I need that wsconsctl could load it anyway. Best wishes, -- ynzo
re: call for testing: completing the device/softc split
> I also noticed that this patch fixes a problem on sparc, > booting a -current sparc GENERIC + QUEUEDEBUG hits an assertion > about the alldevs list being corrupted, whereas with this patch > it's fine. it wasn't obvious exactly what I fixed though. ah, this might explain some problems i was seeing recently that looked like corrupted alldevs list. thanks! .mrg.
