From owner-freebsd-hackers Sun Feb 14 16:52:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07128 for freebsd-hackers-outgoing; Sun, 14 Feb 1999 16:52:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07110; Sun, 14 Feb 1999 16:52:27 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA18367; Sun, 14 Feb 1999 16:44:47 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdq18365; Mon Feb 15 00:44:40 1999 Date: Sun, 14 Feb 1999 16:44:37 -0800 (PST) From: Julian Elischer To: Doug Rabson cc: Bill Paul , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: How the hell does one create a new bus?! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The trouble is Doug, that until there IS a developer's guide, the only person capable if moving PCI and ISA to your scheme, is you. and as you pointed out.. you're short of time right now.. This stuff is very cryptic. On Mon, 15 Feb 1999, Doug Rabson wrote: > I hope I've explained some things. There isn't a developer's guide as > yet, I'm afraid and I don't really have time to write one :-(. Perhaps > one of the people who has used the code might like to tackle it (or you > might if you manage to struggle through implementing this thing...) > > If anyone wants to write such a guide, please go ahead and feel free to > ask me any questions about how the thing is supposed to work. > This email in itself has cleared up a few things.. but there is still a nead for a more general overview which should be read before getting to this level of detail.. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message