Date: Wed, 23 May 2001 13:17:51 -0700 From: Mike Smith <msmith@freebsd.org> To: Brian Somers <brian@Awfulhak.org> Cc: freebsd-arch@FreeBSD.ORG Subject: Re: RFC: unit_list routines Message-ID: <200105232017.f4NKHp400923@mass.dis.org> In-Reply-To: Your message of "Wed, 23 May 2001 18:02:09 BST." <200105231702.f4NH29F07183@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >I didn't do it that way because the ``usual'' way units are allocated
> > >is sequentially. Using bits when there are large numbers of units
> > >gets awkward. I figured what was required was something small and
> > >simple that would cover the requirements of most/all drivers that
> > >need to track their units so that it's easy to find an unused one,
> > >and it's easy to allocate/deallocate things.
> >
> > How does newbus allocate/manage unit numbers ?
>
> I don't think it does. The only way to find out what's in use
> (AFAIK) is by looking at every specinfo in dev_hash....
Er, what exactly are you smoking?
Newbus manages unit numbers using the devclass:
struct devclass {
TAILQ_ENTRY(devclass) link;
driver_list_t drivers; /* bus devclasses store drivers for bus */
char *name;
device_t *devices; /* array of devices indexed by unit */
int maxunit; /* size of devices array */
};
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105232017.f4NKHp400923>