So I've been lookin gat this patch set.. it seems to duplicate a lot of code already in FreeBSD, by just replacing it with the equivalent code from NetBSD.
(or rather, jsut adding the NetBSD code and not using the FreeBSD version. This is acceptable in a test scenario). What is not so clear is what the chances are of us getting something that takes the best features from NetBSD and the best features from the new-bus code. There are similarities, but the differences are less obvious. The framework may be totally different, but how different do the DRIVERS have to be? julian (still reading the new-config stuff) On Tue, 13 Apr 1999, UCHIYAMA Yasushi wrote: > ftp://ftp.nop.or.jp/users/uch/PCMCIA/FreeBSD/sys4c990410-newconfig990413.patch.gz > This is newest newconfig patch against to 4.0-CURRENT(990410). > > FreeBSD/newconfig provides NetBSD compatible frame work ,bus_space(9) > (bus_memio.h,bus_pio.h are no longer required.) and `bus name`_intr_establish. > and also provides resource management. > This feature makes easy to implement and feedback drivers among *BSD. > As a sample, dev/pcmcia/ directory was imported from NetBSD. The > amounts of #ifdef __FreeBSD__ is little. > I'm working CardBus (dev/cardbus/) driver with NetBSD people. > (originary written for NetBSD) > > Newconfig may not to be seem exciting, but this is powerful and > flexible implementation in fact. please see this patch. > > Following table is guide map for comparison. > > newconfig new-bus > framework: > kern/subr_autoconf.c kern/subr_bus.c > sys/device.h sys/bus.h > resource management: > kern/subr_rman.c kern/subr_rman.c > i386/i386/resource.c i386/i386/nexus.c > > mainbus: > i386/i386/mainbus.c i386/i386/nexus.c > ISA bus: > i386/isa/isa_machdep.c i386/i386/nisa.c > PCI bus: > i386/pci/pci_machdep.c pci/pci.c > --- > UCHIYAMA Yasushi > u...@nop.or.jp > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
