Re: __BROKEN_CONFIG_UNIT_USAGE ?

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

> > Well, I implemented bus_dma(9) and bus_space(9) for it,
> > but the rest annoying part is framebuffer support which
> > has too many quirks to use MI drivers...
> 
> Well, there is bus_space_mmap() and bus_space_vaddr()...

Most quirks are in attach code. See sys/arch/sun3/conf/cg4.sun3:
---
# Each cg4 config line applies to only one machine type,
# and the low 4 bits of the flags (if set) are matched
# against the same bits of the machine type ID code.
# Also, flag 0x10 signifies Type A (AMD RAMDACs),
# and the flag 0x20 indicates a missing P4 reg.
cgfour0 at obmem0 addr 0xFE400000 flags 0x34    # 3/110
cgfour0 at obmem0 addr 0xFF300000 flags 7       # 3/60 (P4)
# These two appear to have no P4 register.
cgfour0 at obmem0 addr 0xFF300000 flags 0x27    # 3/60 (old)
cgfour0 at obmem0 addr 0xFF300000 flags 0x28    # 3/E
---

cgfour on 3/60 is most major ones, I guess (and I looked for).

> > (and I don't have such machines)
> Write emulators of those devices for TME? :-)

I'm not sure if it's worth to implement such variants
to confirm them... (quirks are not so much fun but just annoying)

> Of course, the MI VME drivers don't seem to use much of
> bus_space anyway... take a look at the xy and xd drivers!

sun2 already uses MI vme and xy(4) on it. It's not so hard.

There are also MD ie(4), si(4), cgtwo(4), bwtwo(4) etc. on sun3 vme.
MI bwtwo(4) requires MI sun kbd drivers. Maybe we also need wscons.
And more something else? :-)

ie(4) and si(4) might be trivial (there are MI vme attachments),
but sebuf(4) on 3/E is also annoying..
---
Izumi Tsutsui