Date: Wed, 17 Mar 1999 21:14:43 -0500 (EST) From: Brian Feldman <green@unixhelp.org> To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= <sos@freebsd.dk> Cc: Robert Nordier <rnordier@nordier.com>, current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? Message-ID: <Pine.BSF.4.05.9903172113070.12911-100000@janus.syracuse.net> In-Reply-To: <199903171338.OAA26021@freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Mar 1999, S=F8ren Schmidt wrote: > It seems Robert Nordier wrote: > > OK, I'll add it to the bootblocks. > >=20 > > Incidentally, while I'm in there and thinking about it, I'd quite > > like to fix the boot code to boot from LS-120 drives at the same > > time. So if anyone has one of these, and wouldn't mind spending > > some time running a few bits of test code, I'd appreciate it. >=20 > I have a ZIP if that can help you ?? >=20 > > > > However, I'd *still* expect it to pass a major# of 0 rather than > > > > 30. Why? Because a 2.0 kernel knows only 0. And if a 5.0 kernel > > > > knows only 30, it is -- at least -- in a position to know what > > > > 0 meant, and simply substitute one for the other (under the > > > > influence of a kernel configuration option, if necessary). > > >=20 > > > Hmm, wd should give 0 and ad should give 30, no AI please :) > >=20 > > I wasn't actually thinking at all along the lines of "smart" code > > at all: > >=20 > > #ifdef FORCE_FOO > > =09if (foo =3D=3D 0) > > =09 foo =3D 30; > > #endif >=20 > Well, that breaks somewhere else, as the mount code is clever enough > to look at the name of the driver in this case "ad" which doesn't=20 > match the specified #0 ie "wd". > I kindof tried this by having my driver put itself in both the > wd & ad majors in the table, but that doesn't work, because the mount > stuff gets confused on the root name somehow, and fails to mount > root because the names dont match... >=20 > > AFAICS, adopting the separate "wd" and "ad" route entails the > > following: > >=20 > > Update your bootblocks. > > Add a /boot.config statement like "0:ad(0,a)" to make use > > of the driver the default. > > Failure to boot if you inadvertently specify wd out of habit, > > or if you specify ad when booting an earlier system. > >=20 > > So we're introducing three points with good potential for failure. >=20 > Well, what else can we do as long as we potentially need both > drivers in the kernel. I'm pretty sure that if I kill of wd.c > et all, there will be screams of bloody murder again... > been there done that :) Well, since the new ATA doesn't work with my LS-120 yet nor support DMA... ;) I want to see the LS-120 working, so where would I send it to if you wer= e to work on its driver? :) >=20 > > In contrast, the kernel configuration route requires commenting > > or uncommenting a single statement. >=20 > But that doesn't work, at least as the mount code behaves now. >=20 > At any rate, any solution that makes it possible to boot with=20 > a new driver without me having to call it "wd" something all=20 > over the place is acceptable to me... >=20 > -S=F8ren >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman=09=09=09=09=09 _ __ ___ ___ ___ =20 green@unixhelp.org=09=09=09 _ __ ___ | _ ) __| \=20 =09 http://www.freebsd.org/=09 _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve!=09 _ __ ___ ____ _____ |___/___/___/=20 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?Pine.BSF.4.05.9903172113070.12911-100000>