> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
- Major device numbers and mem device redesign Mark Murray
- Re: Major device numbers and mem device redesi... Doug Rabson
- Re: Major device numbers and mem device re... Peter Wemm
- Re: Major device numbers and mem devic... Mark Murray
- Re: Major device numbers and mem d... Peter Wemm
- Re: Major device numbers and ... Mark Murray
- Re: Major device numbers ... Poul-Henning Kamp
- Re: Major device numbers and ... Mark Murray
- Re: Major device numbers and mem d... Jeroen C. van Gelderen
- Re: Major device numbers and ... Mark Murray
- Re: Major device numbers and mem d... Poul-Henning Kamp
- Re: Major device numbers and mem device redesi... David O'Brien
- Re: Major device numbers and mem device redesi... David O'Brien
- Re: Major device numbers and mem device re... Mark Murray
