Re: [Xen-devel] Re: [PATCH] Virtual console driver on /dev/xvc0

[Jeremy Katz <katzj@xxxxxxxxxx>]

On Fri, 2006-08-04 at 15:31 +0100, Keir Fraser wrote:
> On 4/8/06 3:23 pm, "Jeremy Katz" <katzj@xxxxxxxxxx> wrote:
> >> How did you pick the major? Is there a process for allocating one (I
> >> think our bklock-device major is now official)? Could we use a more
> >> dynamic (e.g., udev-based) scheme to avoid locking down 1/256th of the
> >> 8-bit major space for this?
> > 
> > The instructions for getting a major are available at
> > http://www.lanana.org/docs/device-list/instructions.txt and the official
> > list of majors/minors is at
> > http://www.lanana.org/docs/device-list/devices-2.6+.txt.
> > 
> > char major 232 is already taken for biometrics.  There's no reason that
> > we shouldn't be able to get a minor (or a couple, if it makes more sense
> > to have more than one xvc device in some case) char devices in the
> > low-density serial console region (char major 204)
> 
> That page makes it sound like the static allocation of device numbers is
> obsolete. Is there some preferred dynamic method now?

Using udev or similar is the way of doing things dynamically.  But there
are still a number of areas where static major/minor is strongly
desirable and consoles are one of those areas.  

Jeremy


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel