From: Jonathan Gray <email@example.com>
To: Paul Ruizendaal <firstname.lastname@example.org>
Subject: [TUHS] Re: Porting the SysIII kernel: boot, config & device drivers
Date: Sun, 1 Jan 2023 19:05:32 +1100 [thread overview]
Message-ID: <Y7E+zBDzD/YIt2So@largo.jsg.id.au> (raw)
On Sat, Dec 31, 2022 at 09:02:38PM +0100, Paul Ruizendaal wrote:
> > On 31 Dec 2022, at 15:59, Dan Cross <email@example.com> wrote:
> > On Fri, Dec 30, 2022 at 1:26 PM Paul Ruizendaal <firstname.lastname@example.org> wrote:
> >> [snip]
> >> It would seem that the next step for Unix in the area of boot, config and device drivers came with Sun’s OpenBoot in 1988 or so. This also appears to be the first appearance of device trees to describe the hardware to the bios and the kernel. Moreover, it would seem to me that OpenBoot is a spiritual ancestor of the modern Risc-V SBI specification. Maybe by 1988 the IO hardware had become sufficiently complex and/or diverse to warrant a break from tradition?
> >> Was there any other notable Unix work on better organising the boot process and the device drivers prior to OpenBoot?
> > I think that BSD supported autoconfiguration on the VAX well before
> > OpenBoot; the OpenBSD man page says it dates from 4.1 (1981) and was
> > revamped in 4.4.
> That is interesting. Are you referring to this:
"the tuned-up system, with the addition of Robert Elz's auto
configuration code, was released as 4.1BSD in June, 1981"
McKusick, Twenty Years of Berkeley Unix
"This update to the fourth distribution of November 1980 provides
support for the VAX 11/750 and for the full interconnect architecture of
the VAX 11/780. Robert Elz of the University of Melbourne
contributed greatly to this distribution especially in the boot-time
system configuration code"
4.4 discussed in Torek's
Device Configuration in 4.4BSD
A New Framework for Device Support in Berkeley Unix
from Proceedings of the UKUUG, London, Summer 1990.
not online, though Chris sent Warner a copy in 2021
I would also like to read it. Perhaps it could be added to the archive?
prev parent reply other threads:[~2023-01-01 8:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 18:25 [TUHS] " Paul Ruizendaal
2022-12-30 18:56 ` [TUHS] " Steve Nickolas
2022-12-31 14:59 ` Dan Cross
2022-12-31 19:08 ` Clem Cole
2022-12-31 21:10 ` Dan Cross
2022-12-31 21:39 ` Clem Cole
2022-12-31 21:52 ` Dan Cross
2022-12-31 23:25 ` Dave Horsfall
2023-01-01 1:02 ` Rob Pike
2023-01-01 1:16 ` George Michaelson
2023-01-01 1:40 ` Larry McVoy
2023-01-01 2:29 ` Warner Losh
2023-01-01 1:24 ` Larry McVoy
2022-12-31 22:38 ` Theodore Ts'o
2022-12-31 22:55 ` Marc Donner
2023-01-01 3:55 ` Dan Cross
2023-01-01 20:29 ` Paul Ruizendaal
2023-01-01 21:26 ` G. Branden Robinson
2023-01-01 21:31 ` Rob Pike
2022-12-31 21:11 ` Paul Ruizendaal
2022-12-31 20:02 ` Paul Ruizendaal
2022-12-31 21:04 ` Warner Losh
2022-12-31 21:41 ` Dan Cross
2023-01-01 3:08 ` Warner Losh
2023-01-01 4:40 ` Dan Cross
2023-01-01 8:05 ` Jonathan Gray [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).