Re: newconfig/new-bus

1999-04-16 Thread Doug Rabson
On Fri, 16 Apr 1999, UCHIYAMA Yasushi wrote: > | shouldn't be too hard though, but even then there are seriously non-trivial > | differences in the tty, block/character devices, VM, networking, etc. Even > | if the config interface was compatable it wouldn't ever be a 'drop in' > | option, ev

Re: newconfig/new-bus

1999-04-16 Thread UCHIYAMA Yasushi
| shouldn't be too hard though, but even then there are seriously non-trivial | differences in the tty, block/character devices, VM, networking, etc. Even | if the config interface was compatable it wouldn't ever be a 'drop in' | option, even with 'newconfig'. In strongly system-dependent par

Re: newconfig/new-bus

1999-04-13 Thread Julian Elischer
On Wed, 14 Apr 1999, UCHIYAMA Yasushi wrote: > NetBSD drivers already bus-specific frontend code was separated from > bus-independent(backend) code. So easy to adapt another buses. > I've tested its separation for FreeBSD's ep code, but it was already > done by NetBSD. ed case, I determined

Re: newconfig/new-bus

1999-04-13 Thread UCHIYAMA Yasushi
| 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). ep at isa/pcmcia/cardbus ... I fully rewrote code t

Re: newconfig/new-bus

1999-04-13 Thread Julian Elischer
ing 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.

Re: newconfig/new-bus

1999-04-13 Thread Peter Wemm
"Rick Whitesel" wrote: > Hi: > I should have been more clear. BSD driver interoperability is a seperate > issue from Linux application interoperability but I think both are > important. I don't want to get hopes up prematurely, but we think we might be able to emulate enough of the newconfig-s

Re: newconfig/new-bus

1999-04-13 Thread Matthew Jacob
> Hi: > I should have been more clear. BSD driver interoperability is a seperate > issue from Linux application interoperability but I think both are > important. For an example of Linux/*BSD driver interoperability and the grief and difficulties therein, you might want to look at the Qlogic

Re: newconfig/new-bus

1999-04-13 Thread Rick Whitesel
orary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 - Original Message - From: Doug Rabson To: Rick Whitesel Cc: ; UCHIYAMA Yasushi Sent: Tuesday, April 13, 1999 3:11 PM Subject: Re: newconfig/new-bus On Tue, 13 Apr 1999, Rick Whitesel wr

Re: newconfig/new-bus

1999-04-13 Thread Doug Rabson
On Tue, 13 Apr 1999, Rick Whitesel wrote: > Hi: > I just wanted to say that I see this as very important work. BSD and > Linux interoperability is the best way to insure the BSDs survive (and maybe > better) the Linux mania. I think the work is important too but it won't improve interoperabil

Re: newconfig/new-bus

1999-04-13 Thread Rick Whitesel
MA Yasushi To: Sent: Tuesday, April 13, 1999 3:58 AM Subject: newconfig/new-bus ftp://ftp.nop.or.jp/users/uch/PCMCIA/FreeBSD/sys4c990410-newconfig990413.pat ch.gz This is newest newconfig patch against to 4.0-CURRENT(990410). FreeBSD/newconfig provides NetBSD compatible frame work ,b

newconfig/new-bus

1999-04-13 Thread UCHIYAMA Yasushi
itten 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/