Date: Wed, 14 Apr 1999 03:53:16 +0800 From: Peter Wemm <peter@netplex.com.au> To: "Rick Whitesel" <rwhitesel@nbase-xyplex.com> Cc: "Doug Rabson" <dfr@nlsystems.com>, current@FreeBSD.ORG, "UCHIYAMA Yasushi" <uch@nop.or.jp> Subject: Re: newconfig/new-bus Message-ID: <19990413195319.16D6A1F4F@spinner.netplex.com.au> In-Reply-To: Your message of "Tue, 13 Apr 1999 15:26:02 -0400." <001101be85e3$77fd1e20$d3e4b38c@xyplex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"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-style interface via the same sort of wrapper shims that we use for the old isa and pci drivers. If that works out, then it should make porting/using a NetBSD/OpenBSD/BSDI driver a lot easier. There's bound to be #ifdefs required no matter what, but it shouldn't require two totally different config interfaces. Of course, this is still a "might" case since it hasn't been written. However, it would be quite hard to get this to work seamlessly for sub-busses and devices, eg: PCIC->PCCARD->CARDBUS->etc. Simple devices 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'. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990413195319.16D6A1F4F>