Date: Sun, 21 May 2000 19:57:41 +0200 From: Mark Murray <mark@grondar.za> To: Peter Wemm <peter@netplex.com.au> Cc: Doug Rabson <dfr@nlsystems.com>, current@FreeBSD.ORG Subject: Re: Major device numbers and mem device redesign Message-ID: <200005211757.TAA17130@grimreaper.grondar.za> In-Reply-To: <20000521144928.B30681CE1@overcee.netplex.com.au> ; from Peter Wemm <peter@netplex.com.au> "Sun, 21 May 2000 07:49:28 MST." References: <20000521144928.B30681CE1@overcee.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> Yes. Each instance of make_dev() takes a cdevsw argument for the minor numbe
r
> in question. So, you could have /dev/mem read/write/ioctl etc routines
> for major 2, minor 0 and 1, while have minors 3 and 4 being installed with
> their own open/close/read/write/etc routines.
>
> Devices are looked up as a hash of major+minor, and the devsw entries from
> that point on.
OK - how do the
switch (minor(dev)) {
/* stuff */'
default:
return ENXIO;
}
cases get handled? By the hashing routine?
Can these be hunted down and killed?
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
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?200005211757.TAA17130>